Category: Simulator User Group

Server Deployments: week 11 – recap

As always, please refer to the server deployment thread in the forums for the latest updates / changes.

• On Tuesday March 11th, the Main channel was updated with the server maintenance project deployed the BlueSteel and LeTigre channels  in week 10.
• On Wednesday March 12th, BlueSteel and LeTigre joined Magnum in having support for a new version of the inventory service, AIS v3, enabled.  This service requires the use of the Project Sunshine RC viewer. The only changes compared to last week’s Magnum release was to include this week’s SLS changes.

Aditi Server Maintenance Package

A new server maintenance project arrived on Aditi in week 11, en route for a release on the main grid. This includes some bug fixes and some further work on the LSL syntax project  Ima Mechanic has been developing, and which is largely encapsulated in STORM-1831. The new project on Aditi specifically includes a new schema to fix STORM 2000, so expect this to be filtering through to the main grid in due course.

Group Ban Update

Not a lot to report here. Whirly Fizzle uncovered an awkward bug whereby a person granted the ability to ban others from a group could actually accidentally ban themselves. This proved a little hard for the Lab to initially pin down, prompting Maestro Linden to comment at the Server Beta meeting on Thursday March 13th, “We [he and Baker] both had problems earlier, because we were using a more manual method of just POSTing the data to the capability.” However, now the issue has been identified, a fix is being worked on.

JIRA Settings – Making Older BUG Reports Visible.

Following my note in part 1 of this report that users can opt to set their older BUG reports visible to the public, Maestro Linden said:

By the way, it’s possible to set the visibility of your past BUG issues by editing the ‘Security Level:’ setting. For the most part, we’re leaving that up to the reporters to change, if they’re willing to share their bug report issue more widely.

The reason we’re doing it that way is because people previously filed BUG reports with the expectation of only a few people being able to see it, and in some cases there are sensitive details like email addresses and conversations and whatnot.

On the matter of privacy, Maestro also indicated that new BUG reports can also be set for limited public viewing – that is, only to “Triagers and Reporter” should anyone have any concern over posting sensitive information in a new BUG report.

Oculus Rift

Not a lot to report here. The Lab has put out a call for beta testers for the Oculus Rift version of the viewer, as I reported here. commenting in broad terms about the project, Maestro Linden indicated that there is a slight drop in frame rate when using the headset, although he was uncertain as to the overall impact. He also described the revised UI as seen when in Riftlook as floating overhead, possibly in a toroidal form, and that the user needs to move their head to see it, so as not to have the UI invade the world view. He actually gave up trying to describe it, as he was without a headset when discussing it, and reported, “Marissa’s trying to explain it to me but it’s complicated :).”

Those fortunate enough to have a headset and who get into the beta programme will doubtless find out in due course!

Server Deployments: week 10 – recap

As always, please refer to the server deployment thread in the forums for the latest updates / changes.

• On Tuesday March 4th, the Main channel was updated with the infrastructure update deployed the RC channels  in week 9.
  • On Wednesday March 5th, Magnum remained on the same server version as week 9, comprising the infrastructure update and enabled support for AIS v3.  BlueSteel and LeTigre were updated with a new server maintenance project which contains the following bug fixes:
    • Fixed a bug in which the server release notes link in “About Second Life” would sometimes fail to appear
    • Fixed a bug in which certain objects had incorrect status when crossing between regions
    • Fixed a crash mode

A question in the forum thread on the nature of the fix for “bug in which certain objects had incorrect status when crossing between regions” was responded to by Maestro Linden, who explained the fix was limited to what appears to be a single-case issue.

SL Viewer

The Sunshine project viewer moved to RC status on March 5th, with the release of version 3.7.3.287158 (download and release notes), and a new Voice viewer with Vivox updates entered the release channels as an RC viewer, version 3.7.3.287288 (download and release notes), both of which I previewed here.

The Maintenance RC viewer updated on March 6th to version 3.7.3.287491 (download and release notes). This view includes a range of LL-driven MAINT fixes, including crash fixes, updates to address CHUI-related issues, bug fixes and some localisation work – please refer to the release notes for details.

Group Bans

The Group Ban viewer is approaching a point where it will be appearing in a project viewer form, and it was put through its paces in a group test on Aditi (where some regions have the server-side support), during the Sever Beta meeting on Thursday March 6th.

I’ll be providing a complete overview of how this ability, which allows group own and those within the group assigned the group ban power, to eject and ban people – such as spammers – from a group. The capability is specifically aimed at groups with open enrolment, and those banned are unable to re-join it until such time as their ban has been lifted – although there is a maximum limit of 500 on the group ban list. Go beyond this, and attempts at further banning will fail until such time as one or more names are removed from the list.

I’ll be reviewing the capability in full once the viewer reaches a project viewer status, but in the meantime I’m including a couple of screen caps showing the some of the addition to the group floater which allow group bans to be managed but those empowered to do so.

There’s still some work to be done on the viewer (there are some missing notifications, for example, and some issues were found in the when banning people, which need to be addressed). Also, the server-side code has yet to be deployed to the Main grid. So it may still be a little while before we see the group ban functionality progressing more towards more widespread use.

Other Items

Inventory Loss Issue

There are reports of some users experiencing inventory loss. It is said that around three JIRA reports have been filed on the matter, which started occurring on Magnum regions after the AIS v3 was enabled. However, whether or not the losses are linked to the code or not is unclear. The issues are being described as corrupt inventories, with all contents gone, and LL’s own inventory repair tools have failed to rectify matters. The situation is currently under investigation by the Lab, and it appears that the issue may be related to the use of “obscure” viewers.