Tarheel1999

B9 hasn't been updated yet so reinstall is unlikely to help. Not sure about the dependencies it relies upon.

I think the idea is that you do other stuff while it processes science and check on it every now and again. Clearly like many things it can be exploited if you so choose. In addition, it creates purpose for the scientists.

Obviously. None of this in dispute. I started this thread to bring this bug to the attention of both Squad and fellow players. But this bug does not "block an entire mode of gameplay." Rather it is a inconvenience and it prevents players from using a cool and helpful new feature (the gauges). The sky is not falling chicken little. - - - Updated - - - Funny. I wasn't shot for reporting the bug (look at the OP) but for being insufficiently melodramatic when doing so.

You need to click the atmosphere button in KER to see the thrust on the launchpad. Otherwise you get the thrust in space. Which is substantially less for upper stage rockets like the 909.

It seems to get worse when the gauges turn red and the parts start glowing. It happened to me on re-entry from the Mun. 4 landing legs and two flood lights seemed to be the main cause but I also had some solar panels, parachutes, and two experiments higher up.

Except of course, it does nothing of the sort. Press F10. Problem solved. You are no longer prevented from flying SSTOs. Or if this upsets you so much stop playing until Squad releases a fix. Considering the amount of button pressing this game requires, you are not going to convince anyone that pressing F10 once when the heat gauges show up is a hardship.

The temp gauges leak only happens when the gauges are visible. That seems unlikely to be the problem here. You are probably going to have to provide more info for someone to help. Look at the stickied post on requesting support/reporting bug for what info is needed.

I have not seen any posts from people with 4-8 temp gauges displaying where there wasn't a huge leak. Several people have stated they haven't experienced it but haven't asserted they had multiple temp gauges showing. In the second post, I included a quick save from a completely stock install which causes a crash inducing memory leak during re-entry. Now it would be interesting if only certain systems/hardware had this problem but there is no evidence of that. Update - The memory leak seems to be more severe when the gauges turn red and the parts start glowing. It's possible that those people only temporarily seeing green gauges are not experiencing crashing but are likely seeing small memory leaks.

It happens to me in Windows 7 (English) when I forget to plug in my Logitech joystick.

Regex - Don't you think those values will make interplanetary returns rather difficult? Even if re-entry takes multiple orbits to minimize heat you will have probably used up your heatshield after one or two orbits and have nothing left for the actual re-entry.

So hit F10 to disable the gauges.

FYI. Placement of the wheels seems a lot less finicky in 1.0/1.02. So far I haven't had any problems placing rear wheels at the very back even with a CoM in the center of the craft.

Truth be told, I preferred editing the cig file once I figured out what the numbers corresponded to. Same with sensitivity and deadzone.

I had the same problem and ended up doing the same thing. Sal - is there a toggle for primary/secondary? If not do you know what the intended use case is?

I was wondering the same thing. I spent about an hour today trying to get the axis settings right. I ran into a problem with KSP failing to properly set up the modemasks (staging/rotation/docking) and had to manually edit the settings file (and engage in a lot of guesswork). I'm not sure if this is a KSP bug or a problem with having KSP in the program files directory (seems unlikely as KSP has never had a problem modifying files there before). A link to a "How to setup a joystick in 1.0" would be greatly appreciated.

Radially attached parts cannot be shielded from aero effects (only parts attached to nodes are occluded/shielded). Not sure how aero and thermal interact but this could be part of the reason in addition to the mass differences.

You also need this. http://forum.kerbalspaceprogram.com/threads/118088-1-00-ModularFlightIntegrator-1-0-%28Apr-30%29

Totally fair if you take into consideration how the KSP save file/persistence system works. For example, launchers with probes become "vessel name probe" after separation. I assuming "the two different vessels" requirement expects you to conduct a proper rendezvous.

The leak only occurs when multiple parts are overheating and the temp gauges show up. A capsule or capsule plus heat shield is unlikely to cause a leak. I got a leak with a min lander with 4 landing legs, two floodlights, and several Ox-STATs. The exposed parts all started to overheat. No leak when gauges don't show up or are disabled.

Scott Manley has a new set of videos on career mode. Take a look at episode 5. He puts a simple rocket in orbit and shows the proper ascent path. You need to give yourself a little more time and try and forget the bad habits you picked up from stock aero. It took me a while to figure out how to launch rockets with FAR in .25 the new aero has a similar learning curve.

working fine for me. Every now again I get the occasional flip when testing a new rocket. I launch at 1.2-1.3 TWR. With that setup you probably need to lower the throttle. Overspending will create stability problems at low altitudes. Add fins to bottom of rocket. Stay within 5 degrees of prograde marker.

The out-of-memory crash range for KSP in Windows is about 3.3-3.7. So either you are an outlier, not running KSP in Windows, or KSP is not actually sitting at 3.8 all the time. Even with the improvements memory still steadily increases in 1.0.

Nightingale - Just a heads up. The link in your release post below still points to 2.3.1.

The gauges show up when parts are overheating.

Nope. And it's almost definitely the temperature gauges as the memory leak is not present when you disable the gauges using F10.