sal_vager

This came up recently here. Big thanks to Tankman101, who found he could run KSP at one resolution setting below his maximum, so try deleting your settings.cfg, start KSP and don't use the settings that matches your screen resolution.

Hi Dunder, can you put them on dropbix, mediafire, googledrive or a similar file hosting site please.

Yeah that should have worked. Do any of your other games have logs that might show what's going on?

I'd suggest reinstalling DirectX but that isn't even possible with Windows 10, there is no web installer or redistributable for DirectX 11.2+. Can you tell me what driver you installed?

The logs aren't showing anything wrong, do you have driver info in your dxdiag now? It should say which driver is installed, and do you have any issues with any other programs?

You are getting a white game window every time you start KSP? I have never seen KSP or the launcher show white screens before, or even heard of this, you're going to have to upload the KSP.log and output_log.txt (\KSP_Data) somewhere then link them here so I can have a look. Also, a lot of data is missing from the Display Devices section of your dxdiag, such as the driver number, its date and size, so I suspect your driver is not correct or failed to install properly. You must reboot after installing most drivers by the way.

Hmmm, if all that does is clear the input locks then the "Clear input lock stack" button in the debug menu should do the same. Unfortunately I never seem to run into this issue, so if you don't mind testing the debug button next time this happens, it'd be good to know if it works or not.

Hi Majorjim Both of the small extending solar panels that lack a casing do not have a retract mechanism, it was decided they needed more than just mass and cost to set them apart from the enclosed solar panels. It's only those two, all others (except the OX-Stat and the new one from Asteroid Day) can retract.

Hmm, okay I'm just going off the numbers in the dxdiag, it's not easy as they don't actually match up to the numbers shown on the Nvidia website, for example the dxdiag will say you have driver.... Derp now I see it, I was going off the dates, the dxdiag says this: Driver Date/Size: 10/3/2015 So I thought it was from the 3rd, while the site has a driver dated the 7th, but if I open my eyes I see this: Driver Version: 10.18.13.5850 The last 5 digits match the driver on the site: Version 358.50 - WHQL So it's me being daft, the driver is fine. Replacing the card is an idea, I don't know if it's that though so I am reluctant to cause you to spend any cash, if you have any friends with a spare card lying around you could offer them a few bottles in exchange for a loan of their graphics card. That way you can at least verify it's your card, without worrying the missus

Hi again KingAirDriver, sorry to hear you are still having trouble, but also congrats on getting to orbit and back There's not much in the dxdiag to indicate a problem however, your PC specs look fine but your graphics driver could be updated, a newer version was released on Wednesday the 7th of this month. Can you please upload a new output_log.txt from when the game glitches out, and if you can get one where the game doesn't crash that could be useful too, it may show new information but be aware it's overwritten every time you start KSP, so needs to be manually renamed to prevent this. Also if you can take screenshots of the glitches I might see something I recognize. The dust is a worry, the graphics card may have over heated at some point, unfortunately it's very hard to tell.

I think you are better off with stibbons suggestion to be honest, as that way all users you add to the games group will be able to run it, and KSP will be able to write saves under their permissions, all they would need is their own launcher to start KSP. I think all users will be able to see each others saves though. If you symlink the files to a folder in your /home directory, anyone else trying to use KSP will find they don't have permissions to make files in your folders, so KSP won't work.

The old fglrx drivers from the repository is a bit rough, yes, the open source radeon driver is actually better in most cases. The Catalyst driver from the AMD website is your best bet though.

Yes, the scripts should all be fine for all versions of Ubuntu, and indeed all Linux distro's, as a terminal of some sort and the shell that runs inside it are standard to all Unix-like operating systems.

Well, the idea is that the ISRU will do its thing at 1000+ warp while it's not the active vessel and you're watching your Jool exploder or trundle along its orbit or likewise doing some other thing. Seriously, watching the ISRU is like paint drying.

Hi KingAirDriver, if you run KSP from a protected Windows folder it may not be able to write files, and this can break things, that is why C:\Games is recommended for non-Steam installs, as C:\Games is a folder you create outside the Windows file structure. Your issue looks very much like a faulty graphics card or incorrectly installed drivers, I'm assuming an appropriate Nvidia driver was installed and that the PC was rebooted after driver installation. I don't know if it is the card though, so I recommend you first reboot the PC to ensure the driver can activate properly if this hasn't already been done, then reinstall a fresh copy of KSP to C:\Games and run that copy, do not move your current install as it can already be flagged by Windows as potentially unsafe software and will not work properly as it will be forbidden from writing files. Look up data execution prevention if you're curious. Also your log is full of this: Which suggests KSP was unable to properly compile the parachute on first run, again this can happen if KSP is run from a protected folder. TheClaw also has a parachute fix in his stock bugfix modules. If the above does not help, please run dxdiag from the applications menu (type dxdiag to find it), save the report and upload it.

So, I had a look for this issue on the bug tracker today, because I'd like to present it to the developers, but it isn't there. If you want this changed you have to make a bug report on the tracker, as the support forum is not for bugs, this issue will not be addressed if the only information is a forum thread. So one of you better get a move on.

Hi deltalambdamu. They do have ejection force, if you would like more ejection force please edit the "ejectionForce" line for the decoupler of your choice in GameData/Squad/Parts/Utility/ MODULE { name = ModuleAnchoredDecoupler anchorName = anchor ejectionForce = 250 explosiveNodeID = srf }

If you opened the debug log (alt+F2) you could see what it was getting stuck on while it loaded, or even take a look in the KSP.log or output_log.txt

The logs are truncated, I watch them using tail -f

Hi StarStryder, have you tried putting the settings.cfg, KSP.log, Physics.txt, saves folder, GameData folder and Screenshots folder in /home then symlinking them to KSP in /opt ? I don't think there's any other way to do it, and the symlinks won't work for other users. The developers prefer a portable install, with everything contained in one folder so it can be run from a portable hard drive or memory stick, so the only files that are written outside of the KSP folder are Unity3D specific.

I see what you mean, this looks like the same behavior you get when when using the editor tools to offset parts within cargobays. The cargobay issue has already been reported, if this is the same then it will be fixed when the cargobays are fixed, if not then congratulations, you have found a very unusual thing. If you would like to report this to the bug tracker please see the stickied bug reporting thread, you will find the link near the bottom, after the guildlines on acceptable bug reporting. Though it may just be caused by all those attach nodes, the Hubmax isn't intended to be used this way. As for your fuel issue, your craft file has an awful lot of clipping, that can give the fuel flow code problems if multiple engines are all on one node.

Can you upload your vessel please.

Hi Arugela, the editor tools automatically snap to an invisible grid centered on the parent part when in the default "Absolute" orientation mode. To disable this, press F to toggle to "Local" mode. This is an intended feature. Hope this helps

Closing. Try again in the support or gameplay sections with less vitriol. Thank you. Edit: Don't forget logs, pics and a decent description so others know what you mean.

Closed by request of Probus.