C152 Fuel Pump Cannot be Re-enabled

ISSUE DESCRIPTION

Description of the issue:
When using the Auto Shutdown key in the Cessna 152, the Engine Driven Fuel Pump is disabled. Starting the plane from dark and cold in this situation is no longer possible after this state, there is no way to enable the fuel pump except in the developer console.

Breakers could also trip which cannot be pushed in as well.

FREQUENCY OF ISSUE

Occurs on every attempt.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load into the Cessna 152 at any airport on parking.

  2. Enter aircraft and press the auto shutdown key.

  3. Do the Starting Engine checklist.

The issue is that autoshutdown disables the engine driven fuel pump. You cannot bind a key to enable the fuel pump in the C152. In the actual C152 the fuel is gravity fed not through a fuel pump.
Additionally there are no ways to push in any tripped breakers, such as the starter.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?
Using developer mode to debug, not needed to reproduce.

[PC Only] What GPU (Graphics Card) do you use?
RX7600

[PC Only] What other relevant PC specs can you share?
AMD CPU

MEDIA

Looking at the behaviors for the fuel system: After AutoShutDown

After AutoStart

Can replicate.

How have you been able to determine that the engine Driven Fuel Pump is disabled ? (through the dev mode maybe). Any screenshots ?

Note: the C152 Aerobat does not have this issue.

Edit: thanks for having added screenshots

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes

Provide extra information to complete the original description of the issue:
• Good use of the debug info, OP!
The 152 has triggers set up for auto_shutdown where it turns off the EDP. The Aerobat does not have those triggers configured. Removing it fixes this issue.

If relevant, provide additional screenshots/video: