ibanix

This thread is the only time I have been ashamed of calling myself part of the "KSP community".

0.3.2 correct version?

1) Via CKAN; I'll try a manual install. 2) How much do you want? What steps would you like me to take before submitting logs? 3) I'm using the stock toolbar.

My 0.2 credits: I paid $20 for Firewatch (http://www.firewatchgame.com/), which was a great story and great experience. The entire game play was less than five hours. The experience was great, and that was what made it worth spending money on. For KSP, I spent the $40. In KSP's case, I wanted to support the developers for making something I enjoy greatly. My favorite model for things is actually to fund them. I helped crowd-fun Pillars of Eternity ( eternity.obsidian.net/) as well as the card game Exploding Kittens. I use Patreon to donate to creators I think make good things. I don't know Squad's business model, but I would like it if they could also use this model.

Yeah, ditto here.

1.1 was out the day after it was available on the KSP store. 1.1.1 is not going to show up on GOG.com's patcher, at the request of Squad - they found serious bugs in 1.1.1 and requested GOG hold it off until a fix could be found. I've usually gotten patches in a timely fashion via GOG.

As usual, if you want to get the issue fixed, help out: 1) Find steps that always cause the crash; every time. Reproduction is highly useful. Note: "Crashes whenever I'm in the VAB" or "After 3-4 minutes" are not useful. You want actual steps that work every time. 2) Submit log files and reproduction steps: http://bugs.kerbalspaceprogram.com/issues/8241 3) If you know how, run a debug trace on the dump files, and submit that, too.

1. Pick a mod 2. Uninstall it. 3. Is the issue fixed? Yes -> There's your problem No -> Goto #1

If you don't know, it isn't the cause of your problem.

Install a clean copy of version 1.1 and start from scratch, without mods Do your problems persist? Yes -> file a bug report No -> The problem is in a mod, or because you tried to copy from 1.0.5. "I want to do it my way and only play with my old save and mods" -> Live with your issues.

VAB crashes quite likely to be this known issue: http://bugs.kerbalspaceprogram.com/issues/8241

I'm unclear if this is the same issue as related to: http://bugs.kerbalspaceprogram.com/issues/8241 This bug has happened several times immediately follow staging. I haven't found a pattern other than that. The process immediately hangs and must be force-terminated. Here's a Windows Error Report on the hang: KSP.log, output_log.txt: https://drive.google.com/file/d/0B4Rt7Cyo760PbzdMS09UNEw1R1E/

Well, that can't be my problem - I don't use Steam.

Which files were missing?

I can confirm this behavior. The 'Mun Program' did not give me the 100k advance when I took the strategy.

USB was designed deliberately to be a universal device interface. Graphic card shader models were not. Secondly, supporting older shader models makes it harder to support and develop graphics on newer hardware. Keeping USB 1.1 support, due to the design of USB, has no impact on people wanting to use devices with USB 2.0 and 3.0. In short: Your analogy sucks. Please try again.

Known issue. Quoting nightingale on this:

I would follow the progress on the bugtracker, which is more likely to state when the issue gets fixed and how close to release it is. It seems like an easy way to reduce the occurrence of this CTD is to make sure you ALWAYS ATTACH a surface-attach item, before picking a new item; don't leave surface attached items 'floating'.

This has happened to me, also. Quickload (F9) solved the problem, and I have been unable to reproduce it.

Folks, try the following: 1. Start any game (can be new career or sandbox with default settings)Go in VAB or SPH and add any part that allow surface attachment, like a command pod2. Switch symmetry to 2 anything other than 1 (off)3. Then pick but do not place any part that can be surface attached AND will add staging4. Finally, just move your mouse cursor repeatedly in a left-to-right motion (cyan arrows in screenshot3) while still "holding" the part from the previous step above the other part until the game crashes (should only be a few seconds if you move fast enough). The idea is to have the "ghost" staging icon (bottom right red arrow in both screenshots) switching from 1 icon to multiple icons repeatedly. If the above causes a crash, it's apparently a known issue: http://bugs.kerbalspaceprogram.com/issues/8241 If you can reproduce with the above steps, register on the bug tracker (http://bugs.kerbalspaceprogram.com/account/register); then return to the bug page ( http://bugs.kerbalspaceprogram.com/issues/8241 ) and add a comment indicating you have this problem. Attach your log files.

I believe this is the same issue as reported by users in this thread, but would appreciate confirmation or denial of that:

You can't really fault them for dropping support for hardware that's *10 years old*.

You seem to have the same issue as others are reporting. Join the common thread, here:

Interesting. Here I'm running Windows 8 on an i3-4150, 16GB, and a GTX 960. It seems to me like we need someone with experience reading log files to parse through a bunch of ours for an answer. Anyone willing to rise to that challenge?

I'm using -popup-window to do fake fullscreen, but I think this is unrelated.