SL User Group Meetings – Page 212 – Inara Pey: Living in a Modemworld

SL projects updates 12/2: Group chat

Posted on March 21, 2014September 27, 2024 by Inara Pey

Server Deployments: week 12 – recap

Short and to the point: there weren’t any.

Upcoming Release Items

There are a couple of things server-side making their way towards a release:

Fix for login issues of agents with number display names – this is a fix an issue where users with display names made-up of numbers are unable to log-in. “It was a subtle change in a low-level library that started treating those as numbers and not strings,” Simon Linden said of the issue’s origins.
Fix for llTakeControls() issues with multiple scripts with mixed parameters in same prim

These fixes are liable to testing on Aditi prior to moving to an RC.

SL Viewer

On Wednesday March 18th, the Hotfix viewer was updated to version 3.7.4.288138. This now lists three core issues as being addressed:

Crash fix (MAINT-3703)
Update FmodEx library to 4.44.31
Additional work for MAINT-2718 (Linux viewer was using logging version of library)

Group Chat

As indicated in part 1 of this week’s report, there is work underway to try to improve group chat. A small-scale test with a dozen people was carried out with some of the initial improvements during the Sever Beta meeting on Thursday March 20th. “This is really a test that shows it doesn’t fall over with minor load,” Simon Linden said of it.

During the test, those present were asked to send lots of short messages at speed to two test groups while moving around and between various regions (walking, flying, teleporting). Few issues appeared to be noted, at least none that Simon indicted he was interested in (e.g. messages showing delay between being sent and appearing), but as noted, it was a small group. In terms of what has been done with the code and plans for the future, Simon went on:

Basically I dug into the code and found some inefficient parts and cleaned them up. I also added more metrics, so I’m hoping it can show an improvement. I’m pretty sure it will be better, but it’s really hard to guess how much better. I’m hoping to test it on the main grid soon. It would get put on a server and then it would affect a fraction of the groups. I can pick one group to target and make sure it covers that group.

As chat is handled back dedicated back-end servers, no simulator or viewer change will be required to take advantage of this work as it progresses. If the logs from this initial test show nothing unpleasant or unexpected, and providing LL’s QA are happy, testing on the main grid could start in a week’s time.

SL projects updates 11/3: TPV developer meeting, March 14th

Posted on March 15, 2014September 27, 2024 by Inara Pey

A TPV developer meeting took place on Friday March 14th. The core items discussed in the meeting are reported below, with timestamps in the relevant paragraphs indicating the point at they are discussed in the video embedded here. My thanks as always to North for the latter.

SL Viewer Updates

[0:01:37] The list of release candidates in the release channel remains unchanged from part two of this week’s projects updates, and as per my Current Viewer Releases page.

FmodEx RC

[0:01:44] The FmodEx Hotfix viewer RC (version 3.7.4.287875), is a fix Monty Linden has been working on, and is described by Oz Linden as:

A threading problem that at least manifests when there are various FmodEx things going on, but is not strictly speaking an FmodEx problem. We think that was a good and important fix, but it doesn’t seem to have done all we hoped it would do yet.

Whether or not this is a fix TPVs would need to implement quickly or not is down to how they have implemented FmodEx.

Voice RC

[0:02:38] The Voice RC is essentially the release viewer with the Vivox 4.6.x SLvoice plugin packaged with it for Windows and Mac. Commenting on in from a Mac perspective, Oz Linden indicated that it does appear to solve a number of issues, such as working with an iPhone headset adaptor, which was an issue with earlier versions, as well as addressing some Mavericks related issues.

[0:11:11] There has been some confusion over the latest SDK supplied by Vivox, in that only the Windows and Mac versions of 4.6.x have so far been supplied; the Linux version is still an older version. It’s unclear as to when the Linux Vivox SDK will be supplied, as this is apparently seen as a “lower priority” compared to Windows and Mac, although the Lab is working on Vivox to try to improve matters. The Lab is also working to try to get 64-bit versions of the Vivox SDK, which could then be made available to those TPVs building 64-bit versions of their viewers.

Interest List RC

[0:41:54] Concern is raised as the number of updates which form a part of the interest list RC viewer, and whether these may leave TPVs with another “CHUI situation” when trying to merge things. The repository for the viewer has been available since the viewer reached RC status, however, Oz went on to comment:

There’s a bunch of refactoring of things that people decided needed refactoring as a part of the process [and] which may or may not have been strictly needed as [a] part of interest lists; that is, part of the functional change that that branch is doing. Some of it was a new trace capability that’s used in a bunch of places where they wanted to take the measurements they wanted to take about it.

The interest list RC is working its way towards release status ... slowly ... — The interest list RC is working its way towards release status … slowly …

There have been various stability issues with the interest list RC, hence why it has remained an RC rather than being promoted to the de facto release viewer. However, it is now reaching the point where its stability is comparable to that of the other RCs in the release channel – and is actually better than some.

