Oskar Linden

Nova Convair wrote: I placed a monitor on an estate sim (Main Channel) and one on a mainland sim (LeTigre). Idles around 5.5% on the mainland and 0% on the estate. So idling is there, but not everywhere. And if it's there you cannot see it of course. Idiling is enabled everywhere. the estate must have something keeping the region awake. __Oskar

Stickman Ingmann wrote: Well, they did something right. I didn't even notice. Thanks for the information! Haha! That's the idea.

Echo Hermit wrote: This paragraph really needs emboldened text. better? :cathappy:

  The fix for SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) is going out to the main channel tomorrow morning. This means that this issue will be fixed gridwide. Thank you for your patience. UPDATE: We are experiencing some hardware issues and have to postpone the Wednesday AM RC roll. We'll be doing it Thursday morning instead. Second Life Server (main channel) The code that was on all RC channels last week is getting promoted this week.   Bug Fixes VWR-5044: Attachments only change/inherit the active group when they're "rezzed VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders VWR-20320: Show in search and set for sale remain enabled after owner changed SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location. STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result SVC-7525: Selected objects move when a new keyframe motion is started SVC-7793: Scripted agents can't abandon land on private estates SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side. SVC-7968: When TPing using a landmark the server sends two TeleportStart packets SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938 SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset. SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047 SVC-7641: Add object location info to messages, was "Object on land sending excessive messages SVC-8177: There is different behaivior between the RC channels and the main channel involving permissions, objects lose modify permissions SVC-8208: L$ received notification not appearing when on an RC region 2012-09-11, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12    Second Life RC BlueSteel This is a maint-server project. Bug Fixes SVC-8119: New mass-related llApplyRotationalImpulse error SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047 SVC-8144: Estate Tools, Debug, Disable collisions stopped working. 2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12   Second Life RC LeTigre This channel has the same code as is on BlueSteel. 2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12   Second Life RC Magnum This channel has the same code as is on BlueSteel. 2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12   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!   __Oskar   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   This is not a forum thread for off-topic and unproductive ranting. I will no longer tolerate it. This forum thread is to discuss newly found issues in the Release Candidate channels. If you feel the need to have your opinions heard on topics unrelated to new bugs then please start your own thread. If an individual continues to post unproductive and off-topic comments I will take measures to remedy that. If you are unsure about your posting please read this : "Linden Lab Official:Community Participation Guidelines" https://wiki.secondlife.com/wiki/Issue_Tracker/Conduct

There wasn't anything particular about any of the individual RC's this week. We also haven't really touched physics in a while. So any physics related stuff would be on either all regions, or on all RC channels. We do have some upcoming code to help with region crossings. The code that is on the RC channels now will be promoted in the AM. __Oskar

WolfBaginski Bearsfoot wrote: Magnum RC channel: I have seen Physics frame rates plummet while vehicles are rezzing and moving in the region, Today it went as low of 0,3 fps. Are you seeing these issues in the other channels? __Oskar

Hitomi Tiponi wrote: Oskar Linden wrote: Hitomi Tiponi wrote: I did suggest last week that you should have one RC running just the SVC-8124 fix, unless other fixes have to be applied at the same time. With the user attention this matter is getting it would seem the best approach to make sure there is no other Showstopper bug that gets in the way of it's promotion. Would this be possible? It's a good idea Hitomi and one that we have done before depending on the circumstance. It does however take pre-planning and is harder to do mid-release. The fix would be live right now if it weren't for the blocking issue discovered this weekend and everyone would be happy. To do it now would require us to go back in time. The problem is that the fix needs to be pulled and a special branch made for it which will then go through the entire build/deploy/qa process which takes time. Given that this week had no Monday we lost a lot of the time to set up a special situation like this. We would have had to have started the process last week to get it lined up for a Wednesday release. It's a very complicated set of procedures that each take time. __Oskar Thanks for the reply Oskar. I hope that maybe in future some sort of 'must fix because users are shouting' branch could be set up for similar issues that occur. I actually think your release process works very well (especially remembering how it used to be), but I think this littlle tweak would be useful. :smileyhappy: Often we do. A lot of it depends on how quickly we can hear about it. It usually takes a few days after release for the dust to settle and the real issues to make themselves clear. Then we need to repro them, and investigate fixes. Each step takes time and sometimes we're past the point where that issue can be added to its own branch. Had we been able to find this issue in RC it would have been easy to stop. Once bugs hit main channel it can be a while before they get fixed. The release this week has the fix and is looking good. Tomorrow morning I will suggest creating a separate channel with just that fix in case there are blockers this weekend. __Oskar

Ok change of plans. The code intended for BlueSteel and LeTigre had showstopper bugs discovered on ADITI last night. The code from Magnum was deployed to BS and LT instead. I'm updating the notes now. __Oskar

I updated the BleSteel and LeTigre notes. Both channels will be updated tomorrow if it passes QA tonight. __Oskar

Hitomi Tiponi wrote: I did suggest last week that you should have one RC running just the SVC-8124 fix, unless other fixes have to be applied at the same time. With the user attention this matter is getting it would seem the best approach to make sure there is no other Showstopper bug that gets in the way of it's promotion. Would this be possible? It's a good idea Hitomi and one that we have done before depending on the circumstance. It does however take pre-planning and is harder to do mid-release. The fix would be live right now if it weren't for the blocking issue discovered this weekend and everyone would be happy. To do it now would require us to go back in time. The problem is that the fix needs to be pulled and a special branch made for it which will then go through the entire build/deploy/qa process which takes time. Given that this week had no Monday we lost a lot of the time to set up a special situation like this. We would have had to have started the process last week to get it lined up for a Wednesday release. It's a very complicated set of procedures that each take time. __Oskar

Ok here's the update. Finding that issue on a weekend with a Monday holiday has been very tricky. It messed up our whole release process and schedule this week. All the code that was to go to RC had to be redone. We had to investigate the issue, narrow it down, find a fix for it, build it, deploy it, and test it all in the timeframe of a few hours. This will continue to be tested overnight and we will have one channel ready for deploy Wednesday AM. Magnum will be updated then. The other channels will continue to be QA'd Wednesday for a Thursday morning release. The Magnum channel notes are updated now. __Oskar

Cully Andel wrote: So does this mean 8124 will be fixed this week or not? My land is on SL servers and I don't see anything mentioned? (I don't speak technial, sorry) It does mean that. I'm sorry. When I have more information I'll post it here.

Paratrex, this is a forum thread for the QA team at Linden Lab to talk with residents about current issues in the Release Candidate channels in the attempt to stop these issues from going live. This is not a forum for everyone to whine about how bad they think LL is this week. Please keep your thoughts on topic and productive. If you would like to voice your strong opinions on things unrelated to the server code please create your own forum thread. __Oskar

I appreciate that people need a place to rant, but many comments in this thread are borderline unacceptable. We work hard here and many worked over the weekend on a holiday weekend to make sure things would be ready for a Tuesday morning release. That is how we have done it every other time we've had a holiday on a Monday. I am not sure why you think it would be different this week. A showstopper blocker issue was discovered and we cannot promote it to the main channel. I am sure you can understand the need to stop issues before they reach main channel wherever and whenever we can. __Oskar

