Debug Menu Options

[Apelli]

Got my hands on the debug menu,it's fun, but there is a small problem, even when all damage related options are enabled in debug mode, my spaceship still is getting destroyed by the collisions (excluding the fuel tanks), engines and control pod still explode, even with No Crash damage on...

Would like to know, will the devs fix this, or they don't even use the debug mode now?

[pandaman]

Hi, not exactly sure what you mean,

But AFAIK crash damage, as in dents and scratches and gradual loss of a parts effectiveness is not simulated, apart from on a few things like wheels and landing gear etc.

Stuff like engines or fuel tanks either work fully or are destroyed by impacts above their tolerance level.

Hope this helps.

[Kelderek]

I think the OP is talking about how even with the debug options enabled, it is still possible to have your craft explode, which seems to render those options less useful. There needs to be a true invulnerability option.

I just ran a mission to Eeloo where I had landed safely and hit F5 to quicksave after I gathered my science and planted a flag. Later on my ascent I needed to reload my quicksave and parts started to explode on the physics load for the lander on Eeloo's surface. I tried everything I could using those debug options and these parts still blew up every time I tried to F9. Eventually I had to scrap the whole mission and chose to use hyperedit to return the remaining half of my ship safely to Kerbin. That may have been a bug with physics load and the colliders for the lander and Eeloo's surface, but I still would have expected the debug options to protect the vessel and they do not.

[Apelli]

Yes, you are right, it is very sad that it does not save ship parts from any damage, although it would be really easy to implement ;(

Maybe someone who has the information will enlighten us...