The majority of the following notes come from the Simulator User Group meeting of Tuesday, June 19th, 2018.
As always, please refer to the server deployment thread for the latest information.
- On Tuesday, June 26th, the Main (SLS) channel was updated with server maintenance package 18#18.06.14.516450, previously deployed to the LeTigre and Magnum RC channels, comprising internal fixes and logging improvements.
- On Wednesday, June 27th, the release candidate channels should be updated with server maintenance package 18#18.06.22.516968, which includes Animesh on a first-time deployment for LeTigre and Magnum (having been deployed to BlueSteel in week #25), and “new Main Channel code”.
Some SLS channel regions reported double restarts on Tuesday, June 26th, and these are being investigated by the Lab.
Follow the Wednesday, June 27th, Animesh will be live on all the major RC channels – however, as previously noted in this updates, it is still in development, and not product-ready.
The Animesh project viewer, necessary for working with Animesh and rendering it correctly, can be obtained from the Alternate Viewers wiki page.
You can find further information on Animesh via the following resources.
- Animesh User Guide
- Animesh test content
- Animesh test regions:
- Animesh LSL methods:
- Animesh – Updated Limits and Cost Formulas
- Animesh feedback thread
- JIRA filter for Animesh
- The release viewer updated to version 18.104.22.1686459 (dated June 15th) on June 21st, formerly the Pálinka Maintenance Release Candidate.
- A new Maintenance RC viewer, version 22.214.171.1246813 and code-named Quinquina, was released on June 22nd.
- The Animesh project viewer updated to version 126.96.36.1996525 on June 22nd, and again on June 25th to version 188.8.131.526979.
The other SL viewers in the current pipelines remain as:
- Project viewers:
- Linux Spur viewer, version 184.108.40.2069906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 220.127.116.110847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
Environment Enhancement Project (EEP)
The is still some confusion as to how EEP will work with different region / parcel windlight settings at altitude when compared to Firestorm’s parcel windlight capability. In short:
- Firestorm allows the windlight within a parcel to be changed at any altitude using a command line construct in the About Land description floater.
- However, this is purely a viewer-side change.
- Anyone entering a region using a viewer that does not have the same windlight support will not automatically have the setting defined in About Land applied to their viewer.
- EEP should ensure that windlight settings set by altitude will apply to everyone in a parcel, regardless of the viewer they are using.
- However, windlight changes by altitude are limited to four heights: from ground level up wards; 1,000m and above; 2,000m and above; 3,000 and above.
Top Scripts and Region / Parcel Management
Some people are experiencing region performance issues – notably around scripts, etc. It’s been suggested that making Top Scripts and Colliders visible to parcel holders within a region so they can see what in their parcel might be impacting performance has been suggested.
- This isn’t a fresh request (see JIRA SVC-835), but it is one that hasn’t been discussed recently.
- The concern was raised that allowing Top Scripts to be more widely visible could lead to harassment between parcel holders in a region.
- There is also some concern that over-use of the capability could itself impact region performance, because Top Scripts is an intensive query to run.
- Even so, it is something being take back to the Lab for further discussion, and is seen as “reasonable”, providing the ability to start / stop scripts isn’t included (griefing vector).