Double Timan

Generally I'd say most things are too big (menus, labels etc) hard to see as you say. Also the centre of mass or the centre of lift seem to be off significantly... building planes I'm getting very unpredictable performance even with a good Cg and CP indicated.

Same issue

I've noticed that the wings generally end up upside down if attached to another wing (to make a cranked arrow delta or something like that)

I noticed my fairings leaving in odd directions as well. There seems to be vortex whisper lines as if flying in a drastically different direction than actually moving when in the upper atmosphere so I wonder if this is related as well.

Related issue, typing notes on flags often triggers the game to pause or other key commands. These commands should be locked out in these scenarios.

The estimated burn time in ksp1 was very useful but the ideal time to start the burn is often not 50% of this time. It would be nice to be able to set the start of burn time and show a burn line rather than a point. The more the rocket will change in mass and speed over the burn, the earlier the burn should happen. I wont get into the math on a bug forum but the current warp to node landing right on the node is definitely not useful.

Ya just took off from Duna, same issue. I noticed the lack of trajectory and then noticed the landed status in the tracking station. I also had an issue with the engines only lighting when deactivated for take off from duna on the same mission.

Also wondering this

kahlzun you are absolutely correct and this is the whole reason that gravity assists from other planets can also help with reducing the total delta-v of a mission in the real world. On the later Apollo Missions one of the ways they could reach the sites they wanted to on the moon with the addition of the lunar rover was launching into a lower parking orbit. The orbit was actually low enough that it would have decayed very fast however the time from insertion to trans-lunar injection was short enough that the drag penalty was well worth the delta v reduction. The simplest way to understand the effect is to look at the definition of work which is a force multiplied by a distance. The force generated by a rocket is constant and related to a given expenditure of fuel in a given time. The work done by a rocket in a given period of time (dictated perhaps by how much fuel is on board) is given by the distance travelled in that time multiplied by the force exerted by the rocket. Distance travelled in a unit of time is speed and so you can say that work done in a unit of time is given by the speed multiplied by the thrust which has the interesting result of yielding more energy from the same burn if you burn while travelling the fastest. Highest velocities in any trajectory are on closest approach to a massive body due to the exchange of potential energy for mechanical energy. This means that you should always plan your burns at as low an altitude as is practical. The energy gained however is not free it is the result of the kinetic energy of the fuel as well as an exchange of energy with the body being interacted with gravitationally. Since the object is huge the inverse effect is not measurable. The effect holds in KSP and is very useful for minimizing rocket size.

I Have been experimenting with using a derivative of a rocket I used for landing on the mun that was made only from the base parts to escape the solar system and actually was able to reach a very high hyperbolic excess velocity and leave the system at a very high rate of speed. I left the system at top time compression all night and woke up to see that the whole system was barely visible in the map view and I was still travelling at over 10,000 m/s. The way I did this was essentially a dual gravity assist (sort of) You start on a launch pad on Kerbin travelling around the center of mass of kerbin which has a the mun travelling around it and which travels around Kerbol. I started the mission and waited 4 night cycles by speeding up time right away and then launched eastwards into a minimum orbit just a hair over 70,000 m. the waiting had put the mun in the right position to perform the gravity assist as my intercept point would be the point in the orbit of the mun where it is traveling around kerbol faster then kerbin (outside of the orbit) Which also happens to be my launch direction. I came in behind the mun and lowered my hyperbolic trajectory to just 800m over the surface on the far side. When I reached close to periapsis, I fired the engine full throttle, shed my 'descent stage' and fired the ascent stage until cut out. this left me traveling faster then the mun by about 6000 m/s which was traveling faster then kerbin which in turn is traveling around kerbol...... all in all this left me in a trajectory about twice the velocity of kerbin (at periapsis) in the Kerbol system and I went sailing off with far more then escape velocity.