2019 Simulator User Group week #44

Abrahamstrup, September 2019 – blog post

Simulator Deployments

At the time of writing, no deployment notes had been published. However:

  • There was no deployment to the SLS (main) channel on Tuesday, October 29th, leaving it on server release 2019-10-03T01:12:11.531528.
  • There are two RC deployments planned for Wednesday, October 30th:
    • 2019-10-24T19:07:13.532143, comprising further internal script improvements, internal logging changes and improvements to simulator state saves.
    • 2019-10-26T00:06:48.532192, comprising a previously released hotfix to fix teleports being 5%-7% less reliable and makes the simulator take a little bit longer to report as “Up” to the Lab’s internal tools to more accurately reflect when residents can actually access a region.

SL Viewer

The Project Muscadine (Animesh follow-on) project viewer updated to version on October 28th. The update brings it to parity with the release viewer, but contains not project updates.

. The rest of the viewer pipelines remain as follows:

  • Current Release version, formerly the Vinsanto Maintenance RC viewer, dated September 17th, promoted October 15th – NEW.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
  • Project viewers:
    • Copy / Paste viewer, version, October 21st.
    • Legacy Profiles viewer, version, September 17th. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version, July 16th.

Script Event Order

It was asked if the script updates would affect the order in which script events are handled, Rider Linden stated:

Some events have always had priority just by virtue of the order in which they were collected. The order of collection has changed. For instance, sensor events were collected and posted before chat events and then touch events. Chat events are now posted immediately upon processing in the simulator. It should still be FIFO… just don’t bet on what event gets collected when.

In addition, it was noted in regards to event messages:

  • Generally, event handling should not to be counted on in any sort of coding since it may change again in the future.
  • Link messages:
    • If multiple link messages are sent from a single source to a single receiver script, the ordering should be preserved. Similarly, when using llLinkMessage to send a message from script A to script B in the same prim, they are posted immediately, and the order is maintained.
    • If the same message is sent to link A and then to link B, the order the links get them is not always the same. Similarly, if script A and script C are using llLinkMessage to post to B, all bets are off which gets there first.