[BUG-7202] Scripted objects not derezzing from world when not in line of sight

[sl-service-account]

Steps to Reproduce

This occurs when testing the below mentioned system at any time. Although it has appeared that a sim reset causes this derezzing problem to temporarily abate, this is not consistently the case and sometimes it occurs immediately after a sim reset. So its inconclusive what effect resetiing the sim actually has.

Actual Behavior

In our scripted simulation experience, users teleport from a location approx 300m high inside a building, onto the ground level approx 25m high. Before they arrive a large multiprim object (30-100 prims) simulating a plot of land is given the llDie command and a new fresh multiprim object is rezzed in the same spot. This object is what the users are supposed to interact with in the simulation.
Over the 3 previous years of this project using the same set of scripts and objects, the multiprim objects have been derezzing properly when given the llDie command. The last known verified time that it worked as expected was December of 2013.

This year upon initial walkthroughs of the system in preparation for user participation, it has been noticed by multiple testers that the multiprim scripted objects that had always disappeared as commanded now appear to visually remain. When the user teleports from the building at 300m down to the surface they are still able to see the large object that has been commanded to die on top of the newly rezzed object in the same space. The improperly derezzed object persists until it is selected with the build tool at which point it instantly disappears. If any of the prims in the improperly derezzed object which have a touch event in them are left clicked then just that individual prim of the object derezzes leaving the rest of the object there until the entire object is selected with the build tool.

Expected Behavior

The expectation of course is that objects given the kill command through llDie would fully disappear from any users view.

Other information

It appears from some testing that if the user is within line of sight of the object when it is given the kill command, then the object properly derezzes for that user. This means that a user who teleports to the object from outside of line of sight may still see the improperly derezzed object while standing next to user who does not see the object because they were within line of site when the kill command was given. In the actual simulation experience, the user will never be in line of sight of the object when it is told to derez.

Links

Related

• [BUG-7084] Prim properties visually revert to an earlier state since Interesting #14831

Duplicates

• [BUG-7084] Prim properties visually revert to an earlier state since Interesting #14831

Original Jira Fields

Field	Value
Issue	BUG-7202
Summary	Scripted objects not derezzing from world when not in line of sight
Type	Bug
Priority	Unset
Status	Closed
Resolution	Duplicate
Reporter	Random Cole (random.cole)
Created at	2014-09-05T17:48:09Z
Updated at	2018-12-24T11:08:13Z

{
  'Business Unit': ['Platform'],
  'Date of First Response': '2014-09-05T17:28:30.631-0500',
  "Is there anything you'd like to add?": 'It appears from some testing that if the user is within line of sight of the object when it is given the kill command, then the object properly derezzes for that user. This means that a user who teleports to the object from outside of line of sight may still see the improperly derezzed object while standing next to user who does not see the object because they were within line of site when the kill command was given. In the actual simulation experience, the user will never be in line of sight of the object when it is told to derez.',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'In our scripted simulation experience, users teleport from a location approx 300m high inside a building, onto the ground level approx 25m high. Before they arrive a large multiprim object (30-100 prims) simulating a plot of land is given the llDie command and a new fresh multiprim object is rezzed in the same spot. This object is what the users are supposed to interact with in the simulation.\r\nOver the 3 previous years of this project using the same set of scripts and objects, the multiprim objects have been derezzing properly when given the llDie command. The last known verified time that it worked as expected was December of 2013.\r\n\r\nThis year upon initial walkthroughs of the system in preparation for user participation, it has been noticed by multiple testers that the multiprim scripted objects that had always disappeared as commanded now appear to visually remain. When the user teleports from the building at 300m down to the surface they are still able to see the large object that has been commanded to die on top of the newly rezzed object in the same space. The improperly derezzed object persists until it is selected with the build tool at which point it instantly disappears. If any of the prims in the improperly derezzed object which have a touch event in them are left clicked then just that individual prim of the object derezzes leaving the rest of the object there until the entire object is selected with the build tool.',
  'What were you doing when it happened?': 'This occurs when testing the above mentioned system at any time. Although it has appeared that a sim reset causes this derezzing problem to temporarily abate, this is not consistently the case and sometimes it occurs immediately after a sim reset. So its inconclusive what effect resetiing the sim actually has.',
  'What were you expecting to happen instead?': 'The expectation of course is that objects given the kill command through llDie would fully disappear from any users view.',
}

[sl-service-account]

NeoBokrug Elytis commented at 2014-09-05T22:28:31Z

It's not just multi-prim stuff, it's single prim stuff too. From my experience the items are still visible client side to those who originally saw the item, and once clicked disappear. I suspect it's a Project Interesting issue.

[sl-service-account]

Whirly Fizzle commented at 2014-09-06T00:48:28Z

Possibly related to BUG-7084 ?

I have also noticed on interesting enabled viewers that if a Resident deletes an object or returns an object or edits an objects position while you do not have this object within your line of sight, when you change camera position so the object is within your line of sight, the object will still be rendered on your screen when it is no longer on the region and if the objects position was changed, you will still see the object in its old position.
Editing on the object will make it disappear if it was deleted/returned and will make it pop into its correct location if it's position was changed.
So I do not think this glitch applies to only scripted objects and I am positive this is new on interesting enabled viewers.

[sl-service-account]

Whirly Fizzle commented at 2014-09-06T00:53:12Z

For testing:

• Pre-interesting viewer: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.7.289441 (last build before Interesting)
• Post-interesting viewer: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.7.289461 (first Interesting release)

[sl-service-account]

Marissa Linden commented at 2014-09-08T22:20:29Z

This appears to be a dupe of BUG-7084. I'm linking it up to that bug, and closing out as a dupe.