Server Deployments
Please refer to the server deployment thread for the latest news.
- On Tuesday, February 19th, there was no deployment to the SLS (Main) channel, leaving it on server maintenance package 19#19.01.25.523656; however, region on the channel were restarted. The planned update for the channel was again postponed due to a late-breaking bug.
- On Wednesday, February 20th, 2019 the RCs are likely to be updated as follows:
- BlueSteel and LeTigre should receive EEP update server maintenance package 19#19.02.16.524516, comprising the following fixes:
- BUG-226252 [EEP] Please create an internal error code for llReplaceAgentEnvironment() & llSetAgentEnvironment() that distinguishes whether an agent does not have the experience allowed and if the experience is not allowed at their location.
- BUG-226246 [EEP] llGetEnvironment() reports SKY_LIGHT fade_color as a rotation instead of a vector. (SKY_LIGHT only returns vector light_direction and vector total_ambient. fade_color is removed https://wiki.secondlife.com/wiki/LlGetEnvironment)
- Magnum should receive server maintenance package 19#19.02.16.524515, comprising further internal fixes.
- BlueSteel and LeTigre should receive EEP update server maintenance package 19#19.02.16.524516, comprising the following fixes:
SL Viewer
The EEP Project viewer updated to version 6.0.2.524476 on Tuesday, February 19th. The remaining viewer pipelines remain as follows:
- Current Release version 6.0.1.522263, dated December 5th, promoted December 13th, 2018. Formerly the Spotykach Maintenance RC viewer – No Change.
- Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
- BugSplat RC viewer, version 6.1.0.524348, dated February 13th. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
- Estate Access Management (EAM) RC viewer, version 6.1.0.523351, dated January 23rd.
- Love Me Render RC viewer, version 6.0.2.523177, dated January 16th.
- Project viewers:
- Bakes on Mesh project viewer, version 6.0.2.524367, dated February 15th.
- 360 snapshot viewer, version 5.1.6.515934, dated June 6th (see my hands-on update).
- Linux Spur viewer, version 5.0.9.329906, dated November 17th, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 3.7.28.300847, dated May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.
EEP Deployment Oddities
There are some oddities being witnessed while EEP is being deployed. These should all go away once the code is fully deployed on the servers and the viewer code has reached all release versions of viewers.
Day / Night Cycle Differences
With the EEP updates currently on around 20% of the main grid, it is possible for very different values to be returned to the viewer when travelling between adjacent EEP and non-EEP regions, and this has been causing some confusion. Rider explains it thus:
EEP changes how the time is calculated. llGetSunPosition is dependent on the environment. It was not before. Legacy regions determine the beginning of the day differently than EEP regions. So until [they] have been [updated] there will be some disruption.
The way the start of the day has changed. It is now GMT-8, this [also] may not align with neighbouring legacy regions.
Other Oddities
- There are also reports of jarring region crossing transitions that can sometimes occur when moving between regions with different EEP settings – see BUG-225689.
- Stars on EEP regions will appear black against the daytime sky when seen on a non-EEP viewer with Advanced Lighting Model (ALM) enabled, or as white stars with ALM disabled.
Marketplace Gifting
There is an issue with the redelivery of gifts made via the Marketplace that (depending on the age of the original gift delivery) might result in the redelivery going to the sender, rather than the intended recipient – see BUG-226124. If you encounter this, please raise a support ticket.