KSP has its own screenshot button (F1) and so does integrated Steam (F12). This is pretty uncommon but it has happened to me 3 times. The Steam Screenshot Glitch: Sometimes while having FASA installed it will make Steam crash your game. Don't multitask while playing KSP unless you're using the Steam version but it is limited to only browsing the community and web in Steam overlay. Running a game booster will help close programs that are using a lot of memory to make sure that KSP is the only one using large amounts of memory. Make sure you only use mods you need because if your only building rockets don't install KAX while you have FASA because it's just taking up memory and your not going to use it. This can be avoided by not having every mod ever released installed in your KSP. Your computer will then do the one thing it must which is terminate KSP. Running out of memory: This one is almost the same as the one where KSP steals memory, except this is when KSP eats through allocated and reserved. This can not be avoided and it's perfectly normal because even computers make mistakes. A corrupted game will do you in with this one. This problem usually originates from sloppy mod coding or too many mods. This will make your computer mad and it will terminate KSP at once. KSP likes to write (or try to) write to a read only file. How to avoid leaks? Don't try and fry your computer by switching scenes often and don't run memory hungry programs while using KSP.Īccess Violations: Ever tried writing a read only file? No you probably have not because it's impossible. When your computer sees KSP stealing memory from it your computer will ask (force) KSP to end and give you this message: "KSP has terminated in an unusual way". Changing between buildings in KSP is what will start pocketing memory. Why? KSP will actually start pocketing (leaking) reserved memory after frequent and large transfers of it. If you install FASA and keep switching back and forth between the VAB and the map you will be seeing your desktop in a few seconds. Reserved it like a bank that KSP can borrow from if it needs memory to perform a short task that drained the allocated memory. KSP steals memory: KSP has allocated and reserved memory, allocated is what is set aside for the game itself by the computer. Please Log in or Create an account to join the conversation.Well after lots of researching stack dumps from KSP and doing a little thinking of my own I have gathered several crash scenarios and ways to avoid as well. Unity also offers a dx11 mode (-force-d3d11) which I couldn't get to work with reshade either.Īny ideas what I could try to get it to work? I'm kinda new to this For players who play it with many mods it's the better alternative to the buggy 64 bit version of the game. OpenGL mode in KSP is obviously a bit weird if d3d9 works fine, but many people use it because it frees up about a gig of ram and therefore avoids crashes. Also tried loading without the sweet.fx file present. I tried to kill all processes and services that might do any overlays that might conflict with OpenGL but still no joy. It crashes at startup with an error message, writes a opengl32.log and unity crash messages. Even 8xAA works! \o/įunny enough it auto-detects opengl and puts the dll as opengl32.dll in the game folder, but the game crashes when I start it in OpenGL mode (calling it with the switch -force-opengl). I ran Reshade Setup on the game and it seems to work out of the box. First of all thank you guys! Been playing KSP with reshade+sweetfx for several hours and it's been great fun.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |