Jovian Oracle

I started with HDMI, went to DP with the new monitor and are now back with HDMI. My GPU has 3 DPs and 1 HDMI, so I have little choice with the new arrangement.

I've heard of that particular issue before, but I didn't think of it applying in this case. Though, now that you mention it, I'm going to go ahead and see if the Unity 5.4 titles are all trying to select anything other than the one GPU which I have. Perhaps messing with the Vsync settings when I got my new monitor messed things up? Update: While I only have one GPU, double checking that the Unity 5.4 games are using it does not work.

Alright, after some time consuming experimentation, versions of KSP up to 1.7.3 work fine even after UnityPlayer.dll became included in KSP's main installation folder. 1.8 and beyond are where my problems start, as that's the point when KSP upgraded to Unity 2019.2.2f1 and a different UnityPlayer.dll. Swapping the latter out from an older version does not fix the game.

Interestingly, I didn't actually have any drivers updated until well after the problem started to arise. I'm not in the process of trying out different UnityPlayer.dlls in an effort to see if something sticks. I just downloaded the demo for Mars Horizon as a KSP substitute and that also crashed, to my extreme displeasure. I might also see if cleaning the registry might have some effect. Update: Nothing wrong in the registry. It's also so weird that half my Unity games work and the other half do not. Update 2: After some rolling back of Kerbal Space Program to a previous build of Unity, I've determined that common thread with the failing Unity games is Unity 5.4. Versions of KSP made before 1.2 work fine.

I had to return my monitor for health reasons. It appears that grafting Mantis Shrimp eyes on to my head did not provide the performance boost I was expecting. The earliest system restore and a reset also did not work.

Coincidentally, I had turned cloud saves off a week ago. Unfortunately, cycling it off and back on again did not fix the problem. Is it possible my particular copy of Kerbal Space Program is simply cursed? Or, looking at your avatar, I'm sure the Shadows may be involved.

I recently acquired a new Spectre M32 185hz monitor and, despite successfully playing KSP with it twice yesterday with VSync finally turned off (for once) and running very well when it worked, KSP suddenly started to crash every time I would start it not after I later put the computer in sleep mode and awoke it. This problem also expanded in to two of my other Unity based games from Steam (Hardspace Shipbreaker and Subnautica) but not for any of the others I've had (like Battletech, Two Point Hospital), something I tried on a hunch after reading through the crash logs. I did not have any driver or Windows updates in between the last successful playthrough and final crash, and I've since updated my GPU drivers, updated Windows, made sure there are exceptions for KSP in my antivirus software, made sure DirectX is up to date and I have the latest version of VC_Redist. I've spent the better part of a whole day trying to find the issue and have searched Google for every reference to the UnityPlayer.dll violation I've seen in the crash logs, but there appears to be no solution. I don't have the remote desktop software that people with similar crashes have been getting, and I've not had any memory errors detected. I have uninstalled and reinstalled KSP several times by now, using different hard drives and install locations outside Steam with no success. Rolling back KSP to an earlier version does not have any effect. Turning down my monitor's refresh rate to 60hz does not have any effect. Restarting the computer did not have any effect. Forcing KSP to use anything other than DX11 does not have any effect. Running the game as an administrator does not have any effect. Human sacrifices to my desktop have also had no effect other than staining my carpet. The use of a professional exorcist has also had no effect other than finally removing the tormented spirits of the restless dead from my closer and ending that racket they would make every night. Literally nothing seems to work with this. The DXDiag.txt is here, the error.log is here and the player.log is here. I'm using Windows 10 with KSP 64 launched on Steam, build 02939.