New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
510 Stable doesn't render planes right for some people #21264
Comments
So this is fixed in the very latest beta build of 511. I got through like 95% of the byond bug report before I realized this... I'm posting it here because I did too much work not to post it somewhere. THAT SAID: we're currently requiring some part of the playerbase to use the beta build of byond to properly render the game. This is "very bad"™ and we REALLY should remove the use of planes until 511 properly goes gold at the very least! Descriptive Problem Summary: When this occurs the previous plane image becomes static, and moves with the player until a new plane (usually also frozen) takes its place. This is a little hard to picture so here's a visual. 1. How the surrounding area looks. 2. The player initially spawns to the immediate right of the blue wall, hidden black tiles to the west as expected. 3. As the player moves to the eastern grey wall the image from 2 remains static on the screen, the actual motion of the tiles properly shown only on the hidden black tiles from number 2. 4. After a while (erratic, up to 20 seconds!) the static overlay updates, showing the true visuals for standing at the eastern wall. Note that you can make image 3 by overlaying image 2 (minus the black tiles) over image 4. This is only a snapshot, and if we moved back towards the blue wall, the same problem would happen, image 4 would overlay onto image 2.This happens constantly on z levels other than 1, but not for everyone. Some portion of the player base is affected, and this has nothing to do with the "Use Graphics Hardware for displaying maps" maps (which is on in these screen shots). Leaving z = 1 by any means starts the issue, and returning to z = 1 by any means fixes it. In SS13 you need to be a mob/living for this to occur, but I believe that's just because other mobs (observers) don't use planes. Moving the cursor over items on the screen correctly shows their proper positions regardless of what the visuals show, so this is a purely visual problem. Numbered Steps to Reproduce Problem:
Expected Results: Actual Results: Does the problem occur: When does the problem NOT occur? Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? |
as it stands, fixes tend to only come to the beta, so once we get to this point, shortly before the beta is released, using it starts to become a necessity. That being said, a bug that only some people see, in relation to an issue with their video card drivers, requiring a move to beta to fix isn't that fartetch. I'm not gonna support reverting a rather beneficial change that will lead to us being able to completely remove the whole ghost images mess just because some people have to upgrade to the beta to make it work. |
I've cleaned up this PR a lot so we can centralize discussion to one place. |
I have a 980Ti and I still hit this issue with stable. |
So far my studies showed its exclusively a nvidia issue. AMD and Intel graphics work fine. |
I don't think this happens with other z levels. I get this bug very very frequently when: Only a reconnect fixes it. GF1060 card However when I play I rarely ever leave the station z. |
@lzimann 510 issue |
This is occurring on my system on 510 stable but not 511 latest beta
Mod edit: -- for people with this issue - first update to the latest 511 beta byond client
Then try the steps listed in https://tgstation13.org/phpBB/viewtopic.php?p=220316#p220316 if you are still having the issue
The screen will stop updating, any animations playing will freeze. You however will not be frozen and can move around, taking the whole frozen scene with you. As you move the unrendered blank tiles will properly render under the frozen image (the plane?).
Eventually the frozen image will "update" and the new still will replace the old one. Bizarrely I've only seen this off station. It happens constantly when z != 1, but never when z == 1.
This never stops happening. Ever.
The text was updated successfully, but these errors were encountered: