ID:2655083
 
Resolved
Using plane masters caused non-HUD objects not to clip when outside the normal map area.
BYOND Version:513
Operating System:Windows 10 Pro 64-bit
Web Browser:Chrome 88.0.4324.146
Applies to:Dream Seeker
Status: Resolved (514.1547)

This issue has been resolved.
Descriptive Problem Summary:

If a client's screen contains screen objects whose screen loc values are below (1,1) and there is also a plane_master on the client's screen, the viewport will render all turfs on the rows occupied by the screen objects whose values are less than 1,1.

Ordinarily those turfs are not interactable, but if one uses render_target and render_source to display the plane on the client's screen they become interactable.

Numbered Steps to Reproduce Problem:

1. Add an object to the client's screen with a screen_loc that is less than (1,1)- for example: (0,1)
2. Add a plane_master to the client's screen.
3. Behold as the viewport expands.

Expected Results: The game will not render additional turfs.

Actual Results: It does.

Has always occurred since these features (plane_master and now render_target) were added.

Workarounds: Create black boxes to block out the newly rendered areas or put HUD in a different map element entirely. Not great solutions though.
This is definitely gonna need a test case.

I'm currently looking into your other issue pairing plane master render targets with KT groups, so it's related but doesn't have the screen offset issue.
Lummox JR resolved issue with message:
Using plane masters caused non-HUD objects not to clip when outside the normal map area.