sal_vager

It is not clipping, it is a purposeful change to allow players to avoid the automatic fairing if they choose to do so.

That would be the Settings.cfg, though it may be incompatible. Also, moving to Support...

That reason being the copyright infringement of all the modders work that was, and still is, all rights reserved or otherwise non-redistributable, which is why Squad didn't close the unmaintainable mess that was just a skin to wordpress commonly known as "Spaceport" straight away, allowing players to continue to access addons while the modders who had an interest in preserving and supporting their work could upload it elsewhere. Thankfully the other addon repositories do respect the modders and their choices, and do not intentionally host the works of others without consent. Also as many modders have shown there is a path to keep old addons alive, if the creator can be contacted and permission given, a new modder can take up the work and continue it

Juts a note on the parachute test contracts, the chutes you test don't have to be the chutes you land with.

Hi jwbrase, Ted handles bug tracker stuff so let him know there's an issue and he can sort you out.

We have one of these already! Merging!

No worries, I'm just glad it's working, though it'd have been nice to find out why it was broke, have fun in space

Please put your output_log.txt (it's in KSP_Data) on a site like dropbox or pastebin for us, we'll see what's up

Chutes should be fine until just under mach 1, which will tear them apart, also the default opening altitude is 1000m now, so any old craft will need to have their chutes tweaked in the action menu, or risk unexpected lithobraking. You should be alright without the droges, just don't re-enter with too low a periapsis so the atmosphere slows you down more.

That should happen tomorrow, if not PM Ted and he can fix you up.

Please file a detailed bug report here when you are ready, I suggest also checking the bug reporting guide in Claws sticky support thread.

That might work, it's probably a Bios feature though and if there's something wrong with the Nvidia you can re-enable the Intel card.

Well it's definitely using the Intel, not the Nvidia, your powersave options should be set to "Performance" when plugged in, hopefully that will do it as more modern laptops should automatically switch. The error with Limbo just reinforces that it's a problem with the graphics card or driver. Edit: Lenovo user manuals say to use Fn + F3 to open the display options, that might let you select which graphics card to use.

Do other 3D games work? I'm starting to think the card has worked partially loose over time and with heat. Okay this is even stranger, your KSP log doesn't detect any graphics card at all, it uses DirectX on Windows to do it and when it tries it dies, and your dxdiag says your graphics card is an Intel HD4600, which I just googled, and is a notebook/laptop card, though your dxdiag doesn't mention it's a laptop. Lower in your dxdiag under System Devices it says you have a NVIDIA GeForce GT 750M, it's common for laptops to have two cards, the Nvidia should be used for gaming and the Intel should be used for low power modes and office/browsing stuff. So my guess is you ran the laptop on battery at some point, maybe the cable worked loose, and it automatically switched to powersave mode and disabled your Nvidia card. Derp, I just spotted the Lenovo 20217, it's a laptop and I don't know how to switch to the Nvidia on that model, checking your powersave options and making sure it's plugged in should be enough, or there may be a physical switch to select the graphics card, set it to the Nvidia and reboot. You should also have the option when right-clicking the KSP.exe to run it with the Nvidia. Might be a good idea to check for a newer Nvidia graphics driver as well.

Lots of players are saying that KSP is working fine for them on Win10, I don't know if the upgrade will fix this though, if it's still not working with the new driver and DirectX please make another dxdiag report and get the new output_log, they may say something different.

I just hope it works, honestly KSP should be working fine on a fresh install, though a guy yesterday had an issue that required a full reinstall of windows to fix, we never found the actual cause.

Might be, also I had to update that link as I posted the link to the web installer by mistake, the full package is closer to 100mb, and should work even with Dx11 already installed. You could test KSP with -force-d3d11 by adding that line to a shortcut's properties, it won't look great but KSP should at least start, then we'd know that Dx11 is working at least.

Is it still saying it can't find DirectX9 ? If it is you may need to install the DirectX package from Microsoft to make sure it is fully installed.

Okay the dxdiag is a little odd, it says you have DirectX 11 installed which should be fine for KSP, and that you have a driver for your graphics card (11.1 which seems a bit old), but it's showing me three identical graphics cards, all Intel HD 4600's, that's not normal. I think you need to update the driver, this looks like the latest driver for your card on Windows 8.1 64bit, download that first, then uninstall your current driver in Programs and Features, then reboot. That will put you in a basic Microsoft driver mode, no good for games but good enough for the next step which is to install the newest driver, and reboot again. That should clear up the misreported graphics cards and even make the PC perform a little better because it's a newer better driver.

Something like this is immensely useful to Intel GPU owners, I may link it in the self support thread.

Hi derekmw, this is telling me your graphics card is not detected, has missing or incorrect drivers, or DirectX is not installed. Please run dxdiag (start, run, type dxdiag), and generate a report, and either post it in [noparse] [/noparse] tags or upload it to a file share or paste site.

I'm pretty sure an addon causes this, maybe tweakscale or mechjeb.

It's pretty much a bug, KSP just fails to realise a node can be set on some orbits, usually if it's too far ahead of the current orbit but it's usually possible to find a point where it works then drag the node to where you need it.

If raid 0 worked before then yeah it should work now, I assumed it was a new setup, unless there just happens to be a bad file but the Steam verification should have solved that. Your edit is making me think this is driver related though, what driver version are you using? And did you remember to reboot after installing it?

Yeah, on a standard Windows install with suitable graphics drivers installed it should work fine, not crash when clicking. Did you try the KSP.exe? That'd rule out the Steam overlay and directory/shortcut issues. And testing KSP from a memory stick would rule out issues with the raid configuration. KSP can also have issues if it can't write to its own files, do you have any anti-virus programs installed? I have heard recently that some firewalls can cause issues, comodo firewall especially.