ID:2422596
 
Resolved
When told to forget about an obj or mob, the client would sometimes incorrectly hold onto its list of visual contents. This tended to happen in situations where the object was moved out of view rather than deleted outright.
BYOND Version:512.1462
Operating System:Windows 7 Pro 64-bit
Web Browser:NA
Applies to:Dream Seeker
Status: Resolved (512.1463)

This issue has been resolved.
Descriptive Problem Summary:
Sometimes removing something from an object's vis_contents will cause it to remain on the client, seems to generally involve the object's loc changing directly after the vis_contents change.

Numbered Steps to Reproduce Problem:
1. Place object B in vis_contents of object A
2. Remove B from vis_contents of A (but dont del it) and move A into object C
3. Move A out of C, B will still be visible on A despite not being in A.vis_contents, note: relogging will fix this


Code Snippet (if applicable) to Reproduce Problem:
https://www.dropbox.com/s/eli6iyg1xed7i9b/ vis_contents_issues.zip?dl=1
Once you compile and launch it hit the "start vis_contents test" verb

Expected Results:
Things removed from an object's vis_contents will no longer show up as if in the object's vis_contents list.

Actual Results:
The thing removed is still visible as if it were in vis_contents to some clients.

Does the problem occur:
Every time? Or how often?
Every time
In other games?
Yes
In other user accounts?
Yes
On other computers?
Yes, tested with one other user in the linked code and 100+ in another project

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Didn't test anything earlier than 512.1454 where it did show up
Lummox JR resolved issue with message:
When told to forget about an obj or mob, the client would sometimes incorrectly hold onto its list of visual contents. This tended to happen in situations where the object was moved out of view rather than deleted outright.