FADEC problem, VL-3 Unplayable

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

:white_check_mark: SIM INFORMATION

MSFS 2024
XBOX series X as per 21.11.2024

:white_check_mark: ISSUE DESCRIPTION

  1. Description of the issue:

The starting RPM on FADEC while flying VL3 are always red lined. After I tried to bring them down with propeller axis (I know that fadec shouldn’t let propeller lever do any change but I tried anyway). After I touched it, the RPM halved, and now, as plane is remembering last settings, I cannot take off after restarting mission. I cannot make RPM go back with any key. The plane become unplayable with RPM stuck around half, so even with full throttle it barely lifts.
2. If applicable, which aircraft is experiencing this issue:

JBM VL3 but knowing how this is fadec related and it is occurring since 2020 propably DA40 too.

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

Yes, never used mods

:white_check_mark: FREQUENCY OF ISSUE

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

Every time

:white_check_mark: REPRODUCTION STEPS

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

  1. Fly career mission with JBL VL3
  2. Use prop lever on turtle beach or any other way to put down RPM
  3. The rpm will stuck forever in half

:white_check_mark: 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.

  1. What peripherals are you using, if relevant:

  2. [PC Only] Are you using Developer Mode or have you made any changes to it?
    No

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

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

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

:white_check_mark: MEDIA

Please add a screenshot or video of the issue occurring.

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

So quite possibly VERY related issue, in the cockpit of the VL-3 there is no RPM/propeller axis physically there. This seems like one of those planes where there’s just a throttle, no mixture or prop control.

And yet, if the propeller control is mapped to a peripheral, it works as if this plane has such a control on it. This isn’t new in 2024, has been there all along in 2020, always meant to make a thread about this but never got around to it. So this phantom propeller/RPM axis might be what’s causing OP’s issues. I’ve long suspected something’s janky about the way the VL-3’s engine is implemented.