Day: April 29, 2015

SL projects updates week 18/1: server, viewer

Posted on by Inara Pey
UNIA launches at 12:00 noon on Monday, April 27th
MadPea’s UNIA is now open for those of a brave disposition, and uses Experience Keys / Tools

Server Deployments Week 18

As always, please refer to the server deployment thread for the latest news.

  • There was no Main (SLS) deployment on Tuesday, April 28th.
  • On Wednesday, April 29th the three RC channels all received the same sever maintenance package. This comprises Internal server logging changes  and a new flag for llGetObjectDetails()  – OBJECT_LAST_OWNER_ID; plus new data which can be requested  via llGetEnv(). These are:
    • “agent_limit”- get the maximum number of avatars normally allowed on the region (teleport home, and login to last location, are allowed to exceed this).
    • “estate_name”- returns the name of the estate (e,g, “mainland”, “Linden Homes”, “My Happy Estate”, etc. )
    • “region_cpu_ratio”- returns the number of regions per CPU for this region type (i.e. “1” or “4”)
    • “region_product_name” – returns the type of region this is: “Estate / Full Region”, “Mainland / Homestead”, “Estate / Openspace”, “Estate / Full Region – Skill Gaming” etc.
    • “region_product_sku” – returns the region’s product number as a string
    • “region_start_time” – returns the time the region was last (re)started, in llGetUnixTime format
    • “simulator_hostname”  – returns the simhost running this region. Same as llGetSimulatorHostname but without the script delay.

Commenting on the llGetEnv() updates at the simulator User Group meeting on Tuesday, April 28th, Simon Linden, who made the updates, said, “these are all pretty simple ones … I went for the easy pickings.  Basically, information we already  sent to the viewer, or was readily available, and thus not a privacy issue.”

He continued, “There was one [further option] for the max number of agents that was in the original list but that one got skipped … not part of a sinister plot but I overloooked it.  want to do some other things with that limit sometime soon as well 🙂 … I’d like to see how the region and viewer performs with bigger numbers. Things go bad with many AVs for a variety of reasons … the server has more updates to send to more people, all wearing more scripts and AOs and HUDS [and] the viewer gets overwhelmed with too many complex avatars and too many textures in the download and graphics pipeline.”

SL Viewer

The Avatar Layer Limits RC viewer updated to version 3.7.29.301305 on April 28th, bringing it to code parity with the current release viewer. This RC allows users to wear up to 60 wearable layers (jackets, shirts, tattoo, alpha, etc.) in any combination – so you can wear 60 tattoo layers with it an nothing else, if you want – rather than being restricted to wearing a maximum of 5 of each type of layer.

Other Items

Online / Offline Indicators

People are noticing that the group chat list (the list of group members in the Group panel), is now much slower to update as people’s status changes (i.e. whether they are on-line or off-line). This is intentional, and comes as a result of the recent improvements made to group chat.

In particular, and as I reported in these pages as work on group chat commenced in 2014, the volume of people logging-in to and out of SL can generate a huge amount of updates for the group chat service (given your status has to be sent to every group of which you’re a member, and to over member of that group who is online to update the group list in their viewer with your new status), meant that more time was being consumed by the group chat servers in handling these update messages than in handling actual messages.  The fix for this problem means there is a natural delay in group list updates, as they are now processed differently to reduce the impact they have on message handling.

However, some people have started noticing that some group chat lists with 20+ members seem to take a very long time to update – times of 5-10 minutes have been mentioned, and this is causing some confusion when seeking things like assistance from group owners / moderators (as they can appear to be logged-in long after they have logged-off). It’s also bee reported that at times the list seems to get stuck with no updates until the group chat itself is closed and re-opened, although this appears to be somewhat intermittent.

Bright Canopy: first user group meeting notes published

Posted on by Inara Pey

Bright CanopyBright Canopy, the planned new streaming service for Second Life and OpenSim, hosted its first user group meeting on Saturday, April 25th.

The meeting drew interested parties and beta testers from SL and OpenSim, and was hosted by Bright Canopy founder, Bill Glover (known in-world as Chaos Priestman). As Bright Canopy will be running on technology provided by Frame (who are putting considerable effort into helping to get the service up-and-running and ensuring it can meet users’ expectations), they were represented at the meeting by Carsten Puls (Carsten at Frame in SL).

Held in text chat to allow those running on SL Go to join the session, the meeting was mainly focus on questions and answers to give people a chance to learn what they wanted to learn about the service, and ran to just over an hour.

The notes from the meeting have now been posted on the Bright Canopy website. Rather than presenting a formal transcript (because some questions were asked a number of times), the meeting notes group questions and answers in to subject groups.

While those interested in potentially moving to Bright Canopy when it does launch should read the notes directly in order to get the most complete picture of things, I’m providing a high-level key point summary below from the major topics discussed (note questions were asked about supporter viewers, please refer to the meeting notes for these):

Chaos Priestman, aka Bill Glover, Bright Canopy’s founder, at the in-world meeting

When will Bright Canopy be ready?

  • Bright Canopy is in closed beta,  right now. The plan is to move to an invitation-only pre-launch as soon as possible, to allow for more widespread testing; when this happens depends on getting a few more technical issues dealt with and sorting management and billing issues

How does it work?

  • Bright Canopy is like SL Go, but accessed via a web browser. Initially, for the pre-launch this will be Chrome, but support for other browsers will be there for the launch. Essentially, if your device can run a modern browser and is capable of viewing a streamed video, you should be good to go
  • Bright Canopy will provide the service, Frame will managed the underlying technology and Groove will provide support assistance

Accessibility and performance

  • Bright Canopy will initially be hosted in the USA. However, Frame utilises Amazon WAS G2 servers, so the aim is to support Bright Canopy as widely as possible. Frame already utilises Amazon data centres in Ireland, Tokyo, Sydney, Singapore, as well as both the east and west coasts of the USA
  • There may still be legal restrictions that prevent people in some countries from using the service (as we the case with Germany and SL Go); these will be looked into
  • In terms of connectivity, a bandwidth of at least 3 Mbps is required and latency of under 100 ms

Price and Payment Options

  • Pricing is not currently available. The idea is to make the service as cost-effective as possible while obviously meeting the costs involved in supplying the service
  • Stripe is being used for back-end payment processing
  • Payment options will initially be credit card and bitcoin for the pre-launch. linden dollars will be added after pre-launch, and PayPal may be offered as well.

For the rest, as noted above, please refer to the Bright Canopy blog.

If you have any questions on the service, please be sure to ask them on the Bright Canopy blog, not here, so that they can be fully addressed.