Autostart (WIN+Home) - Canopy not locking

[Tusky]

Hi all!

When performing autostart, the automatic checklist (upper right-hand corner) mentions "Canopy locked" without actually locking it (the canopy and master caution are lights are on). You still have to manually click on the handle to lock it.

Thank you!

P.S. I know that autostart is a big "no no" but:
1) For my first flight, I didn't want to go through the whole startup procedure
2) It is still beta, right?

[6S.Duke]

Hi, thank you for reporting.

Solved in our internal version. It will be available with next update

[SlipHavoc]

On 10/29/2022 at 5:25 AM, Tusky said:

Hi all!

When performing autostart, the automatic checklist (upper right-hand corner) mentions "Canopy locked" without actually locking it (the canopy and master caution are lights are on). You still have to manually click on the handle to lock it.

Thank you!

P.S. I know that autostart is a big "no no" but:
1) For my first flight, I didn't want to go through the whole startup procedure
2) It is still beta, right?

For me, autostart is a big "yes yes", and I use it all the time, and have already made an optimized startup script for the MB-339, although I'll probably hold off from putting it up in the user files until the first MB-339 patch, as I expect that may change some bindings.  However in the meantime, you can modify your Macro_sequencies.lua file, replacing all the cockpit-related lines with this block:

 

Quote

push_start_command(0.2, {device = devices.SWITCHES, action = CanopyUnlock, value = 0.0})
push_start_command(0.2, {device = devices.SWITCHES, action = CanopyHandle, value = 1.0, message = _("Canopy Closing"), message_timeout = std_message_timeout})
push_start_command(3.0, {device = devices.SWITCHES, action = FwdCanopyLockUnlock, value = 1.0, message = _("Canopy Closed and Locked"), message_timeout = std_message_timeout})