ISSUE DESCRIPTION
Description of the issue: The Saab 340, in the flight deck, has levers for throttle and engine condition, but not propeller RPM. However, if controller axes are assigned to propeller, they have an effect. This seems unintentional.
If applicable, which aircraft is experiencing this issue:
Saab 340 (also same issue on the VL-3 going back to MSFS 2020)
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
yes/yes
FREQUENCY OF ISSUE
always
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- load Saab 340 (or VL-3)
- assign a controller to the propeller axis
- observe that it has an effect when no such control exists in the plane
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:
Bravo, but irrelevant
[PC Only] Are you using Developer Mode or have you made any changes to it?
no
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
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:
•
Yeah technically it should be the fuel levers on peoples setups that move the condition levers, and that is what changes the pitch of the propellor blades in the actual aircraft. (Source: former Saab 340B CA)
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:
• The prop levers on my Honeycomb Alpha impact the engines, however they don’t cause any levers to move including the condition levers. Furthermore, I can’t seem to bind anything to the condition levers in a way that works.
If relevant, provide additional screenshots/video:
• N/A
I don’t know if it’s as simple as the prop and condition levers being mapped wrong. It’s very confusing because I’m 90% sure that can move the condition levers to Max in the VC but the prop levers still have an impact on top of that.
If only that were the only problem with the Saab. The thing has 1,000 bugs!
What bothers me most about Carenado aircraft is that Carenado doesn’t support turboprop/turbocharger simulation, and its “Cargo loaded”/“Cargo unloaded” aircraft are always reversed. This means that you can’t load Carenado’s aircraft with the visual representation of cargo in EFB. Carenado generally swaps left, right, and up with down, as you can see with all the switches, and the Saab 340’s cockpit camera quick view transports you to the cargo area, but you can’t see anything.
How can you not see such fundamental bugs during testing and bring the products to market like this?
The number one question.
Given the state of some 2020 aircraft and how they performed in 2024. I have a developed a suspicion that some of the new default 2024 aircraft might have been created for 2020 originally, and then loosely ported over to 2024 with a walk around mode and nothing else. This is the only way I can see major functions such as the condition levers and inverters not working.
Bring the Saab to 2020 and I bet it will work just fine.
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:
•Still broken after 8 months
If relevant, provide additional screenshots/video
Still an issue today, what a weird bug, if you map a condition, or a prop axis, neither does anything, but a feather or prop idle will do something, but levers wont move. This aircraft needs some work
ISSUE DESCRIPTION
Description of the issue:
Can’t map the Condition Lever in the Saab 340
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:
-
Go to the mapping table and try to map the Condition Levers
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:
Honeycomb Alpha & Bravo
[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?
no
[PC Only] What GPU (Graphics Card) do you use?
RTX 4070ti
[PC Only] What other relevant PC specs can you share?
MEDIA
Please add a screenshot or video of the issue occurring.
Neither of those worked for the Saab. Looking in developer mode looks like there are variables
Thanks