Update;
This was posted 8 moths ago on another Forum.
Is there a way to set the propeller rpm in the Diamond DA40? When Cruising it seems to constantly be getting itself into the red and flashing the warning. Even when throttling back it does not see to make much of a difference, rpm reminds high. Is there a way to fix this…
That’s a serious bug since day one and you can’t adjust prop RPM.
AFAIK there’s a patch available for the NG at flightsim.to.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No. Xbox.
Brief description of the issue:
Despite the pilot having no control over the RPM’s in the DA40NG, the plane flashes an intermittent, flashing warning about over speeding RPM’s. This problem did not exist at Xbox launch. It was introduced in a System Update several months ago. There are other planes with this problem (JMB VL-3) but the placement in the DA40NG puts the flashing indicator directly in the pilots line of sight.
For PC users this is less of an issue, as there are mods that address the problem, but on Xbox there are no such solutions.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Go for a flight. It doesn’t flash 100% of the time, but you will see it every single flight.
PC specs and/or peripheral set up if relevant:
Xbox Series X
Build Version # when you first started experiencing this issue:
A quick search of the archives will show this problem has been around for a while.
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:
Dose this issue only occur on the 40NG?
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:
Xbox no stock engine management unit modelled
If relevant, provide additional screenshots/video:
Xbox + g1000NXi
Is this for real? June 2022. All aircraft that come with FS2020 (no matter edition) SHOULD get overhauled, and looked over. This needs to be done!
I have not yet tested the enhancement. Will it help?
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:
Still an issue after WU10.
Still an issue, the VL-3 also.
It’s still going to be an issue after SU10 too. According to the SU10 beta release notes the DA40 will not get an update: https://forums.flightsimulator.com/t/sim-update-10-beta-release-notes-1-27-9-0/528823
I don’t understand why MS / Asobo and whoever is in charge of acknowledging bugs reported here (with the bug-logged tag) is ignoring this for 2 years now.
When the simple avionics in 2 of the base planes don’t work (in Discovery Flights no less), the bug should be acknowledged and put on a list to be fixed…
For new users, it’s a surprise that things don’t work as they should, especially in the base planes. You learn it’s a work in progress - fine. And MS / Asobo have this bug-reporting forum - great. But why are they refusing to acknowledge the bug and add it to a list for future fixes…?
Bueller?
Bueller?
Anyone?
@Jummivana this bug was reported 15 months ago; any chance can we get a “feedback-logged”?
@Jummivana … or at least some guidance on how bug reports here are “accepted” or not? I’m doing the Xbox Stability Test, the MSFS SU10 Beta Test, and so on, in order to report bugs. But if the bugs we find are not acknowledged here, what’s the point? It’s very frustrating. Thank you.
Why can’t I “ping” community team members? I’m trying to notify about an overlooked bug. Isn’t that what the functionality is for?
I’d be happy to do something else instead, but I’m not sure what. What do you recommend to get the attention of the community team? I may have missed some documentation, but haven’t found any relevant docs yet. Thanks for your time!
(The only documentation I can find for the foums at all is the code of conduct, which doesn’t really address the issue clearly. It’s possible I’m meant to send a private message to “@ - moderators”? But this would seem to be for a moderation issue; I’m trying to ensure that bug feedback has been relayed to the development team.)
Fair enough; we’ll keep bringing in the votes. 
Thanks for the clarification!
(I’ve been on the other side of software with a long list of bugs, so I get it. We must all have patience! :D)
Hester, MS / Asobo should be interested in ALL bugs. This particular bug is a good example because: (1) it affects 2 default aircraft (2) is pretty much the first thing that goes wrong in a handful of Discovery Flights (3) every new user experiences it (4) the default planes should work properly for the 40th anniversary and (5) has been reported for over 2 years without acknowledgement.
I want MSFS to be successful - I see the huge potential. However, as a new user, I am hesitating to spend any more money because so far after 2 months I’ve had more crashes than successful flights, I’ve signed up for all the beta tests to help in a small way, but then I find the bug reporting rationale is arbitrary.
Here’s a screen shot of the MSFS Official introduction series, from 2019, of Asobo’s Martial Bossard explaining how the cockpit instruments are “modernized with extreme details and script to behave exactly as they should…” Sounds great. I also get that it takes time, there are always bugs, etc. I love the progress and am a fan still. However, since you are reaching out to the user community for bug reports to help solve difficult issues, please consider a better way to acknowledge reports even if you consider “some bugs aren’t important”. Thanks.
Issue happening in August 2022 still.
still happening, beginning to see why the one pilot I know dislikes MSFS…
This issue is still present, I found this thread after Googling the cause as I’m a new player and am seeing the same behavior.
While cruising I get a constantly flashing RPM at a value of 2100.
It doesn’t matter where I put the throttle it’ll continue to flash. Lowering the throttle will sometimes stop the flashing for a few seconds but then it continues again immediately.
Has this been addressed or confirmed to be looked at by the team?
At the top of the page it is listed as “bug logged”, but when/if it will be addressed is unknown.
