Jump to content

Deploys for the week of 2011-06-20

Oskar Linden

You are about to reply to a thread that has been inactive for 4111 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

We do have a release ready for this week. The Group Chat fixes on BlueSteel are being promoted to the main channel

Second Life Server (main channel)
The majority of the group chat fixes were fixed on our util nodes a week and a half ago. The changes in this branch affect users using the same group while on the same region. This is a smaller use case, but it will see a benefit.
  • Enable addressing chat message to more than one agent in a region
    • A protocol was implemented on the sim and in the multiagent chat backbone service to enable addressing of a chat message to multiple agents. When more than one recipient agent is present in the same region a single request is made to the sim addressed to all recipients. Previously a request was made for each agent needlessly duplicating requests.
2011-06-21, 5:00am: Rolling Restart - Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/11

Second Life RC BlueSteel
We have a set of maint-server fixes from Josh here this week. 
  • Added new parameter to llHTTPRequest - HTTP_VERBOSE_THROTTLE. Value is '''4''', type is '''integer'''. If specified in the parameters list as a non-zero value (true), the script will emit errors when the throttle for outgoing requests is hit. If zero (false), the script will remain silent on errors. Example:
    key http_request_id = llHTTPRequest("http://example.com/", [HTTP_VERBOSE_THROTTLE, 0], "");
  • SCR-67: Added new constant PRIM_OMEGA for use with llGetPrimitiveParams, llSetPrimitiveParams, llGetLinkPrimitiveParams, llSetLinkPrimitiveParams, llSetLinkPrimitiveParamsFast. This gives access to the "target omega" property of primitives which can be set via llTargetOmega, but allows getting the current target omega for a prim (previously not supported) and setting the target omega on a child prim (previously only doable with a script on each prim). The list has the signature [vector axis, float spinrate, float gain] like the parameters for llTargetOmegaExamples:
    // Set this prim rotating
    llTargetOmega(<1.0,3.0,0.5>, TWO_PI, 1.0);
    // Read back this prim's current target omega
    list current_omega = llListToList( llGetPrimitiveParams([PRIM_OMEGA]); // should be [PRIM_OMEGA, axis, spinrate, gain]
    vector axis = llList2Vector(current_omega, 1); // Should be <1.0,3.0,0.5>
    float spinrate = llList2Float(current_omega, 2); // Should be TWO_PI
    float gain = llList2Float(current_omega, 3); // Should be 1.0
    // Set all child prims rotating
    llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_OMEGA, <1.0,3.0,0.5>, TWO_PI, 1.0]);
Bug Fixes:
  • Fixed issue with "Buy" option remaining set on purchased child prims of no-mod objects (Originally VWR-9796)
  • Addressed issue with teleport and other service failures affecting simulator hosts.
  • Server-side support for STORM-1261 - send message IDs on login failure to allow localization
  • SVC-6905: Fixed issue with objects resisting return, delete, take and autoreturn
  • WEB-3096: Fix unsubscribe link in IM-to-Email messages"
  • SVC-6953: Fixed issue where region restart notification appears to be from the avatar being notified.
  • SVC-5780: More specific error message when deeding land to group fails because transfers are blocked on the region

2011-06-22, 8:00am: Rolling Restart - Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/11

Second Life RC LeTigre
This channel will keep Kelly's "mono2-performance' branch with fixes.

2011-06-22, 9:00am: Rolling Restart - Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/11

Second Life RC Magnum
This project is keeping the "mesh-prep" branch after getting some more bug fixes. This contains infrastructure and framework updates to get the grid ready for mesh. It does not include any mesh features or functionality. The physics engine has been updated and the 10cm gap between colliding objects has been removed for some objects. 
The llCastRay() function has been included, but it is disabled..

2011-06-22, 10:00am: Rolling Restart - Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/11

We will be monitoring this thread during the next week so please feel free to post issues that you feel have been introduced by the new code. Please file a JIRA for issues you find and post the JIRA link into this thread. It really helps us out. When determining if issues are relevant or not research is key. Tracking down exactly the right situation where an issue is occurring greatly speeds up the development process to get fixes in place.
I appreciate your help. Have a good week!
p.s. If you are interested in helping test SecondLife in beta please join the group "Second Life Beta" in-world. We also have an email list where we communicate upcoming projects and how you can help. ( https://lists.secondlife.com/cgi-bin/mailman/listinfo/server-beta ) Once a week we meet on ADITI to discuss new features, new bugs, new fixes, and other fun stuff. You are more than welcome. Information is here: https://wiki.secondlife.com/wiki/Server_Beta_User_Group


Link to comment
Share on other sites

Group chat appears to not be fixed.

I am chatting in two different groups, with only about 10 people in each chat at once. One is not lagging at all, but the other is lagging a ton. I'm doing so from the Northern Michigan sim, which is on the main server channel.

Link to comment
Share on other sites

I think something has gone wrong, but I'm not sure I have enough data to pin it down, and I don't speak JIRA

1: All this has happened since the completion of roll-outs this week.

2: In some cases, I know the Le Tigre RC server is involved. In other cases I'm not at all sure which versions of the Server code were involved.

3: Both problems have been seen the current versions of Firestorm and Phoenix. That is, V1 and V2 codebases, both programs having worked well for at least a week before the problems started.


Problem 1: A region becomes isolated from all adjacent regions, with nothing visible. I've had this happen with the Furness and Uzume regions.

Problem 2: Region-to-region transfers, whether by teleport or by crossing the boundary, are sometimes incredibly delayed. This can lead to large-scale rubber-banding, up to 5km in one case  By the time it gets that bad, it's likely to fail completely, with the Viewer exiting. It's clearly worse with scripted vehicles, and I have some which are decent, some dreadful, for the number of scripts used.

Problem 3: Failure to initiate a group chat session. There's a initialisation-error message in Firestorm. No message in Phoenix, but the chat session doesn't start.



Link to comment
Share on other sites

Yes, the non-existent region problem seems to have struck again, a couple of minutes ago, when crossing from Burandt to Miller, at the start of the road bridge. In fact, the scenery was slow to rez, then the bridge rezzed, and then everything vanished on the Miller side of the boundary, before I was translocated to Burandt (0,0,0), with nothing visible but a flat white plane, occupying Burandt region-space only, apparently with a snow texture.


Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4111 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...