ID:2433447
 
Resolved
Visual contents could mistakenly not get used when removing an object from the visible map and adding it to client.screen at the same time. Conversely, visual contents would not reset when adding an object to the visible map and removing it from client.screen at the same time. (The fix for this issue impacts both client and server.)
BYOND Version:512
Operating System:Windows 7 Home Premium 64-bit
Web Browser:Firefox 52.0
Applies to:Dream Daemon & Dream Seeker
Status: Resolved (512.1465)

This issue has been resolved.
Descriptive Problem Summary:

Numbered Steps to Reproduce Problem:
1. Launch using Dream Deamon so you are able to reconnect
2. Click on box, you should now see a ! on the box on your screen (you likely wont)
3. Relog, you can now see the ! on the box on your screen
4. Click on box on screen, it will move to the floor, you should not see a ! (you likely will)
5. Relog, the ! is now not seen


Code Snippet (if applicable) to Reproduce Problem:
https://www.dropbox.com/s/58fg772rmosyo7p/ vis_contents_issues_client_screen.zip?dl=1

Expected Results:
The ! shows up when added to the box's vis_contents and vanishes when removed

Actual Results:
The ! refuses to show up or vanish properly


Does the problem occur:
Every time? Or how often?: Every Time
In other games?: Yes
In other user accounts?: Yes
On other computers?: Yes


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.)
Under 1462 the ! would correctly show up when the box was placed on screen, however it would not vanish when the box was removed from the screen

1463 acts the same as 1364


Lummox JR resolved issue with message:
Visual contents could mistakenly not get used when removing an object from the visible map and adding it to client.screen at the same time. Conversely, visual contents would not reset when adding an object to the visible map and removing it from client.screen at the same time. (The fix for this issue impacts both client and server.)