MattJL

Just to update: Filed a bug report (issue 9479), it's been noticed! Thanks to the folks that are working on sorting this kind of stuff out.

Alright, just ran a a permissions repair, and the end result is... no dice. Now, the thing about the launcher is that I dragged it over from 1.0.5 because that breaks in the exact same way (the launcher insta-crashes) in 1.1 as well. The 1.0.5 launcher works beautifully, and through it, I've managed to tweak a lot of settings (and generate a config file). Problem is, when I click "play," the exact same issue happens with KSP proper. I've done as you've said both by editing the config file and going in through the 1.0.5 launcher, but no dice, same story. I wish I understood the problem, but I'm no closer to getting it than I was four days ago.

Just a small update... I tried booting into 64 bit mode (which is possible with my OS), but that didn't work (on either account, both doing so and getting it to work). Are 64 bit OS X folk having the same issue? My gut tells me no, and this may have something to do with this being a 32 bit system. Might also be OpenGL related; we'll see.

Trying bewing's suggestion has not worked, I'm sorry to say. However, this comment has me intrigued: Which supports my own theory about it being a Unity/OS X issue in some situations.

I'm "running" (not really much of a run) a stock install, so that's probably not the solution. Sorry, I missed your comment on my first go-round! I'll start trying these tweaks. It was not a Steam download, I got this right off the site.

Just to be clear - when I say insta-crashes, I mean the whole thing goes kaput - it launches for a split-second and then quits. No black screen of death, just nothing. It'd be really interesting to know what the common problem is (surely there has to be something that connects these things if they're all showing the same symptoms).

I wouldn't be surprised, but the fact that it's been reported elsewhere as a Unity 5 and OS X not getting along type issue has me curious.

So, I've been dealing with an instant crash issue in KSP, as reported here: http://forum.kerbalspaceprogram.com/index.php?/topic/137661-110-crashes-instantly-on-load-osx-edition/#comment-2529501 In my journey for an answer (nothing's worked yet), I came across this: http://forum.unity3d.com/threads/our-game-no-longer-runs-on-mac-osx.395699/ Very recent thread, only started 20 days ago. The error described there is exactly the error I'm getting. Apparently there's some kind of conflict with Unity 5 and OS X and, in my situation, OSX, and other Unix-based machines. The former I can confirm firsthand, the latter is more anecdotally. Unfortunately, the fix appears to be squarely in the dev side of things. I haven't found any way to do this on the user end (and I've been working at this for the last three days, there's no easy solution to it). I know this isn't technically the right place to bring this up, but I hope this gets some visibility on behalf of non-forum users that might be having the same problem/for those that might have a fix for the problem.

So, I've had an afternoon of messing around, time for some updates: 1) I have since taken the 1.0.5 launcher and shifted it into my 1.1.0 root directory. The launcher works just fine (whereas it didn't before) but when I click "Play", the game itself does the exact same thing (insta-crashes). 2) I've examined the config file that's been generated by the Frankenlauncher, but nothing strange stands out to me. I'll dump most of the thing here (relevant data), in case I'm blind (Note: I did tweak some settings in the launcher - mostly resolution - in hopes that it would solve the problem): 3) I've unzipped the patcher (which I'm not sure works in the first place) and attempted to run it. Insta-crash on that part, too. Seems to be a 64-bit issue, and the fact that I think I'm running as a 32-bit machine. I honestly don't know, this might be irrelevant to the problem.

Oh boy, I have a feeling this is a Unix-based OS issue, then. I was originally going to report that it might be (based on non-forum anecdotal evidence), but a very big hmm.

After doing some research, I came across this: http://forum.unity3d.com/threads/our-game-no-longer-runs-on-mac-osx.395699/ It seems like the switchover to Unity 5 is causing some problems on all OSX machines (be it a total failure to load or otherwise). There's a workaround on the dev end, as established by that post, but unfortunately it seems like we're going to have to wait - there's no simple fix on the user end. So the blame lay squarely on Unity.

Ah, I'll try with the 1.0.5 config file. I originally went for the 1.0.4 one, but maybe there's a difference that I'm not able to see. Wouldn't surprise me, I am not a clever man! I'll give it a shot and update accordingly. EDIT: No dice, still have the same problem.