In terms of merges, there is the potential for the interest list viewer to cause TPVs some problems, as there appear to be changes to llCommons and other libraries which are causing issues for those TPVs which have attempted a merge.

Google Breakpad

[0:04:53] The Google Breakpad RC is due to make another appearance, as a “bunch of issues have been wrestled to the ground”, and the hope is that when it does appear in the release channel, it will mark the last round of updates for that particular project, and those TPVs using Google Breakpad are advised to take a look at what the Lab has done.

Overall Status for RCs

[0:04:10] Overall, it appears as if none of the RCs are performing as well as the Lab would like them to be in terms of crash rates. It had been hoped that the FmodEx Hotfix RC would get the Lab back below what Oz referred to as “an acceptable, if not admirable, crash rate”, but it has not done so as yet.However, the other RCs in the channel should see updates released in week 12 (week commencing Monday March 17th), one or more of which may improve the crash rates.

[0:43:56] In terms of what does get promoted next, the most likely candidate will be the RC which shows clear evidence that it is reducing the crash rate compared to current levels across the release and RC viewers.

[0:05:27] In the meantime, because of the volume of RCs sitting in the release channel, the Lab are holding back a number of further RCs,. These include the Project Zipper (faster installer) viewer being updated to RC status, and the group ban viewer (although there are bugs in this which are still being worked upon). There is also likely to be a further Snowstorm RC appearing with a mix of code contributions, again once the number of viewers currently in the release channel is thinned-down a little.

Continue reading “SL projects updates 11/3: TPV developer meeting, March 14th” →

SL projects update week 11/2: group bans, JIRA, Oculus Rift

Posted on March 14, 2014September 27, 2024 by Inara Pey

Server Beta meeting, Thursday March 13th

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!

SL projects updates week 11/1: server, viewer, group bans

Posted on March 12, 2014September 27, 2024 by Inara Pey

Server Deployments: week 11

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

Main (SLS) Channel

On Tuesday March 11th, the Main channel was updated with the server maintenance project deployed the BlueSteel and LeTigre channels in week 10. This 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 following the week 10 deployments about 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.

Release Candidate Channels

On Wednesday March 12th, BlueSteel and LeTigre should join Magnum in having support for a new version of the inventory service, AISv3, enabled. This service requires the use of the Project Sunshine RC viewer.

SL Viewer Updates

On Monday March 10th, the Maintenance RC viewer was promoted to the de facto release viewer, version 3.7.3.287491 (download) – release notes are here.

A new hotfix release candidate appeared on Tuesday March 11th. The FmodEx Hotfix version 3.7.4.287875 (download and release notes) is intended to correct a suspected thread race crasher in the FmodEx audio streaming library.

Otherwise, all other viewers remain as listed in my Current Viewer Releases page.

Group Ban list

Baker Linden, ironing-out viewer-side issues with Group Bans

Baker Linden is working to fix issues which were picked-up on during some initial public testing of the Group Ban functionality on Aditi during the Server Beta User group meeting on Thursday March 6th. Those issues already identified with the viewer code can be found here.

Allowing for further testing and scheduling, the current plan is to have the server-side elements of the Group Ban functionality deployed across Agni prior to the viewer code being released in an RC viewer.

Until that happens, the viewer code will either remain as a direct download or may filter into a project viewer at some point once the server code is ready to start being deployed on Agni (there is currently no date as to when this will be).

Currently, the development viewer is available for Windows or Mac OSX or Linux, but the group ban functions will only work on the Aditi test regions such as in Morris (at the Server Beta UG meeting area).

JIRA: Old BUG issues Can be Made Visible

The re-opening of the JIRA occurred in week 10, and at the time, only BUG issues raised after the re-opening would be available to public scrutiny. However, it now appears as if reporters have the option of re-opening their old issues to public viewing if they so wish. Callak Skytower, for example, has made BUG-4427 publicly viewable once more.

Other Items

Group Role Updates

An issue with group roles was raised at the Simulator User Group meeting on Tuesday March 11th. If a member of a group is assigned a new / additional role, the update occurs server-side, and is reflected in the Group floater for the owner / officer (or whoever is empowered to grant roles), but the change is not reflected in the Group floater of the person who has been granted the new / additional role until such it as they either re-log or are sent a re-invitation to join the group.

This has not been a cause of major concern, possibly because there is little in the way of role re-assignments occurring in groups on a daily basis. It is not currently clear as to whether the matter will be addressed, although there was general agreement that updates to role assignments should require something like a relog in order to be seen in the Group floater.

My thanks to mona Eberhardt and Rex Cronin for the meeting transcripts.

SL projects update 10/2: group ban preview

Posted on March 8, 2014September 27, 2024 by Inara Pey

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.