ID:2662412
 
Not a bug
BYOND Version:514.1549
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 88.0.4324.190
Applies to:Dream Maker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary: Some weird stuff happening. I posted recordings of the issue on Discord.

Discord:
https://discord.com/channels/725444629172060262/ 725458744711839873/818630883451600927

Edited to include images here, for non-Discord users:
Incorrect results: https://puu.sh/HnoHA/490439ba44.mp4
Correct results: https://puu.sh/HnoHy/8e062dd1a8.mp4

Numbered Steps to Reproduce Problem:
  1. Run the test case
  2. Use test1 verb
  3. Observe the screen/viewport. You should notice the screen has shrunken.
  4. Use test2 verb
  5. Observer the screen/viewport. You should notice a mirrored viewport appear.


Expected Results:
Viewport goes crazy and becomes smaller.

Actual Results:
User's screen becomes messed up.

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

When does the problem NOT occur?

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

This problem DID NOT OCCUR in 1546.

Test case: https://www.dropbox.com/s/etzimnkak9jhzcn/ SG%20Playground_src.zip?dl=0
Can you edit your post to include a full build number? This is required for all Beta Bugs reports.

This likely relates to id:2653867 BTW. You can fix some of your problems by changing your viewport object's screen_loc to "CENTER"; the old "1,1" was a bug. I'm still seeing a problem when doing test1 and test2 together where there's some odd duplication at the top of the screen, so I'm looking into that.
Actually on further investigation I'm not sure this is a bug at all. After correcting the viewport's screen_loc to "CENTER", I then saw you were defining map_layer with a pizel_z value, which I'm sure was to account for the old buggy behavior. Once I removed that pixel_z offset as well, everything worked flawlessly.
Gotcha, thanks for your time.
Lummox JR resolved issue (Not a bug)