Carenado Piper PA-28: Pitot heat stuck in ON position after RESTART FLIGHT

Bug Reporting Hub Aircraft & Systems
, ,
1

ISSUE DESCRIPTION

Description of the issue:
After using the ESC + Restart Flight button, the pitot heat switch is no longer clickable and stuck in ON position. No matter if it was OFF before.

If applicable, which aircraft is experiencing this issue:
PA28

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

FREQUENCY OF ISSUE

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

REPRODUCTION STEPS

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

  1. start cold and dark, get inside the cockpit and see the pitot switch works as it should
  2. press ESC and restart flight
  3. see how the pitot is now stuck in ON

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?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

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

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

MEDIA

PA28 pitot
PA28 pitot1402×685 139 KB

[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:
•

2

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:
• I also seem to get this, occasionally, on first load of the Piper. (I also see issues with the pitot heater switch in other aircraft – the C175 Basic and C185, so this may not be exclusive to the Piper. Disconnecting my peripherals does not fix it, so it isn’t a binding issue that I can see.)

If relevant, provide additional screenshots/video:
•