adinfinitum

I'm no aerodynamics expert, but shouldn't body lift also be perpendicular to the part, just like the lift vector is perpendicular to the wings?

I haven't placed surface attached parts on the ceilings of the bays, but, at least in my experience, attaching a part to the ceiling attachment node is best avoided. I've actually never had problems if I clip into the service bay ceiling, as long as its attached from the floor up.

Got anything attached to the ceilings of those service bays? That's pretty much an invitation to the kraken, not sure why it would happen in one situation and not the other though.

One thing you mentioned is that the SAS always tries to return to where the last steering input stopped, I believe this part was an intentional design choice. It was a while ago, so I might not be exactly right, but in earlier versions of the game the SAS only held the heading at which it was engaged, and to change to a new heading you had to disengage the SAS and reengage once you had reoriented yourself. It was then changed that SAS would be automatically disengaged and reengaged when there was steering input. I don't have any sources other than vague memories, so if I'm wrong someone please correct me. The easiest way around this issue is to just tap the F key once you reach your desired heading, that resets the SAS so that it doesn't try to return to where steering input stopped.

In the spirit of space travel, I would have to say any food that comes in a squeezable pouch is good, and it keeps your keyboard clean too. Of course, the hard part is actually finding food like that, so I just stick to food that doesn't get your hands greasy or oily.

Along the lines of aesthetics, I wish that the game had versions of the landing struts that retract into streamlined bays. While not necessary, I personally prefer the streamlined look more than the utilitarian look, and it would be nice to have the option with landing struts.

I've had some similar weirdness with the trajectory plotting, but it's been in the Kerbin system. In my case it hasn't been the second encounter that doesn't display, but the first one. Specifically, there have been multiple times where I set up a Minmus encounter that also happens to encounter the Mun on the way back. After I have it set up and warp a little bit, the Minmus encounter disappears, leaving me with just the Mun encounter shown. If I'm careful and cross Minmus' SOI at warp below the highest two levels I enter the SOI as expected, and the shown trajectory is now correct. If I use those top two levels of warp I pass through the SOI without it registering as such, and continue on the previous trajectory that leads to a Mun encounter. This may be related or it may not, but there definitely seems to be some weirdness when the trajectory has multiple encounters.

I've got to agree that I'd rather have no description than what they've got now. Maybe I've just played too much Dwarf Fortress, but the KSP random description generator seems rather bad. Especially since they usually have nothing to do with the goals of the contracts, and seldom make any logical, or illogical, sense.

Unless you're using nukes you do need to add in the mass of the oxidizer.

I may be wrong in my math, but the equation listed is for a constant heading burn, and so a straight line velocity vector. Following the normal marker gives you a curved path, and so is less efficient.

I think it's just how KSP handles any sort of decoupler, whether it's launch clamps or whatever. I like to stick my launch clamps up high because it keeps it above the CoM, and I just like how it looks. This always makes them stage somewhere in the middle of the sequence. It seems the way it works is whenever you attach any decoupler, the game creates a new stage in the sequence below the stage of whatever the decouplers are attached to.

The burn time given by the game is simply the time required to accelerate the planned amount of dV, at the ships current max acceleration, given in the ship info in map view. From what I've observed it doesn't take into account the change in mass as fuel is used, so the longer the burn is the less accurate the displayed time is. I've searched an answer for this question before, and while I'm on my phone right now and don't have the link, I found that burning in the same direction as prograde at the maneuver, half dV before the node and half after, is the best approximation of an instantaneous burn. In other words, point at the blue maneuver marker and start at half the expected burn time to be the most accurate.

Besides SSTO to orbit space planes having the cool sci-fi factor, their advantage is that you recover the full cost of parts minus fuel. The cost of losing a few empty tanks really isn't much at all, and while it is a small distinction, I consider it much closer to SSTO than a traditional multistage rocket.

I'd have to say that if hovering the cursor over it and using the mouse wheel doesn't work, it might just be a problem Squad didn't consider happening.

Are they deleted when a craft is deleted in game, or do they stay then also?