Server Deployments week 46
As always, please refer to the week’s forum deployment thread for the latest news and updates.
Main channel: Tuesday November 12th
Release Candidate Channels, Wednesday November 13th
- BlueSteel and LeTigre should receive the maintenance package originally scheduled for deployment to all three RC channels in week 45, but which was cancelled as a result of a last-minute issue being found. This package comprises further infrastructure changes for the yet-to-be-announced Experience Keys (experience tools) project
- Magnum should receive a new server maintenance project this week. This project fixes some bugs, including BUG-4152 related to vehicles crossing region boundaries, as described in this thread; and which also includes some changes around script behaviour, comprising:
- The fix to allow objects rezzed by sat-upon objects should have a fresh auto-return and temp-on-rez timer, This will allow them to last the full ~60 seconds (for temporary) or parcel auto return time. This should help is situations where combat vehicles in regions with short auto-return times can have their ordnance immediately returned when a weapon is fired, and any temp vehicles are unable to rez attachments, even when sat upon
- Fixes to prevent estate managers / owners being teleported home through a misuse of llTeleportAgentHome(), and to prevent estate managers / owner being affected by “Trojan” objects manipulating ESTATE_ACCESS_BANNED_AGENT_ADD
- Updates to the grey goo fence do that it is stricter for large object rezzes in a further attempt to limit the ability of griefers to bring down a region through multiple rezzing of large objects
- More robust handling of inventory management within objects
- Cleanup of controls-grabbing in LSL scripts (no functional changes).
The SL release viewer updated on Tuesday November 12th to version 220.127.116.113403, formerly the Maintenance RC comprising finer access control for estate/parcel owners; CHUI: toggle expanding Conversations by clicking on icon; GPU table update + more.
It is thought the project viewer containing the last of the current viewer-side updates for interest lists should be appearing very soon now. After recent setbacks in getting the viewer publicly visible, the time frame for its arrival had been noted to be unlikely before November 12th. However, speaking at the Simulator User Group meeting on the 12th, Andrew Linden indicated he believed the viewer may well be out in the next few days.
Andrew Linden’s Bug Fixing
Andrew Linden has been taking time to fix a some unusual bugs. The first, which is not generally visible, he describes as, “In some cases our servers will upload an asset multiple times before it successfully creates an inventory item (on take to inventory for example). Which creates garbage assets in the asset system.” This issue could also result in multiple notifications being sent to the avatar uploading the item, if they remained in the same region.
The second issue he’s fixed is that of “ghost objects” appearing in the viewer but which are not present on the region server. This issue appears to have been caused by a race condition which could occur under certain situations such as deleting the objects too fast on a region crossing, so they’d be removed server-side, but not from the viewer. Both of these fixes should be appearing in an RC soon.
Group Management and Culling
Request have been made to have the limit of banned avatar lists raised from 500, particularly for regions that are popular with users. Whether there is a widespread need for this is entirely open to debate, but during the discussion of the problem being faced by a particular estate, suggestions were put forward by which such lists might be made easier to manage, including:
- Auto-culling from all ban lists of any account name banned from the grid
- Such auto-culling to take place only as a ban list approaches its upper limit
- Add a feature by which would allow the removal from a list any avatars that have not logged-in to SL for a given period of weeks / months / years. If implemented, this could either take the form of a selectable set of options (e.g. something like 6 months, 1 year, 2 years), or possibly be a free-format field the owner can use to specify as the time period.
Whether any of these options eventually get implemented, remains to be seen (and doubtless on whether feature requests are filed).
This conversation was also bound-up with matters of group chat and group chat lag. Various suggestions were put forward for trying to address this as well, ranging from replacing the current group chat mechanism with something like IRC and whether it would actually work / scale any better, through to implementing a server-side change so that when someone leaves a group chat, the channel is actually closed, rather than messages still being sent to the viewer, which just disregards them, as is currently the case. Commenting on the status of group chat in general, Simon Linden stated, “Just FYI, practically speaking we’re not going to be re-writing the chat system any time soon.”