

ColourOfFire
Members-
Posts
67 -
Joined
-
Last visited
Reputation
75 ExcellentProfile Information
-
About me
Rocketry Enthusiast
-
To add on the CKAN thing, don't know the current status, but when I tried a while back it was such a pain in the ass on OSX I just installed the mods manually. I'm not going through the whole homebrew install process only to find out it doesn't want to recognize my KSP install just to get some stuff I can just download and unzip...
-
It's very weird that the newer macbooks seem to have more issues. Maybe it's because my old one can't handle fancy graphics anyway, so I turn them down quite a bit. Even mods don't hurt stability on mine, only several huge packs like KW Rocketry and B9 running together runs into problems.
-
Same here, no issues on a 2011 macbook pro. My 0.25 did crash/glitch every once in a while, but that had a ridiculous amount of mods on it.
-
The hidden secret, of the mk2 cockpit interior space!
ColourOfFire replied to SeniorFight's topic in KSP1 Discussion
I'm terribly sorry, but if this is unforgivable you're going to have a hard time living in 2015. It's unnecessary and useless but come on, not unforgivable. Btw, if you're so offended by this, do you realise you just posted it uncensored on a forum kids might be watching? -
No. It does not change the physics calculations, it just unlocks the ability to use different threads to do it, so it can use more of your computers memory. It's not going to help gazillion part spaceships, it's not going to make miracles happen. Of course, more memory to play with and the updated physics engine might mean there will be improvements, but purely changing from 32 to 64 bit will only makes certain things run a little faster.
-
And people pointed out factual errors in that opinion, no need to get so defensive. You were the one that came in here trying to vindicate an old post of yours...
-
Well of course re-entry heat and working aerodynamics are very weird and unique features to implement in a game about space flight... Until there's code that shows they copied stuff this line of thought is completely ridiculous. AFAIK the implementation of aero in 1.0 differs a lot from the way FAR used to handle it with pre 1.0 stock...
-
In addition, I read (I believe in one of the devnotes) that even though 64 bit might happen, we shouldn't expect huge part counts to be suddenly a lot smoother, as single ships will still need to be in one thread. It will still be faster as other loads can be spread, but don't get overhyped.
-
Debris cluttering up save files
ColourOfFire replied to MLWostal's topic in KSP1 Gameplay Questions and Tutorials
Probably because erasing/storing debris with the save game loaded and active is not a great idea -
Unless you're on a mac... I much prefer the unzip in gamedata way.
-
Ever feel guilty when dropping nuke engine on planet?
ColourOfFire replied to enroger's topic in KSP1 Discussion
I never drop them, usually they are on a dockable stage that stays in orbit, gets refueled and goes for more missions. -
Tell your story. How did you get to KSP 1.0
ColourOfFire replied to Ival70's topic in KSP1 Discussion
Can't remember if it was .21 or .22. Steam kept recommending this weird game to me, it was on sale and I was in a good mood, so I bought it. No regrets -
It's fun. Why else would you be playing it. At times when I think it's not fun, I do something else. That's the whole point of videogames IMHO.
-
How Much Time Have You Spent Playing KSP?
ColourOfFire replied to SelectHalfling0's topic in KSP1 Discussion
Steam says 234, but that's mostly my very first save and the current one I just started to play stock career. Most of my time was spent on heavily modded copies outside steam. I think the total will be somewhere between 750 and 1000 hours.