So is there a way for us less technically minded to correct this? Or must we wait for MS/Asobo to get its act together?
You can probably add a key binding for it, explicitly starting the right engine. But console users have only limited keys available on a controller, so I have to use the autostart in the end. ![]()
Asobo could easily push a few hotfixes for some of these default aircraft if they cared to. Seriously, how much effort would it take to fix something like the right engine starter?
When I remember it correctly, was one statement for MSFS2024 that streaming scenery and plane is big advantage. That they only need to fix/ update the files on the servers, without creating download packages, which is much faster…
Don’t know if this should go somewhere else but the ECU run up tests don’t work either.
They didn’t worked from beginning.
I remember them working in MSFS 2020. Maybe that was with the DA62X mod.
The default has not this system depth. There wasa mod for MSFS2020, which is unfortunaley, not working in MSFS2024. The smaler one, the COWS DA 42 has it.
But back to the crrent issue. Are there any news about getting it fixed?
Same exact thing happened to me!
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.
Excellent, in the name of all pilots here, thank you for taking this forward! Fingers crossed that a fix will be provided soon. ![]()
Yes, this is such a wonderful plane in most respects, and to not be able to start one of the engines unless you Autostart is a real immersion killer.
Still an issue in the beta I’m afraid.
My god, almost two months later and this STILL isn’t fixed. That’s insane for something that must surely be an almost trivial fix – just swapping which engine the right starter button activates (especially since this is a regression from what was previously working).
Hi, why has this issue not been transferred to bug-logged yet?
Nobody can start the right engine from cold and dark and that is quite a sever bug for a flight simulator.
Garmin 1000 misbehaves during start up procedures and blinks in and off too.
Thanks for the ping on this one! I usually get pinged when the status changes on an internal report to bug-logged from feedback-logged, but didn’t for some reason on this topic.
I’ve now correctly updated the status as this issue has been bug-logged. Unfortunately I’m unable to provided timelines on when issues are planned to have fixed implemented.
Cheers,
Chewwy
Thanks a lot!