UPDATE: It seems like this is a problem with Unity 5 and machines that run OSX - this is not an issue with KSP in and of itself. Evidence here: http://forum.unity3d.com/threads/our-game-no-longer-runs-on-mac-osx.395699/ UPDATE 2: Seems this is also a problem with Linux. Possibly an issue with Unix based systems as a whole? Hopefully this gets some attention. Okay, hopefully I'm doing this right, I've never submitted a bug report/otherwise before. Information first: KSP version: 1.1.0 Crash log(s): None, it apparently dies before being able to generate one. System specifications: OSX version 10.6.8 Processor: 2 GHz Intel Core 2 Duo Memory: 4 GB 1067 MHz DDR3 Graphics: NVIDIA GeForce 9400 (It's a MacBook, no real clear graphics card) System: 32 bit Clean installation: Yes, just downloaded it a half-hour ago. What happens is, when I go to launch it (either by double-clicking on the launcher or the game itself), it starts up and than instantly quits. The icon lasts for a fraction of a second in the dock before dying. When it does this, nothing else happens - no crash log is generated, there's no messages from my system indicating that something terrible has happened, all that happens is that it starts up and commits seppuku virtually instantly. Additionally, I've tried launching it through terminal commands, and the exact same thing happens. At this point, I'm assuming this is probably a hardware related issue. For the record, 1.0.4 and 1.0.5 run just fine. EDIT: Found the player.log:

Question - what are you doing for the Saturn V/Apollo spacecraft?

First Mun lander, Iron Bell III. Note the very broken engine: I miss 0.13.3 sometimes. Old KSP had a certain kludged together charm to it.

Been working on more replica craft, this time with more of a focus on early US spaceflight: Surveyor! Sadly couldn't fit any scientific instruments without making it look weird, but it looks the part. Atlas-Centaur. Mercury-Atlas. Atlas-Agena. Also finished but have yet to fly a replica of Pioneer 10/11. Just barely fits in the Atlas-Centaur payload shroud.

If you're interested in alternate Shuttles, I have this: It's a Saturn Shuttle. Surprisingly, it flies pretty well, and makes orbit (90x90km, roughly) with about a fifth of the external tank left. Unfortunately not all stock, as it uses SpaceY parts for the S-IC. Thrust-to-weight ratio is also pretty low just after staging (which is to be expected).

Gemini! Debating if it's big enough for a release.

In between testing more craft for SpaceY Saturns, I played around with RoverDude's Orion/Medusa mod: 102 days to Duna ain't bad, right?

Finally figured out how to stick a Mun buggy on the LEM! However, it tends to... roll. More development is needed.

Thanks for featuring SpaceY Saturns this week - I'm honored to be among so many awesome crafts!

I seem to build Skylab a lot. Like way back in 0.17: But here's the most recent one: And a wet workshop built on-orbit out of a converted S-IVB: As well as Skylab II (built in preparation for a Duna expedition).

I hope this isn't extreme thread necromancy, but I built a large portion of the Saturn family of rockets with SpaceY parts. I don't think there's a single one that gets above about 160 or so parts, meaning they're perfect for meh computers. I call it SpaceY Saturns.

Sorry this took a little while longer than I anticipated, but the Saturn IC/Multibody is finished! SpaceY Saturns Eyes Turned Skyward lifters! Saturn IC: The powerful yet economical (only 55 parts) Saturn IC uses a single Emu engine as a substitute for the single F-1 that the "real" thing had. Pretend it's an F-1B if you'd like. After launching, throttle back to 2/3 to help prevent laggy aero effects. The S-IVB reaches orbit on fumes. Comes with a free resupply/logistics module as a default payload. Downloads: With Apollo spacecraft. With payload faring. Saturn IC2S: A step up from the IC in terms of payload performance, the IC2S is merely a baseline Saturn IC with two solids strapped to it. Equivalent to the Multibody M22. Downloads: With payload faring. Saturn IC3 Stretched: NASA's heavy workhorse in Eyes Turned Skyward, the Saturn IC3 Stretched features an enhanced S-IVB (S-IVC) that allows it to rival the Saturn V. Equivalent to the Multibody Heavy H03. Downloads: With Apollo spacecraft. With payload faring.

Quick update: Unfortunately, the Saturn Multibody probably won't be happening due to the fact that the orange tank arrangement I came up with is horribly inefficient. To make up for that, I'm working on a new type of vehicle based off of the Saturn IC called the Saturn IC3. Basically, it's a Multibody without the orange on the first stage. I have yet to give it a proper shakedown cruise, though, but I think it'll have a slightly better payload than the IB. TWR's already excellent, I think it'll play well with the AARDV and the Centaur kit. Expect that to be released soon. Are you referring to the Saturn C-5N? If so, that'd be a fairly easy one to throw together - SpaceY Expanded has a set of vacuum engines that make really good representations of NERVAs. I'll have an upload ready by tomorrow. If you want one with a proper NERVA, I'll use the four-chambered one from Modular Rocket Systems. The Duna spacecraft I'm also working on (spoiler: it's based off of Ares from "Voyage") won't use vaccum/NERVA engines, for the record, because the TWR is painfully low.