cmoody

I play on a mid-2012 MacBook Pro. I usually have to play with the graphics (effectively) off and with the physics slider at the max delta-t, which may allow me to run in the "green" frame rates when waiting for a maneuver node to come by. If I'm doing anything else, I'm solidly in the yellow. Wouldn't multi-core and 64-bit support solve some of these graphics "issues" people are having? I feel that a lot of my computer's potential is being missed and that I'm getting the short end of the stick concerning a lack of such support.

They need to move over to a proper game engine before they should work on that.

Used to live in VA. Hope you're having fun.

I just want an engine that will use all of the cores in my computer to their fullest extent. Thanks, devs.

I play on a MacBook Pro, so I kill my graphics but changing the delta-time seems to not do too much. Graphics are the biggest problem for KSP because it runs on a 32-bit engine while most of our OSes run at 64 bits. If you have more than about 2GB of RAM, you'll not get too much from changing the delta-time. Once Squad removes their craniums from their rectums and moves KSP to a 64-bit engine that actually uses 2+ cores, we'll see a significant increase in performance.

I use RemoteTech2 as my drug of choice. Makes probe missions pretty complicated when you go farther out. I'm currently trying to build a Kerbol Communications network in Career Mode, which is taking enough time... However, I will agree that after a while things start to get a bit slow. But his looks like fun: http://wiki.kerbalspaceprogram.com/wiki/Planned_features#Celestial_Bodies mmm...20 moons...

This leads me to think this: When first playing with RemoteTech, I had similar issues. However, for my Kerbin-orbit Comm satellites I aimed for overkill on the omni antennae. Oddly enough, this Kerbal-rigging fixed the problem. For what I have in the local Kerbin system, there seem to be too many antennae and not enough targets...time to expand.

I recently did a series of three launches into orbit, followed by consecutive burns for a grand tour of Jool and Eeloo. One probe was sent out of the system using gravitational assists while the other two used reverse gravitational assists (with a lot of recalculated burns, as I use RemoteTech) to fall into orbit. It was pretty epic.

Eeloo b/c yes

Run Mechjeb. If you're an audio-visual learner like myself, learning by observing what is done can help immensely. I used to have these issues with Mechjeb (v. 2.1) upon initial startup, but after returning to default settings and reloading the game (tl;dr: turned it off, turned it on) the problem disappeared. Protractor is wonderful.

The log function in MatLab in the natural log. (Source: GEEN 1300 General Computing for Engineers) This is your problem. Make your specific impulse a linear function (which it won't be in actuality) from sea level to vacuum with the endpoints the values given in the part info box. You'll see that your equations is much more accurate. Also note by Newton's equations that gravity is NOT constant with altitude. While this is not terribly important, you'll find that your numbers are still coming up short.

Key word right there.

I've been trying to build a space station in the Jool system...so yeah...

"70% of all software issues can be fixed by turning off the computer, waiting 30 seconds, and then turning it back on again. 25% are fixed by uninstall, then reinstall. The last five are making sure your hardware, firmware, and software play well together." Good old dad. Told me this when I was 10.

I've heard there are many issues with freezing and crashing NOT attributed to graphics/physics setting and hardware. Mine seemed to be with wanting to have a 4k experience on a MacBook Pro. But in all seriousness, form follows function. I'm not too concerned with everything else, just a fun, smooth, efficient game experience.

We'll have n-body physics, "real" atmospheric simulations (minuscule drag extends far beyond 70,000 m and reentry), asteroids, space junk, and more parts and skins. A few more planets/moons and/or multiple solar systems to choose from when playing. More training, career mode, co-op/online play, and resources. I think the biggest thing will be the spawning of a separate version that has n-body physics, much more accurate atmospheres/reentry, the works, while you can get the current "complexity" version if your computer isn't that strong.

Granted, but it malfunctions in some horribly epic fashion (am I the only one who this happens to?) I wish for a peanut butter and jelly sandwich.

Welcome to the community. If you build the craft like it is in the video, there shouldn't be any problems. Make sure you modulate your throttle so you keep a respectable speed. (~140m/s up to 12,000m, then work slowly up to 500 m/s until orbit)

I use it for long-term probe missions and efficient/low-part/low fuel missions when I have the time. Takes forever to get anywhere, though.

Cool. It has been acquired.

As a Chem. E. major, some of the physics stuff blows my mind but most of everything else is simple (at least to me). It boils down to a few things: -Have more thrust than mass -If you want to go faster, burn prograde -If you want to slow down, burn retrograde -Use maneuver nodes and follow the blue thingy -Don't crash into anything to quickly, or you will blow up and die

Hello, all! I'm Chris and this seems to be my first post ever. I recently got into KSP and have been enjoying it almost too much. However, I have noted a few problems with running it on my laptop. I was wondering if any of you all had similar problems and what you did to correct them. Symptoms Slow opening save file, can freeze Freezes then crashes computer opening Vehicle Assembly Building (about 33% of the time) Frame rate drops extremely low in atmosphere, but does not freeze of crash When doing any sort of maneuvers in orbit, frame rate will flicker between green and yellow On Terminal CPU % Used will shoot to up to 110% I have a Mid-2012 13" MacBook Pro (inb4 Mac Attack). It has the "2.5 GHz (3210M) Intel Core i5 with 3 MB on-chip L3 cache, 4 GB of RAM, and Intel HD Graphics 4000 with DDR3 SDRAM shared with main memory." (sourced from http://en.wikipedia.org/wiki/Macbook_pro#Technical_specifications_2) After talking to a few of my friends who are Comp. Sci. guys, they said it was with my RAM. I am curious to know if this is the case or they are completely wrong and it is something else I may have overlooked. If it is the lack of RAM, what is the amount that will eliminate the problems? I really love playing the game, and I want to find a solution that will fix this. Thank you for any help in advance!