PC-24 - Pressurization and Reference Speeds and Checklist not set correctly in the Epic Avionics


:white_check_mark: SIM INFORMATION

  • Microsoft Flight Simulator 2020 or 2024: 2024

  • Version Build Number (Where do I locate that?): v1.2.8.0

  • Game Platform (Steam, Xbox, MS Store): MS Store

:white_check_mark: ISSUE DESCRIPTION

  1. Description of the issue: The PC-24 has not got its pressurasation and reference speeds set correctly in the panel.xml for the Epic2 Avionics. Epic2 panel.xml Tag Documentation | MSFS Avionics Frameworks and Instruments

There is a few key issues:

The Cabin Altidue is always flashing red, the pressure and cabin rate are not showing correctly

Working Title confirmed that this is due to the Aircraft Developer not setting this up correctly.

The reference speeds for the PC-24 are set incorrectly in the panel.xml they are incorrectly using the PC-12 speeds, this means the aircraft Auto throttle in FMS mode is using the wrong speeds and is trying to cruise at Mach 0.3

The checklist is not defined in the PC-24 but is working in the PC-12

  1. If applicable, which aircraft is experiencing this issue:
    PC-24

  2. Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
    N/A

:white_check_mark: FREQUENCY OF ISSUE

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

:white_check_mark: REPRODUCTION STEPS

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

  1. Launch the PC-24
  2. Fly to FL300 using the Autothrottle (Reference speeds are wrong)
  3. The CAB ALT logic is not working or implemented causing the ALT symbol to flash red
  4. The checklist don’t appear which is required for the No Takeoff message to disappear

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

5 Likes

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

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

If relevant, provide additional screenshots/video:

additionally: it’s not possible to change cruise speed from .470M to anything more appropriate (like 0.6M, which is standard for the PC24 i believe). after entering a different mach number, the MFD simply replaces it with .470 again.

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:
• On the upper MFD, INIT pages, Databases tab, we can see that the PC47E-WT0453 is being used. thats a PC12-47E. not a PC24. so the numbers and programing is for the NGX not the PC-24.

If relevant, provide additional screenshots/video:

This seems to be fixed now.

Yesterday I was able to dial in .7M which this time wasn’t replaced by the MFD.

1 Like

coincidentally i’m just about to do a PC-24 flight now. i’ll see if that works. cheers.

EDIT: it works now. thanks for the heads up.

the speed also for approach seems to be wrong, low close to stall speeds.
Someone know what is the correct value for this airplane?

VREF (reference speed, final approach) | 102 KIAS, from pilatus-aircraft.com.

see the following:

1 Like

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.

1 Like

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:

If relevant, provide additional screenshots/video:

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:
• same here also