ID:2077329
 
BYOND Version:510.1340
Operating System:Windows 10 Pro 64-bit
Web Browser:Firefox 46.0
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:

An /image added to client.images does not update after having its icon_state changed, unless something else in the map view changes, such a normal atom in the view changing its appearance.

Numbered Steps to Reproduce Problem:

1. Create a new /image with a specified loc.
2. Add it to client.images such that it will appear in the world.
3. Set icon_state on the /image without otherwise changing the state of anything in view.

Code Snippet (if applicable) to Reproduce Problem:
/world
fps = 25
maxx = 8
maxy = 8
maxz = 8

/atom/icon = 'flicker.dmi'

/turf/icon_state = "turf"

/mob
icon_state = "mob"
var/image/I

/mob/Login()
..()
I = image('flicker.dmi', new /turf(locate(1, 1, 1)), "0")
client.images += I

spawn()
loc = locate(4, 4, 1)
while(1)
I.icon_state = "0"
sleep(1)
I.icon_state = "1"
sleep(1)


I've made a test project to demonstrate the issue at https://mega.nz/#!VYsijJga!9o51SsK_MUge0xN_efQqBPkSKBePxApOp gPvafQU-wI. The circle in the bottom-left of the world should be flickering between a picture of 0 and 1 every frame. It does so in 510.1339, but you have to move the little mob arrow around in 510.1340 in order for it to change.

Expected Results:

For the image to visually update in accordance with icon_state.

Actual Results:

The image does not update unless an atom in the world does.

Does the problem occur:
Every time? Or how often? It happens in any game that uses dynamic client.images.
In other games? SS13
In other user accounts?
On other computers?

When does the problem NOT occur? It reliably occurs on my computer.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?

This issue did not occur in 510.1339.

Workarounds:

Spam movement etc.
I'll test your project out Monday to be sure, but I'm pretty sure this is a duplicate of id:2076729 and has a fix already.
Both of those are probably duplicates of id:2075483 then, because they sound similar and it was posted first, though it somehow got buried.
510.1341 appears to have fixed the problem. Thank you Lummox.