ID:2145447
 
Resolved
BYOND Version:511.1355
Operating System:Windows 8
Web Browser:Chrome 52.0.2743.116
Applies to:Dream Seeker
Status: Resolved

This issue has been resolved.
Descriptive Problem Summary:
It seems as though areas which cover a large area aren't being displayed if the map control size (or client view?) is updated.

http://i.imgur.com/2hxD1Lx.jpg - This is how the map initially appears. All of the shaded/lighted parts are areas.
http://i.imgur.com/ixAuBjt.jpg - After the map size is updated, for example by messing with the window size. Note the small, 2-tile wide dark space between the first arc; this is also an area exclusive to this z-level, but it appears just fine with the proper color/etc.
http://i.imgur.com/rwt8UMh.jpg - Going back into preferences, turning off hardware mode, and then turning it back on will show the areas once again.

While the areas are displaying I can move around, even to different z levels and so on, and the areas will remain displayed. But if I drag the window size or call the proc that updates the map/client view size, even if it doesn't change, it will stop displaying the areas.

If I had to guess, maybe the changes to the message format in 511.1353 have something to do with this, because I downloaded 511.1352 and this issue does not occur in that version.

Expected Results:
Areas don't disappear from the client's view if they're large or 'originate' from a different z level.

Actual Results:
They disappear from the client's view.

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

When does the problem NOT occur?
When using 511.1352, or when the area originates on the same z-level as the client's view (I'm guessing here).

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.)

511.1352

Workarounds:

Do you have a test project that shows this in action? It would be much easier to solve that way.
Any news on this? Obviously I consider this a big deal but I have nothing to investigate yet.
Sadly I'm having trouble reproducing this in a test environment. I've been toying around to try and figure out why over the last few days, including making adjustments on the actual environment it does work on, so I could reproduce it in the testing environment and get it to you.

All I've found so far is that it only occurs when I have the area's blend_mode set to 4; if I change the blend_mode to 1, it shows up on the map just fine without having to change any rendering modes, and if it's set to that it doesn't disappear when the map size or client view changes.
A full environment is fine if you have source and can give me full instructions on how to get to a spot where the bug can be reproduced reliably.
I would just like to report that this issue is no longer occurring in the 511.1360 beta that was released recently.
Good to know. I'll change this to Resolved for now but if it recurs, please let me know and provide a test case.
Lummox JR resolved issue