All_Hail_Autostrut Posted October 28, 2023 Share Posted October 28, 2023 (edited) Reported Version: v0.1.4.1 | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 5 6-core | GPU: GTX 1660 Super | RAM: 32 gb I was driving a small rover around on Eve, when I reloaded a quicksave and the terrain broke. Debris icons that were landed on Eve started teleporting around the screen, and everything was a mess. Jumping to a higher timewarp and going back to x1 does nothing, F5 F9 does nothing and Map Screen cycling also does nothing. Interestingly, neither does restarting the game. When I went back to the KSC, even the menu with the options of which building to enter's background screen had the same effect. All of the screens with terrain visible (excluding the Map Screen and Tracking Station) had the same glitch. The VAB doesn't, but if I launch from it, the glitch will start again. Definitely worth mentioning that I am still on Patch 4, because I was scared to update while flying interplanetary. Any help would be appreciated, as I can do nothing except for build crafts right now. Thanks! P.S. I'll link a video below, just in case. Included Attachments: 2023-10-2808-53-53.mkv Edited October 28, 2023 by Spicat Link to comment Share on other sites More sharing options...
Spicat Posted October 28, 2023 Share Posted October 28, 2023 @All_Hail_Autostrut, does the bug behave like this one (if you remember if you were paused while F5/F9)? And do spamming pause/unpause fix it? Link to comment Share on other sites More sharing options...
All_Hail_Autostrut Posted October 30, 2023 Author Share Posted October 30, 2023 It is similar, but the bug first appeared when I loaded back in after an F5 F9. I don't think I was paused, as all that happened was that I crashed my rover and immediately clicked F9. Thank you so much for finding this post for me though! And in regards to your question about spamming, I didn't try, but I did pause/unpause about 10 times with no effect. Also, I forgot to mention that when I updated to Patch 5 in desperation, the glitch was resolved. Kinda weird that restarting the game doesn't fix it, but updating does (especially if this isn't a known glitch), right? Link to comment Share on other sites More sharing options...
Recommended Posts