Today is a holiday at Linden Lab. I'm getting the release notes out early so I can go back outside and enjoy my day off. There was a blocking issue found in the RC's last week SVC-8208 "L$ received notification not appearing when on an RC region". We had intended to do a release in the AM tomorrow. Much thanks to the resident who got my attention on Saturday so I could escalate emergency investigation into the issue. This disrupts our plans for main channel and RC releases this week. We cannot promote the RC code that we had intended to or release new code to the RC channels. Until everyone gets back to work tomorrow I can't know whether we will be able to have a release candidate for Wednesday morning. Hopefully we can, or we may need to do a Thursday AM release. The code that is on the channels now will stay on there unless I update this thread. Update: We will update the Magnum RC channel Wednesday AM and we will then update the LeTigre and BlueSteel RC channels on Thursday AM. Second Life Server (main channel) There are no changes to main channel. These regions will not be restarted. 2012-09-04, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12    Second Life RC BlueSteel  Showstopper bugs were discovered in QA on ADITI Wednesday night. The code from Magnum was deployed here instead. 2012-09-06, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12   Second Life RC LeTigre This channel has the same code as Magnum. 2012-09-06, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12   Second Life RC Magnum This code is on all three RC channels. Bug Fixes VWR-5044: Attachments only change/inherit the active group when they're "rezzed VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders VWR-20320: Show in search and set for sale remain enabled after owner changed SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location. STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result SVC-7525: Selected objects move when a new keyframe motion is started SVC-7793: Scripted agents can't abandon land on private estates SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side. SVC-7968: When TPing using a landmark the server sends two TeleportStart packets SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938 SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset. SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047 SVC-7641: Add object location info to messages, was "Object on land sending excessive messages SVC-8177: There is different behaivior between the RC channels and the main channel involving permissions, objects lose modify permissions SVC-8208: L$ received notification not appearing when on an RC region   2012-09-05, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12   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!   __Oskar   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   This is not a forum thread for off-topic and unproductive ranting. I will no longer tolerate it. This forum thread is to discuss newly found issues in the Release Candidate channels. If you feel the need to have your opinions heard on topics unrelated to new bugs then please start your own thread. If an individual continues to post unproductive and off-topic comments I will take measures to remedy that. If you are unsure about your posting please read this : "Linden Lab Official:Community Participation Guidelines" https://wiki.secondlife.com/wiki/Issue_Tracker/Conduct

 There is no main channel deploy this Tuesday morning. Each of the RC's had issues last week that we cannot promote. This will delay the promotion of the fix for SVC-8124. The issue is fixed in all three RC's still. Second Life Server (main channel) There are no changes to main channel. These regions will not be restarted. 2012-08-28, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12    Second Life RC BlueSteel This channel will have the same maint-server as last week. Bug Fixes VWR-5044: Attachments only change/inherit the active group when they're "rezzed VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders VWR-20320: Show in search and set for sale remain enabled after owner changed SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location. STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result SVC-7525: Selected objects move when a new keyframe motion is started SVC-7793: Scripted agents can't abandon land on private estates SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side. SVC-7968: When TPing using a landmark the server sends two TeleportStart packets SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938 SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset. SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released 2012-08-29, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12   Second Life RC LeTigre This channel will have infrastructure changes with no modifications to existing behaviour. 2012-08-29, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12   Second Life RC Magnum This is the same maint-server project from last week. Bug Fixes SVC-7641: Object on land sending excessive messages. The messages sent from the simulator about objects now contain location information, making them easier to find and return. SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047 SVC-7641: Add object location info to messages, was "Object on land sending excessive messages" SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released   2012-08-29, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12   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!   __Oskar   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  

The notes are updated for tomorrow's deploy.

https://jira.secondlife.com/browse/SVC-8124 will be fixed on all RC's this week after tomorrow morning's RC roll. __Oskar

  Second Life Server (main channel) The maint-server project from Magnum is being promoted this week.  Bug Fixes llAttachToAvatarTemp fixes llTeleportAgent and llTeleportAgentGlobalCoords fixes Output a script error when a teleport is aborted because the agent to be teleported is not the owner of the object trying to teleport them. SVC-8100: "llTeleportAgent fails silently when user is not the owner" 2012-08-21, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12    Second Life RC BlueSteel This channel will have the same maint-server with bug fixes. Bug Fixes VWR-5044: Attachments only change/inherit the active group when they're "rezzed VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders VWR-20320: Show in search and set for sale remain enabled after owner changed SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location. STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result SVC-7525: Selected objects move when a new keyframe motion is started SVC-7793: Scripted agents can't abandon land on private estates SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side. SVC-7968: When TPing using a landmark the server sends two TeleportStart packets SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938 SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset. SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released 2012-08-22, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12   Second Life RC LeTigre This will have the same bug fixes as are on BlueSteel. 2012-08-22, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12   Second Life RC Magnum This is a maint-server project. Bug Fixes SVC-7641: Object on land sending excessive messages. The messages sent from the simulator about objects now contain location information, making them easier to find and return. SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047 SVC-7641: Add object location info to messages, was "Object on land sending excessive messages" SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) SVC-8136: Attachment point pelvis not being released   2012-08-22, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12   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!   __Oskar   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  

