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.
I create a complex scripted device called "Peanut No. 9" (formerly OpenCollar, often referred to OC, P9 or "peanut collar") that adds interactivity features to avatars.
The device is carefully designed to prevent link message spam inside of its root. I designed it to have 6 "cores", those are the objects root and 5 child-links.
Directing link messages to child-links allowed me to radically cut down on unnecessary script events. My device has been robust for many years.
One of the child-links includes the module that is used to create dialog menus. When the device is touched, or the correct command is used on a chat channel, it serves the main menu.
Although this logic has been robust for years and never failed, it appears to now fail at random on simulator versions Second Life Server 2019-10-03T01:12:11.531528 and Second Life Server 2019-10-11T18:12:36.531693.
My educated guess is that the problem resides in the server's event queue because upon teleporting to an unaffected region my device serves me as many dialog menus as I requested by touch/command in the previous region, one after another.
I'm convinced that this is a wide-spread problem that may negatively affect content such as scripted attachments, texture change HUDs, avatar body HUDs and possibly even furniture objects.
What were you doing when it happened?
In the last couple of days I have been investigating an issue where script events in child-links appear to fail at random after having received many complaints and problem reports from my customers.
I was testing my product in regions with server version Second Life Server 2019-10-11T18:12:36.531693.
Something has changed since the grid rollback on September 28, 2019.
What were you expecting to happen instead?
I was expecting my device to serve a dialog menu.
Other information
I have attached a fully functional export of the peanut core that can be imported to Second Life. It may be a good testing device for this issue in general as it relies heavily on parent-link/child-link link message events.
Script events in child-links appear stuck in event queue
Type
Bug
Priority
Unset
Status
Closed
Resolution
Duplicate
Reporter
Wendy Starfall (wendy.starfall)
Created at
2019-10-21T19:59:46Z
Updated at
2019-10-22T20:23:09Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
"Is there anything you'd like to add?": 'I have attached a fully functional export of the peanut core that can be imported to Second Life. It may be a good testing device for this issue in general as it relies heavily on parent-link/child-link link message events.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'I create a complex scripted device called "Peanut No. 9" (formerly OpenCollar, often referred to OC, P9 or "peanut collar") that adds interactivity features to avatars.\r\n\r\nThe device is carefully designed to prevent link message spam inside of its root. I designed it to have 6 "cores", those are the objects root and 5 child-links.\r\n\r\nDirecting link messages to child-links allowed me to radically cut down on unnecessary script events. My device has been robust for many years.\r\n\r\nOne of the child-links includes the module that is used to create dialog menus. When the device is touched, or the correct command is used on a chat channel, it serves the main menu.\r\n\r\nAlthough this logic has been robust for years and never failed, it appears to now fail at random on simulator versions `Second Life Server 2019-10-03T01:12:11.531528` and `Second Life Server 2019-10-11T18:12:36.531693`.\r\n\r\nMy educated guess is that the problem resides in the server\'s event queue because upon teleporting to an unaffected region my device serves me as many dialog menus as I requested by touch/command in the previous region, one after another.\r\n\r\nI\'m convinced that this is a wide-spread problem that may negatively affect content such as scripted attachments, texture change HUDs, avatar body HUDs and possibly even furniture objects.',
'What were you doing when it happened?': 'In the last couple of days I have been investigating an issue where script events in child-links appear to fail at random after having received many complaints and problem reports from my customers.\r\n\r\nI was testing my product in regions with server version `Second Life Server 2019-10-11T18:12:36.531693`.\r\n\r\nSomething has changed since the grid rollback on September 28, 2019.',
'What were you expecting to happen instead?': 'I was expecting my device to serve a dialog menu.',
'Where': 'http://maps.secondlife.com/secondlife/Davos/128/128/143',
}
The text was updated successfully, but these errors were encountered:
What just happened?
I create a complex scripted device called "Peanut No. 9" (formerly OpenCollar, often referred to OC, P9 or "peanut collar") that adds interactivity features to avatars.
The device is carefully designed to prevent link message spam inside of its root. I designed it to have 6 "cores", those are the objects root and 5 child-links.
Directing link messages to child-links allowed me to radically cut down on unnecessary script events. My device has been robust for many years.
One of the child-links includes the module that is used to create dialog menus. When the device is touched, or the correct command is used on a chat channel, it serves the main menu.
Although this logic has been robust for years and never failed, it appears to now fail at random on simulator versions
Second Life Server 2019-10-03T01:12:11.531528
andSecond Life Server 2019-10-11T18:12:36.531693
.My educated guess is that the problem resides in the server's event queue because upon teleporting to an unaffected region my device serves me as many dialog menus as I requested by touch/command in the previous region, one after another.
I'm convinced that this is a wide-spread problem that may negatively affect content such as scripted attachments, texture change HUDs, avatar body HUDs and possibly even furniture objects.
What were you doing when it happened?
In the last couple of days I have been investigating an issue where script events in child-links appear to fail at random after having received many complaints and problem reports from my customers.
I was testing my product in regions with server version
Second Life Server 2019-10-11T18:12:36.531693
.Something has changed since the grid rollback on September 28, 2019.
What were you expecting to happen instead?
I was expecting my device to serve a dialog menu.
Other information
I have attached a fully functional export of the peanut core that can be imported to Second Life. It may be a good testing device for this issue in general as it relies heavily on parent-link/child-link link message events.
Attachments
Links
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: