Very strange engine startup behavior in MSFS 2024
-
I have been struggling with engine starts with the RJ professional in MSFS 2024 since it became available in the sim, but I have finally been able to at least isolate the issue somewhat, which is as follows:
-
If I load an RJ variant for the first time in the sim (it seems to apply to all variants) I can follow the startup checklist through engine start with no issues - everything works as expected, and I can get 4 running engines.
-
If I then end the flight, and then load the same variant at the same airport and follow the exact same startup checklist, I can get to the point at which I unlatch the throttle to introduce fuel to the engine, but nothing happens after that - the engines behave as if they are not receiving fuel and subsequently do not start.
-
Any further instantiation of a variant that I have loaded previously leads to the same issue - I am unable to start any engines.
-
The only way I can restore engine start functionality is to uninstall and reinstall the RJ Professional package in MSFS 2024, and then I can only get running engines once per above. Needless to say this is an impractical solution, and for now the RJ Professional is essentially unusable in MSFS 2024 for me.
I am curious if anyone else has experienced this issue, and if there is any recommended remediation. I have tried uninstalling other addons such as GSX Pro to see if that resolves the issue, but it does not. Thanks for any guidance on this!
-
-
Although this is not something we are able to replicate on our side, it could potentially be a variation of the MSFS 2024 WASM instability issue listed in point 1 of the following FAQ: https://support.justflight.com/en/support/solutions/articles/17000143831-rj-professional-msfs-2024-known-issues
If that issue occurs again, try changing the RJ livery or variant between flights and see if that resolves the issue. We are hopeful that these WASM instability issues will be improved in the upcoming MSFS 2024 Sim Update 1.
It may also be worth double-checking that you have all four fuel pumps switched ON on the overhead panel and all four throttles in the FUEL ON position when starting the engines. Those should be the only controls that prevent fuel from entering the engines within the user's control.
Mark - Just Flight
-
Just following up on this - I tried changing the livery / variant on subsequent flight instantiations, but still ran into the engine start issue consistently. The behavior seems dependent on selecting a variant I have not invoked previously (since reinstallation of the aircraft in MSFS 2024) - if I select a variant for the first time, I can start the engines with no issues. Any subsequent instantiation of that variant will not allow an engine start.
I also tried clearing the WASM folder contents in the appdata for MSFS 2024, with the exception of the work folder, which I believe contains the license data for the RJ. This did not seem to resolve the engine start issue.
This definitely seems like a MSFS 2024 issue, as there is other odd behavior that seems dependent on whether or not an aircraft variant has been loaded for the first time (ex - avatar not being correctly spawned outside the aircraft when a flight is started on subsequent aircraft instantiations). I am currently using the SU1 beta that is currently available, but unfortunately still seeing the engine start issue. I will wait for SU2 to test again to see if the issue gets resolved. This is unfortunate, as the RJ is a brilliant plane to fly when I can start the engines :(
Out of curiosity, is there any plan to rework the RJ aircraft for MSFS 2024 to use B events as opposed to LVARs as used currently in the 2020 version? I have been flying the Inibuilds A300 specifically coded for MSFS 2024 (with full B event implementation) and have had virtually no issues with that. From the standpoint of someone configuring aircraft control mappings via tools like Spad.Next, B events are so much easier to work with.
