An-2: It is not possible to start the variant with GPS

ISSUE DESCRIPTION

Description of the issue:
The modern variant of AN-2 doesn’t start. Not even using Ctrl+E. Classic version works correctly and it starts without any problem following the same procedure.

I’ve tested the same procedure with the same variant in FS2020 and it works correctly.

UPDATE: I have tried to load the plane (the GPS variant) running directly on the runway. From there, after putting it in cold and dark, following the checklist, the airplane starts correctly. If I start from a parking position in cold and dark, it does not start following the checklist procedure. The classic version starts correctly.

If applicable, which aircraft is experiencing this issue:
Antonov AN-2 GNS530 variant only. Starting cold and dark.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Initially, I detected the problem using a cockpit modification with translated labels. But after disabling the addon, the same problem happens.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Everytime

REPRODUCTION STEPS

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

  1. Select AN2 (GNS530 variant) in a parking spot, in cold and dark state.
  2. Follow the checklist
  3. It doesn’t start

YOUR SETTINGS

What peripherals are you using, if relevant:
Not Relevant

[PC Only] Are you using Developer Mode or have you made any changes to it?
Not, I don’t

[PC Only] What GPU (Graphics Card) do you use?
Asus 3070 TUF

[PC Only] What other relevant PC specs can you share?
Not relevant for this case.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

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

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I’ve updated the first post with more information: the problem only appears if we start the session in cold and dark.