fs 2024 Vanilla Turbine Failure With No Blacksquare Failure - SOLVED See First Post Edit
-
@Buzz Very interesting... I just did all of this exactly earlier, and found no problem, then let the simulator run for about two hours with no problem. Can you also tell me which variant you just tested with, just so there is no chance for error?
@Black-Square The FedEx Livery of the cargomaster. Failures at 1x in MTBF mode
-
B Buzz referenced this topic on
-
B Buzz referenced this topic on
-
And even under active or static pause while the sim is stopped, the W&T keeps decreasing.
Using the "Modern" flight model, with these settings .
@Buzz Thank you for the screenshot of your setting page! It's not the engine damage option, it's the airframe damage! Another completely sensical behavior from MSFS 2024!
I saw a post on the developer forums a while ago about spontaneous failures due to the simulator using the incorrect configuration speed for this mysterious "airframe damage", which I imagine is related. The damage begins as soon as the propeller is spinning, even before the engine is started.
Now we just need to find what undocumented configuration value is being used to determine that a propeller RPM of 0.0001 should damage the ""airframe"". More to come...
-
@Buzz Thank you for the screenshot of your setting page! It's not the engine damage option, it's the airframe damage! Another completely sensical behavior from MSFS 2024!
I saw a post on the developer forums a while ago about spontaneous failures due to the simulator using the incorrect configuration speed for this mysterious "airframe damage", which I imagine is related. The damage begins as soon as the propeller is spinning, even before the engine is started.
Now we just need to find what undocumented configuration value is being used to determine that a propeller RPM of 0.0001 should damage the ""airframe"". More to come...
@Black-Square Copy. I need to run to work, but will be back later today after my flight. Let me know if there is anything I can help test.
Cheers
-
@Buzz Thank you for the screenshot of your setting page! It's not the engine damage option, it's the airframe damage! Another completely sensical behavior from MSFS 2024!
I saw a post on the developer forums a while ago about spontaneous failures due to the simulator using the incorrect configuration speed for this mysterious "airframe damage", which I imagine is related. The damage begins as soon as the propeller is spinning, even before the engine is started.
Now we just need to find what undocumented configuration value is being used to determine that a propeller RPM of 0.0001 should damage the ""airframe"". More to come...
@Black-Square said in fs 2024 Vanilla Turbine Failure With No Blacksquare Failure:
Now we just need to find what undocumented configuration value is being used to determine that a propeller RPM of 0.0001 should damage the ""airframe"". More to come...
Thats odd since it's actually the "Engine Health" that's decreasing, not anything related to the airframe.
-
@Black-Square said in fs 2024 Vanilla Turbine Failure With No Blacksquare Failure:
Now we just need to find what undocumented configuration value is being used to determine that a propeller RPM of 0.0001 should damage the ""airframe"". More to come...
Thats odd since it's actually the "Engine Health" that's decreasing, not anything related to the airframe.
@Buzz said in fs 2024 Vanilla Turbine Failure With No Blacksquare Failure:
Thats odd
You're telling me.
-
No, I take it all back. If you open the other drop-downs in your Wear and Tear debugger, I think you will see that all the aircraft's components are being degraded at the same time and the same rate, as soon as the propeller is spinning. It indicates that a failure would not be expected for ~120 hours, though (yikes, what is this wear and tear system?) Did you ever see the TURBINE_ENGINE health declining at a rate faster than in the default aircraft? I think what I'm seeing right now is just how this default wear and tear systems is supposed to function.
EDIT: Yes, I see the same behavior with the default TBM. Also, the condition keeps declining after you exit the flight and you're in the main menu...
Sorry for the false alarm, everyone. I've become very sleep deprived while working on this tonight.
-
Here is a post on the Official Forums that seems to be at the intersection of what's being described here. Last post 19 hours ago. If anyone wants to engage, let me know what you can learn. I have already invested a substantial amount of time in this, but I would still rather is be a MSFS 2024 fluke than something I neglected.
-
@Black-Square So shutting off Airframe damage should solve the issue?
-
Ooh, reading that post linked above, are people who are seeing this on SU4 or the SU5 beta? I cannot contribute a data point because I have aircraft and airframe stress damage off by default, but also despite owning the Caravan since day 1 I have been unable to find flying time this week, so I'm waiting until 1.1 drops next week.
-
On the last 4 flights, I had 4 engine failures. On the last 2, the engine stress damage in MSFS2024 (SU4) was turned off. The tablet showed no failure at all. In 2 of the 4 cases, I could restart the engine in flight. All 4 flights were done with the passenger variant.
-
On the last 4 flights, I had 4 engine failures. On the last 2, the engine stress damage in MSFS2024 (SU4) was turned off. The tablet showed no failure at all. In 2 of the 4 cases, I could restart the engine in flight. All 4 flights were done with the passenger variant.
-
Hi. I'm experiencing the same thing. Random MSFS generated engine failures even though engine says 100%. Frustrating, impossible to do a full flight.
-
So, I did a couple of flights today. What I have seen is that if u treat the engine with love, wear and tear of msfs diminishes very slowly. At the same rate of other variables. But if u treat it increasingly worse that starts to increase the rate of descend, to the point it diminishes almost to 0 in a few minutes. However the Caravan tablet seems to work differently and damage is almost none. Probably thats what got us confused.
