FYI - Parachute change I don't think I've heard people talk about

[KerikBalm]

FYI because someone complained about PSAs, but I hope they just don't hate TLAs

If you accidentally activate your parachutes, before they semi deploy you can right click on them and select disarm... at which point the menu option changes to deploy again.

A very useful change if I do say so myself....

[Captain Vlad]

FYI because someone complained about PSAs, but I hope they just don't hate TLAs

If you accidentally activate your parachutes, before they semi deploy you can right click on them and select disarm... at which point the menu option changes to deploy again.

A very useful change if I do say so myself....

Sounds like an excellent hotkey candidate.

[Zephram Kerman]

Found it. Already needed it. So happy to have it!

[RocketPropelledGiraffe]

I also just discovered this. As an additional note, you can activate the chute again via staging after you disarmed it.

[Alshain]

This was part of the Stock Bug Fix integration.

[CaelumEtAstra]

On 11/12/2015 at 5:43 PM, Alshain said:

This was part of the Stock Bug Fix integration.

Really? Kudos to SQUAD then.

[NathanKell]

There's even a way to have parachutes hold off going from armed->deployed until conditions are safe. In the MODULE for the parachute, set

automateSafeDeploy = 1

for deploy on risky, or

automateSafeDeploy = 0

for deploy on safe.

The default (if not given in the cfg), as you might guess, is automateSafeDeploy = 2 (i.e. deploy even on unsafe, i.e. deploy as soon as you arm it).

[fourfa]

Oh, that's lovely!  Is AutomateSafeDeploy independent of specific atmospheres; ie can I just set that and not have to worry about Duna vs Laythe vs Eve?

Can I ask for example code?  What I see of MODULEs in parachute part .cfgs has some syntax I don't trust I'll get right.  For instance, would I add this:

MODULE
    {
        automateSafeDeploy = 0
    }

in line with the other MODULE declarations?

[NathanKell]

No, I mean you'd add it to the existing

MODULE
{
    name = ModuleParachute
    ...
}

You can do it with an MM patch, i.e. make a new cfg somewhere in gamedata and put this in it, and if you have Module Manager it'll be applied to all parachute parts:

@PART[*]:HAS[@MODULE[ModuleParachute]]:FINAL
{
    @MODULUE[ModuleParachute],*
    {
        %automateSafeDeploy = 0
    }
}

This will indeed work no matter the atmosphere, or rather it will work exactly like the display does already.

[fourfa]

Thank you, that will be the best way.

[nosirrbro]

Quite useful! I'll have to make sure to remember this.