Pandorah Ashdene wrote: You're not serious, are you? My jaw just dropped to the floor. - I am seeing https://jira.secondlife.com/browse/SVC-8124 mentioned nowhere. We are bleeding datatransfer-wise to death, and you are planning "no intentional changes to existing behaviour"? Sorry, I am so angry that I better refrain from posting one more word. We do 4 releases of server per week. The release on Tuesday morning is the main channel promotion. The code that was on LeTigre got promoted. The SVC-8124 issue was newly introduced and is on Magnum only. Magnum bugs get fixed in the Magnum channel. The release notes update you were reading was for the main channel. The SVC-8124 issue is one which we are working on fixing in the Magnum channel. __Oskar

  Second Life Server (main channel) The infrastructure project on LeTigre is being promoted this week. There are no intentional changes to existing behaviour.  2012-08-14, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12     Second Life RC BlueSteel This channel will have the same maint-server with bug fixes. VWR-5044: Attachments only change/inherit the active group when they're "rezzed VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders VWR-20320: Show in search and set for sale remain enabled after owner changed SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location. STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result SVC-7525: Selected objects move when a new keyframe motion is started SVC-7793: Scripted agents can't abandon land on private estates SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side. SVC-7968: When TPing using a landmark the server sends two TeleportStart packets SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938 SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset. 2012-08-15, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12      Second Life RC LeTigre This will have the same bug fixes as are on BlueSteel. 2012-08-15, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12     Second Life RC Magnum This channel will have a different maint-server than the one that is on BlueSteel.   Bug Fixes llAttachToAvatarTemp fixes llTeleportAgent and llTeleportAgentGlobalCoords fixes Output a script error when a teleport is aborted because the agent to be teleported is not the owner of the object trying to teleport them. SVC-8100: "llTeleportAgent fails silently when user is not the owner"   2012-08-15, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12   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!   __Oskar   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  

WolfBaginski Bearsfoot wrote: The number of vehicles that are hanging in mid-air over the Blake sea, stuck at sim boundaries, and the regions that might be down, there's plenty for you to watch. The sim crossing issues caused there will be fixed once pathfinding is on the entire grid.

Marianne McCann wrote: As an estate manager, I am going to be watching our region's performance with the code* first* before I take measures to optimize or disable. Watching and then reacting if need be is a very sensible approach. :-) __Oskar

Ayesha Askham wrote: Oskar As I read this it looks like the code to be rolled to LeTigre is "TBD", since the wording is identical to last week's post, despite date changes. I repeat my question from last week's post: Will the Planned Maintenance, scheduled for 5am PST today interfere with the Roll to Main Server? Considering all the issues with sim performance under Havok 7 physics, rolling this code to Main Server is a risky venture at the least. You must know that many folk are not able to use the project viewer that would enable "turning off" of Pathfinding? I have to say that Linden Lab is beginning to resemble a runaway train, still heading in the original direction, but with no control over what consequences your action may have. The code is the same as last week on LeTigre. That's how we usually do it. If the code is TBD I write TBD. Also if planned maintennance will interfere with server rolls I would tell you. I think in general you should stop worrying so much. :-) __Oskar

Marianne McCann wrote: I'm easily confused: Pathfinding is going out on main, but it not on LeTigre and BlueSteel? Each weeks RC code gets that weeks promotion code added to it. When the RC get updated on Wednesday they will have the pathfinding code in it. __Oskar