sal_vager

@Fastfishy2, F12 toggles the aero overlay, and there is a known bug where if you highlight a part after the overlay is disabled the game will crash. You can avoid this by disabling the highlighter in flight, or by removing the key mapping to the aero overlay so it can't be toggled.

I meant the whole folder containing your persistent and all the craft with that save

Hi @BlkBltChemie, try disabling anti aliasing, you have it set to 2x

That's so weird, according to Toms Hardware...

Highlighting FX adds the coloured glow to the edges of parts in the VAB/SPH and in flight.

It looks like there may be a bad craft file, you have this error. ArgumentException: An element with the same key already exists in the dictionary. at System.Collections.Generic.Dictionary`2[System.String,ConfigNode].Add (System.String key, .ConfigNode value) [0x00000] in <filename unknown>:0 at ShipTemplate.LoadShip (.ConfigNode root) [0x00000] in <filename unknown>:0 at KSP.UI.Screens.CraftEntry.Init (System.IO.FileInfo fInfo, Boolean stock) [0x00000] in <filename unknown>:0 at KSP.UI.Screens.CraftEntry.Create (System.IO.FileInfo fInfo, Boolean stock, .Callback`1 OnSelected) [0x00000] in <filename unknown>:0 at KSP.UI.Screens.CraftBrowserDialog.BuildCraftList () [0x00000] in <filename unknown>:0 at KSP.UI.Screens.CraftBrowserDialog.Start () [0x00000] in <filename unknown>:0 Can you please zip the save that is causing you trouble and put it on dropbox.com for us, you can make a free account and use the 'share' link on dropbox to share the file.

It looks like you have found something that Squad can fix their end, as the launcher doesn't store any settings itself, it uses the same settings.cfg file that the game uses, which is no longer in the zip or installer and is created by KSP when it first runs. So to fix your launcher issue you just need to run KSP, then the launcher will work normally. I've asked a few owners of the SpaceNavigator to have a look at your 6-DOF issue as I don't have one, and it seems it really is broken, they report that it is still possible to edit the settings.cfg directly to change the bindings which you can use as a workaround until this is fixed on Squads end. So I'll reopen your bug reports now we know what's going on, it's extra info like this that can make all the difference as it helps make the developers jobs a lot easier.

That'd be because KSP needs write access, which it wouldn't have if the player unzipped KSP to Program Files, though it usually causes other problems than this. However, the install in this case is via Steam, which adds the correct registry entries to Windows to allow KSP to write to Program Files, this is in the KSP.log [LOG 11:55:45.322] AssemblyLoader: Loading assembly at E:\Program Files\Steam\steamapps\common\Kerbal Space Program\GameData\Squad\Plugins\KSPSteamCtrlr.dll It's still worth a try at this point though.

It's already there. I forgot it, but I'll add that anti aliasing can do this as well. @doggonemess, does the background work for you if anti aliasing is on but part highlighting is off?

If the root part isn't the cockpit you can re-root it in the editor, press 4 then click the vessel, then click the new root part.

Perhaps solving one will solve the other @jensgw, as far as I can determine it should also be working. Your logs may contain errors that would be clues as to the cause, and they would reveal where KSP is installed, which can be a factor.

Thread closed by member request

The launcher was recently updated and no longer downloads the patcher, the launcher is perfectly usable for starting KSP and for setting many options external to the game, for example to correct the 'cannot switch to monitor resolution' issue that arises when the Unity engine is given a resolution setting it is unable to use. In this case the launcher is not working correctly for an unknown reason, nor is the players 6-DOF device, so I'd like to find out why.

Hi @ComradeGreen, can you please look here, we will need your game logs to help figure out what's wrong. Thank you.

Welcome to the Support section jensgw, where we can try to find out why these issues are occurring for you and resolve them, as they are not reproducible here and these are the first reports of this kind it is too early to know if these are bugs in the game or a problem with your install. With a fresh install of KSP you should see this in the Launcher settings for audio. The Apply button will apply any changes made without exiting the settings manager, the Accept button will apply any changes and exit the manager, Cancel will return you to the Launcher main screen and will revert any changes made since last clicking on Apply. I checked on Linux and on Windows, the volumes are present in the launcher and the Apply and Accept buttons are working correctly, you can see this in the youtube videos below. As this is working it suggests that there is a local issue which technical support can resolve, rather than expend developer resources on an issue that may prove to be external. So I'd like to draw your attention to this thread. You say you have already tried reinstalling KSP but that would not rule out a corrupted download, so what I would like from you is your game logs, please upload to dropbox.com or a similar site the KSP.log, output_log.txt and dxdiag hardware report from your PC. Please also tell us the make and model of the 6-DOF device you are using. Thank you.

Hi NoobTool, can you upload the craft please, maybe someone can figure it out by testing it directly, also there's an option to retain control point in the settings screen, it's for IVA, but I don't know if you're using IVA while you fly.

Hi Jamie, yes it might, can you please upload the output_log.txt from KSP_Data and your dxdiag hardware report for us, dropbox.com can handle the files.

Thanks DocMoriarty, can you please report this on the tracker if you have not already done so.

I'm glad it worked, forcing glcore forces the Unity engine to detect the highest version of OpenGL on the system, and to use that, it's supposed to do this automatically but sometimes fails and has to be forced again via this command. You can use a shell script to start KSP with that line every time, or add it to the launch options in Steam.

I don't think that'll help you to be honest, what I see in your pic makes me think "Bad GPU driver", I'd like to know what card you're using and what driver specifically. Also does starting KSP with -force-glcore or -force-gfx-direct fix this? https://docs.unity3d.com/Manual/CommandLineArguments.html

He may have used it, especially if he was flying a plane, unfortunately there is a bug with the aero overlay and the part highlighter, after using the overlay (it's F12) if a part is highlighted in flight the game will crash. This doesn't explain the CheckEncounter issue though, but that might be a red herring and not the cause (though it could cause a drop in performance, many mods that have their own bugs will quite happily spam the logs and generate logs many hundreds of megabytes in size) and the crash may have occurred when your son moused over the debris. The highlighter crash can be avoided by disabling the part highlighter in flight from the settings screen, it would be interesting to know if your son (or yourself) should experience this crash again with the highlighter disabled.

libxcursor1 isn't installed by default anymore? Anyway you can install it if you want from Synaptic, or the command line with: sudo apt-get install libxcursor1 You can also make Steam open the 64bit version of KSP by default, right click KSP in the Steam client, click Properties, then Set Launch Options and put this in: %command%_64

Please post the logs as well, and the backup saves, best to just zip the logs and the save together and put it on dropbox.

Steam opens the 32bit version of KSP when you click Play or when you use the shortcut, unless you right click on KSP in the Steam client and choose to open the 64bit version, or if you manually modify the launch options.

Hi @Matthieu, can you please try starting the KSP.x86 and the KSP,x86_64 directly from the Kerbal Space Program folder.