Lucia Nightfire

I would look into whether the region's TD/FPS was significantly lagged or if the region was running in idle mode. These two scenario's can cause physics to drift farther than a script can deter if said script was using low polling of operation.

I've noticed a definite increase. Where sims I regularly monitor crash unexpectedly every 2 - 3 days, they're now doing it multiple times a day. This has been going on since last week and on all channels. I've let support know about the times and regions its occurred and asked them to pass on the information to the engineers. Its a roll of the dice if thats ever done though as most times support will try to decipher what caused the crash in the first place and usually won't bother sending information if they've made up their mind what happened. I've on many occasions notified support of down regions with full knowledge why they went down only to be told a reason entirely unrelated to how or why it happened. Sadly, I can only take their word that the proper information is passed on to the proper people. Lets hope that is the case with these recent crashes.

Seems that the release on the RC channels has brought about an annoying bug that effects control event triggering in attachment's child prims after changing regions. There are two different effects depending how you enter a version 13.05.14.275813 RC region. After going into an RC region while using any controls, those controls will lock under execution and remain locked until you reset the script or the control perms or detach the object. After going into an RC region without using controls like with a teleport, the control event will not trigger when attempting to use any controls until you re-request/re-grant control perms or go back to a main channel region. I discovered this today when using my dasher HUD which has been a child prim in my main HUD for several years now. https://jira.secondlife.com/browse/BUG-2601

I think this is what is requested & what we need: https://jira.secondlife.com/browse/SVC-7244

slplugin.exe has to be running for your viewer to get the text of the TOS at login which will then enable the agree button. I purposely block the loading of slplugin.exe and had to temporarily allow it just so I could accept the terms, then reblock it again.

Seems we picked up a bug in 13.04.05.273580 for Bluesteel as requesting PERMISSION_OVERRIDE_ANIMATIONS from an attachment now generates a permissions request dialog. Will wait on LeTigre regions to restart to see if they do it with the new version. I guess I see why now. We lost the Animation Override code with this version change. And just when I started working with making an AO...

I will say I'm glad that 13.03.22.272565 got the update to pathfinding. Now there is no AI Step Time consuming physics timing if there are no PF characters present in the region. That means regions without PF characters can perform as if PF was disabled. Of course, once a single PF character is introduced to a region, it can expect to take a 3 - 4ms hit to physics timing depending on how many objects are set to Movable Obstacle, but at least resources are no longer wasted when PF characters are absent. Thanks for that much needed revision.

Heres an old jira about the issue. Granted you can't comment anymore. https://jira.secondlife.com/browse/SVC-7959 More and more people seem to use the term "rollback" to describe the server time loss that occurs. Traditionally, a rollback means returning to a prior server version after discovering critic bugs in the new version that was rolled out.

Theres also issues with 13.01.14.269010 version regions while they are caching. During region caching, parcel data is not updated for agents that teleport into the region. It remains that of the last parcel you were on in the region you came from. Land owners or staff cannot change parcel settings, check prim counts, return prims via the prim owner's list, check the access list or banlist or add/remove agents via the access list or banlist. Agents are able to fly +/- 128 meters outside of the region boundaries and cannot region cross into other regions. Attempting to teleport out results in a crash. https://jira.secondlife.com/browse/BUG-1516

I saw SEC-1215 happening on 12.12.18.268345. But the crashing after use of moderation functions I've only seen on version 13.01.14.269010. I run sandboxes in many regions, and we have them on all channels. Last two weeks crashes after moderation function use were only happening in regions on server version 13.01.14.269010. Since Main Channel began using version13.01.14.269010 today, I've had three crashes on the same main channel region immediately after send homes and temp bans were made.

Another thing that got promoted from BlueSteel regions is a crash mode with agent departure from regions upon their send home, ban and/or ejection. I expect the frequency of these crashes will now increase grid-wide thanks to there being no resolution on this issue yet. I'm already seeing an increase now. References: https://jira.secondlife.com/browse/SEC-1204 Related: https://jira.secondlife.com/browse/SEC-1215

I wish these random region crashes could be ironed out. I have stats open almost all the time and don't see any indication of why they occur. Just ding and its over. Region comes up within 1 - 2 minutes, but of course has who knows how much server time loss. Had one earlier that lost almost two hours. Had a region just crash and restart while only being up after a few hours after today's roll. Theres several MAINT work orders open on these, but many have no solid leads on the causes. Truly frustrating.

I'm seeing repeated crashing as well as periodic caps failure-like conditions in many RC regions where rezzing, attaching from inventory, url granting, teleporting, region crossing and login to region all fail. The region, Mauve has crashed 6 times as of this writing and the region, Columbia at least twice since their rolls to the new server version today. Both have had caps failure-like conditions periodically.

OK, now seeing this too. After being offline for a few hours, my objects stopped having their IMs go to my email.

I have objects that have IM'd me from Magnum, LeTigre and Blue Steel while offline and they have gone to my email. Strange how only certain people are affected.

I created a feature request that will allow land owners/moderators to input where the ceiling for visibility over the same parcel starts (50 - 5000 meters) above ground. It will give land owners more flexibility. https://jira.secondlife.com/browse/BUG-951 Its currently in review.

On Magnum regions, llSensor() and llSensorRepeat() using moderate to long ranges (24m - 96m) are not detecting agents or objects closest to the object the sensor script is in. This is affecting all sensor types; ACTIVE, PASSIVE,SCRIPTED. Please investigate the cause. Thanks.

Two Magnum regions I monitor have had restarts (apparently two crashes each at least) in the last hour. They now are experiencing issues with HTTP and email in and out failure, object rendering and updating failure (attached and rezzed), capabilities for agents failing as well (can't access about land parameters). Just a heads up. Now seeing an issue with agents ghosting when attempting to leave these regions.