You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug happens when a screen is multi-parented to a prop and happens to be partially inside another prop. The prop the screen is inside of will show up over the display, even if the screen's prop is barely touching it.
Steps to reproduce the behavior:
Place down two props and a screen (any screen model, preferably something like the computer monitor).
No-collide the first prop with the screen and place the screen partially inside of the prop, making sure the area of contact is very small.
Multi-parent both the first prop and the screen to the second prop (settings should equal weld).
The screen's display will be covered up by the first prop.
The behavior I expected from the screen was it to show up over the first prop, as the display wouldn't normally be covered. I assume this is a bug pertaining to how the screen is rendered.
P.S. I checked if the display was just normally being covered by the prop, nope! The display is far enough away from Prop 1 that it shouldn't be covered.
Screenshot of what's happened below.
The text was updated successfully, but these errors were encountered:
I assume this is most likely a game issue, but I won't dismiss this entirely. Respawning the screen has solved this for me before.
Hi, thanks for the advice. When I dupe the props and stuff it fixes the issue. I wouldn't regard this bug as anything too high-priority, more of just a thing my OCD mind noticed.
This bug happens when a screen is multi-parented to a prop and happens to be partially inside another prop. The prop the screen is inside of will show up over the display, even if the screen's prop is barely touching it.
Steps to reproduce the behavior:
The behavior I expected from the screen was it to show up over the first prop, as the display wouldn't normally be covered. I assume this is a bug pertaining to how the screen is rendered.
P.S. I checked if the display was just normally being covered by the prop, nope! The display is far enough away from Prop 1 that it shouldn't be covered.
Screenshot of what's happened below.
The text was updated successfully, but these errors were encountered: