Any of your scripts break after rolling restart?

A tenant is in the process of moving a large build from one of my islands to another one where she has more space. This morning she IMmed me saying that a script of hers that was working fine on her old island just hours before was only working sporadically on the new island- a half-empty class 5 that I had set aside for just her and one other tenant. I asked her to take a prim running the script back to the old island and see if it worked again. She tested it and reported that no, it wasn't working at the old location either- and neither was any part of her old build that used the script, even though everything was fine there yesterday.

I know that some of my islands have been restarted already, but I don't have restart trackers on the newer ones yet... but I'm seriously wondering whether the server updates really did have some "resident-facing differences" after all. What are your experiences so far?

reset

As above post stated. I had some scripts that needed reset also. After the scripts were reset, performed as excepted.

Which scripts in particular?

Geez, yes. I had poseball scripts break and a texture changing script. Resetting the poseballs worked, but I had to completely rebuild the prims with the texture script.

Nothing I love so much as customer IM's from the store "hey, your stuff doesn't work..."

edit: beat me to it..

Or are there certain llCalls that are causing problems with this upgrade?

Is there a JIRA yet for this?

Has somebody poked Propsero or some other Release Linden and told them that there may be a nasty issue here? Asking scripters to reset stuff is one thing, asking everybody else on the grid to reset scripts is a very different story.

I have more information, and my tenant is convinced it is due to a fix rolled out in the restart. Her script uses the collision_start event, and she says the event is definitely being handled differently now.

I know there were collision bugs in recent releases, and that some dev work has gone into that, so it looks like some of their collision work might have sneaked into this build. But according to my tenant, this particular change alters the way the event has been handled for years- not just something that broke in the last couple releases.

Maybe somebody in-world or who has access to live chat can point a Linden to this forum thread?

From what Isablan says above, this sounds like it might be more than collision events that have gone south..

I had a strange script issue this morning myself. I was attempting to create a simple teleporter to a workshop skybox, maybe it was while some rolling restarts were going on, maybe not...but the script at first wouldn't even load for me to put my coordinates in. After finally it did load and I managed to put in my skybox destination, I sat on it and was tossed across the sim about 4 parcels away. Yes, I did click reset before sitting as well.

If you can confirm there's a problem, please create an issue using our issue tracker (http://jira.secondlife.com). Include as much information as possible so that we can reproduce the problem. Post the contents of a short script that demonstrates the different behavior, and describe what behavior is different between 1.22.3 and 1.22.4. Also indicate in which regions you tested it.

I will alert my tenant to do just that. Thanks.

Thanks, Propsero!

TY, Prospero!


Or, for those here that aren't scripters and/or aren't used to JIRA, you could post details here on objects that needed their scripts reset after this weeks rolling restart (ie, not viewer crashes, inventory loss, etc) and others can probably do up a JIRA for you.

just bumping this one because it seems like an important issue that people will need to be aware of as more regions get restarted.

So.. A Linden was lured to the forums.. (TY, Propsero)

Did anybody actually report a JIRA or find something conclusive about this sim upgrade causing problems?

I am not sure whether this merits a JIRA, as it appears to be an undocumented fix in the way collision events are handled. It CAN break some existing scripts that were using the events based on how they actually behaved, rather than how they were SUPPOSED to behave. My tenant had this to say:

That almost rhymes with what LL said broke Siggy's TheSwimmer swimming AO. Maybe I should dust mine off and see if it works now..

It is very common for poseball scripts to break if the poseballs are being used at the time a sim goes down, be it a rolling restart or a sim crash.
Because the script is frozen at the time of the crash/restart, it does not get to register the avatar on the poseball leaving the poseball, thus when the sim comes back up the script still thinks there is an avatar to animate and often gets stuck in an endless "trying to animate but PERMISSION_TRIGGER_ANIMATION not set" or words to that effect.
The poseball may or may not be spamming this error, sometimes they just remain invisible and refuse to work, or visible and refuse to work, it takes a few forms.

This problem has existed as long as I can remember, 2 years ago the break was often permanent, the ball prim itself would become totally unuseable as a sit target and the only way to fix it was to make a new ball prim and put the originals contents into it, these days it seems a reset of the script almost always fixes the problem.

Having said this I have seen the above still happening VERY rarely, it could be what happened with the items mentioned that did not respond to a script reset, I know its not just poseballs that are effected by sim crashes/restarts while being used, but obviously poseballs are the ones Im most familiar with.

no scripts broke but objects moved....

we even found a hammock in the sky!