sal_vager

You make the Games folder on your C\: drive. How to make a new folder in Windows. Using your own folder instead of Program Files avoids issues with User Account Control, which can occur when software is placed into protected Windows folders by the user, this is a bad practice and manual changes to Program Files should be avoided. There is a warning when first attempting to open Program Files for this reason.

C:\Games\ It's best to avoid putting software into Program Files manually, let installers do that as they will add the appropriate registry entries.

Hi @OHara, your logs show that KSP is using your Intel graphics card, not your AMD. To get the most from the game it is recommended that you use your main graphics card, you can do this by creating an application profile for KSP in the AMD catalyst control center.

One thing at a time @HabLab, fixing your screen size may also stop the crashing. Also, see this thread.

Hi @SkyKaptn, can you reproduce this in an unmodded install, thank you.

If it happens again please take some screenshots and save your logs @SkyKaptn, thank you.

It's working here, I think you need to see this thread @Jens Lyn IV

I am unable to reproduce this @tg626, please try to recreate it then post your logs.

Hi @_Astra_ Help us help you by providing more info on your issue, thank you.

By the way guys, -adapter N works on Linux, but only if KSP is fullscreen. The prefs file is a Unity thing, not KSP, and existed in 1.0.5 and earlier, and also exists for other Unity games, just take a look in your ~/.config/unity3d/ folder. It's causing trouble on my other Unity5 games as well, Satellite Reign and Pulsar Lost Colony, in the latter case I can't even change the screen resolution or mode without editing or deleting the prefs file as it overrides any settings changes made in Pulsars settings screen.

Not really as the developers are still working at fixing the pre-release tracker issues, that tracker is just closed to new issues as we're out of pre-release.

Bug reports actually go here @GoSlash27 The Official Kerbal Space Program Issue Tracker Bugs reported to the tech support forums just get in the way of providing tech support to people in need, also completely breaks the workflow when dealing with issues, bugs reported on the forum are not copied to the tracker. It's also important to understand that not everything is a bug, for example heat shield ablator will be reduced if heat shields are exposed to heat, whether from a Moho orbit or being too close to ISRU components, and KSP relies on your CoM relative to the pivot of control surfaces to know which way they should move, that's how the game works. It's worth looking around and asking in Gameplay questions in case something is a game mechanic, not a bug. It also doesn't help to have duplicate reports, please look to see if your issue has already been reported, it may already have a workaround. Unfortunately 100% bug-free software isn't possible, the size and complexity of modern software means that bugs in some form will always exist, whether it's in a computer game, an operating system or even the Space shuttle, and a game like KSP allows players so much freedom there will always be things that go wrong for somebody. So please report issues to the correct place, after having a look in case it's already reported, or in case it's something that's meant to happen. Thank you.

Hi @HabLab, it sounds like your settings.cfg and/or prefs file has the wrong resolution, if it's the settings you can fix this via the launchers gear icon, if it's the prefs file you will need to edit manually, it should be accessible via Finder or see the NEED SUPPORT thread near the top of this section.

Hi @Mutex, yes the logs would be appreciated, though I have no idea why or even how this can occur. Perhaps trying different -force-glcoreXX versions will help, where XX is the version of OpenGL, see the Unity page for details.

Hi @AxSirlotl, I think it's this part. KSP checks the MET (Mission Elapsed Time) of the craft, and an older craft changes the MET of the total vessel to the old MET, meaning it's not a new station.

@miceliux, try running KSP with the -force-glcore command line argument.

They control a few things at the engine level, see here for a list. -force-glcore forces Unity to detect the OpenGL driver on the PC, and use the best version it finds, it's supposedly Windows only but it still works for us. -force-gfx-direct forces Unity to to do single threaded rendering, graphics may be a bit slower but graphics was never KSP's bottleneck so it shouldn't matter much.

Wait, just remembered something. Change to the KSP folder first if you use the terminal, otherwise the game can fail to load everything. cd ./pathToYourKSPinstall/ ./KSP.x86_64 -force-glcore

Hi @Miwarre, there is a known issue with AMD proprietry graphics drivers and Unity5 multi-threaded rendering. Please try starting KSP using the -force-gfx-direct command line argument. %command& -force-gfx-direct You can add that line to the Steam command box in the Properties for KSP in the Steam client. (props to soulsource again for finding this works)

Hi @votec, there are a few workarounds for this, as you have an Nvidia card you will need to force KSP to use it in the nvidia control panel Another option is to start KSP using the -force-glcore Unity engine command line argument. You can do this from the terminal with ~/pathToYourKSPinstall/KSP.x86_64 -force-glcore Another workaround is to manually set your resolution in your settings.cfg to 1 pixel lower than you are using, for example 1023x767 for a 1024x768 monitor. Or keep testing lower resolutions until one works. As to why this is happening, it seems the open source drivers of all cards are not compatible with the Unity5 stencilling at this time. KSP is probably using your Intel, which is why you see this issue.

Okay, the prefs file is in ~/.config/unity3d/Squad/Kerbal Space Program/ next to the Player.log It is created by the Unity engine to record a known good resolution, along with screenmode and graphics quality setting, usually the settings a Unity game was using when it was last closed. All Unity games on Linux and OSX have a prefs file in their own folder, on Windows the registry is used. While Unity4 was generally okay, Unity5 is creating bad prefs files with bad resolutions such as 1920x1 My other Unity5 games are also doing this, and on one (Pulsar) I cannot even change the resolution in the games settings screen without manually deleting the prefs file, as it is overriding the games own settings.

It might be, I have heard of two other players so far that have needed to use this, a French and a German. This isn't the same crash unfortunately, this is in the Unity version of libmono included with KSP, not in the Unity binary (KSP.x86_64) The old segfault fix is no longer possible, but so far no one seems to have needed it, I have tried to find the new offsets in 1.1 but the signature is gone, huge thanks to @MikeAeronautLZ, @meeki, @Addle, @FuzzyLlama and @soulsource who helped me find it in 1.0.5 and earlier. I don't think mono changed between 1.0.5 and 1.1, and any cause for this crash would just be a guess at this point. Off the top of my head you either need -force-gfx-direct (if using AMD) because AMD drivers are dying when Unity tries to do multi-threaded rendering, or your prefs file is bad with a dumb resolution, and needs to be set manually.

Or I could merge your old account into this one, so you keep all your points. Give me a shout via PM from the old account and I'll fix it up for you Saw the other message to Van, I've merged the old account into this new one.

In the KSP.log, output_log.txt or Player.log yes, or just open the debug window with alt+F2

I don't see x64 on the Linux version, so I guess OSX will be the same