joshudson

The first is acceptable if you can fly the jetpack re-entry (I can't). The second is obviously acceptable.

Challenge: Build and launch a SSTO that uses only SRBs to provide propulsion. Bone stock challenge: Informative and decorative mods only. (OK I don't care if you have mods installed you don't use) Known acceptable mods: * DMP * Kerbal Engineer * Planetshine * Protractor (useless) * TAC life support (only adds difficulty) Known unacceptable mods: * Mechjeb * Mechjeb for all * FAR (I don't want to figure out how to adjust the score and stock aero is fixed in 1.0.4) * KW Rocketry * Infernal Robotics * Any mod that adds non-stock SRBs We define SSTO as follows: You may not drop parts after launch and before achieving orbit, nor break them, nor burn them up. All parts not going into orbit must be detached at launch with any launch clamps used. No kraken drives. No ladder drives, no RCS, no get-out-and-push, no fuel pumping dumbbell, no anything else I haven't thought of (thankfully they fixed infiniglide as you need fins). You may use gravity assist if you can somehow reach the Mun's SOI (but if you can do that you've already won, it's only for score at this point). Reaction wheels are allowed (and probably required). If you need reaction mass for steering, you must use sepratrons. You may enable the part clipping cheat, but only for placing nose cones. If parts clip w/o using the cheat, go ahead and fly them that way. If you fly a kerbal, you must provision for getting him (or her as the case may be) down again (this doesn't have to be SSTO). If you claim you can use the jetpack, you have to actually DO it. Stranding kerbals for showing off is not cool. [i used a probe core for my successful attempt.] I'm lazy. Your score is your PE altitude. My score is 77,098. If you can somehow pull off a Kerbin escape, even with a gravity assist, your score is infinite. Hint: use tweakables and read the definitions very carefully.

That's what it was. Garbage-collected leftover nvidia drivers and it started working. Had already verified glxgears so thought nvidia was already purged. Nope.

Due to various reasons involving a motherboard that fried itself I suspect the change in graphics card is the difference between working 2 weeks ago and crash immediately today. KSP crashes instantly on startup. Tried unpacking anew to an empty directory and it didn't fix anything. $ cat buildID.txt build id = 00642 2014-10-07_10-52-32 Branch: master $ ./KSP.x86_64 Set current directory to /tmp/ksp/KSP_linux Found path: /tmp/ksp/KSP_linux/KSP.x86_64 Mono path[0] = '/tmp/ksp/KSP_linux/KSP_Data/Managed' Mono path[1] = '/tmp/ksp/KSP_linux/KSP_Data/Mono' Mono config path = '/tmp/ksp/KSP_linux/KSP_Data/Mono/etc' $ ls buildID.txt Internals KSP.exe KSP.x86_64 Launcher.x86 Parts Resources Ships GameData KSP_Data KSP.x86 Launcher_Data Launcher.x86_64 readme.txt saves sounds $ A window quickly flashes up and disappears instantly. It's so fast I wouldn't know a window was flashing up if the window manager didn't animate the taskbar. NO logfile generated.