You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
First noticed around 12:00 SL time on 11th September, scripts seem to stop working in physical vehicles. Not all scripts, just certain scripts. And it is not predictable which scripts. For example, I have been putting a script monitor script inside my vehicles. Sometimes that stops (and therefore returns no result), but sometimes it is not stopped, so I can see where other scripts did stop.
What were you doing when it happened?
These are happening to automated vehicles. It happens whether or not the vehicles have a rider at the time. However, it does not appear to happen if the vehicles are run non-physical.
What were you expecting to happen instead?
I was expecting the scripts to keep running
Other information
Here is a sample of the logs which might help:
2019-09-25 19:03:06 S1-DB1-288: SCRIPT CHANGED STATE. Script: Asynchronous ops v1.1.1 Position: Maroon <3.29594, 60.50553, 40.68484>. State now 0
2019-09-20 23:53:31 H4-Cal-1196: SCRIPT CHANGED STATE. Script: Anti-griefer V2.1.6 Position: Lutra <5.10418, 181.60810, 65.80029>. State now 0
2019-09-20 23:36:51 H2-Cal-1538: SCRIPT CHANGED STATE. Script: Pod locaton+direction reporter v1.13 Position: Crumbi <24.97742, 221.77670, 75.33215>. State now 0
Scripts stop working for physical objects in certain conditions
Type
Bug
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Yavanna Llanfair (yavanna.llanfair)
Assignee
Mazidox Linden (mazidox.linden)
Created at
2019-09-26T19:48:21Z
Updated at
2019-12-10T22:47:38Z
{
'Build Id': '2019-12-04T20:29:26.533447',
'Business Unit': ['Platform'],
'Date of First Response': '2019-09-26T15:27:02.316-0500',
"Is there anything you'd like to add?": 'Here is a sample of the logs which might help:\r\n2019-09-25 19:03:06 S1-DB1-288: SCRIPT CHANGED STATE. Script: Asynchronous ops v1.1.1 Position: Maroon <3.29594, 60.50553, 40.68484>. State now 0\r\n2019-09-20 23:53:31 H4-Cal-1196: SCRIPT CHANGED STATE. Script: Anti-griefer V2.1.6 Position: Lutra <5.10418, 181.60810, 65.80029>. State now 0\r\n2019-09-20 23:36:51 H2-Cal-1538: SCRIPT CHANGED STATE. Script: Pod locaton+direction reporter v1.13 Position: Crumbi <24.97742, 221.77670, 75.33215>. State now 0',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'First noticed around 12:00 SL time on 11th September, scripts seem to stop working in physical vehicles. Not all scripts, just certain scripts. And it is not predictable which scripts. For example, I have been putting a script monitor script inside my vehicles. Sometimes that stops (and therefore returns no result), but sometimes it is not stopped, so I can see where other scripts did stop.\r\n',
'What were you doing when it happened?': 'These are happening to automated vehicles. It happens whether or not the vehicles have a rider at the time. However, it does not appear to happen if the vehicles are run non-physical.',
'What were you expecting to happen instead?': 'I was expecting the scripts to keep running',
'Where': 'See log entries for locations. Sims believed affected include:\r\nMaroon, Lutra, Crumbi, Agrius, Maia, Veloxm, Celerino',
}
The text was updated successfully, but these errors were encountered:
Except that I have been seeing it, not as a new object rezzes, but as an object registers in a new sim. I imagine the cause and effect are exactly the same. It's good to know it's been spotted elsewhere and will be fixed!
Yavanna Llanfair commented at 2019-11-23T22:14:08Z
Adding to this now because it's still happening, at locations around the SLRR. I don't know why it is particularly an issue there, though.
I'll add to this as I notice places, but one such is the crossing from Hooktip (Second Life Server 2019-11-01T18:02:37.532376) to Tussock (Second Life Server 2019-11-15T21:13:13.532828)
What just happened?
First noticed around 12:00 SL time on 11th September, scripts seem to stop working in physical vehicles. Not all scripts, just certain scripts. And it is not predictable which scripts. For example, I have been putting a script monitor script inside my vehicles. Sometimes that stops (and therefore returns no result), but sometimes it is not stopped, so I can see where other scripts did stop.
What were you doing when it happened?
These are happening to automated vehicles. It happens whether or not the vehicles have a rider at the time. However, it does not appear to happen if the vehicles are run non-physical.
What were you expecting to happen instead?
I was expecting the scripts to keep running
Other information
Here is a sample of the logs which might help:
2019-09-25 19:03:06 S1-DB1-288: SCRIPT CHANGED STATE. Script: Asynchronous ops v1.1.1 Position: Maroon <3.29594, 60.50553, 40.68484>. State now 0
2019-09-20 23:53:31 H4-Cal-1196: SCRIPT CHANGED STATE. Script: Anti-griefer V2.1.6 Position: Lutra <5.10418, 181.60810, 65.80029>. State now 0
2019-09-20 23:36:51 H2-Cal-1538: SCRIPT CHANGED STATE. Script: Pod locaton+direction reporter v1.13 Position: Crumbi <24.97742, 221.77670, 75.33215>. State now 0
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: