Engine Health not updating.
-
I can check tomorrow morning, how do you efficiently damage the engine?
-
The easiest way is probably going into 850 mode on the ground and over-torqueing the engine. Thank you!
-
Over-torqueing for a minute, still 100%.
-
Same here, had some cases with over-torque and never seen health go below 100%. So far accumulated around 120hrs in the hobbs.
And great to hear about the upcoming update, looking forward for it :) -
@Black-Square For me it just never decreases. It used too, but since the beta, it just remains at 100%.
-
Thanks for all the reports on this. It's nice when everyone agrees that they are seeing the same thing, haha.
I checked this on every version of the TBM and in every way I can think of, and see no problem on my end. Are you sure you're waiting long enough to see the change? It took almost 60 seconds at 124% torque (2,337 FT-LBS on the ETM) to see the engine health decline below 100%.
Another way you could test this very definitively would be to induce an engine fire (while the engine is running), using the failure interface. Also, if you want to check that everything is generally working, you can check and set L:var_engineDamage (0-100, or the inverse of engine condition). If you set it over 80%, the engine's performance will degrade, and over 100% will cause a complete engine failure.
I always detest responding to bug reports with "it works for me", but this one is quite surprising, because it should be really difficult for something like this to go wrong between updates while everything else is working. I'm happy to troubleshoot and figure it out, but I'm afraid I will need some assistance if I can't reproduce it on my end.
-
Did another test: Over-torqueing for 5 minutes, still 100%.
-
Starter Main generator failure and Engine fire. Chip alarm went off and engine conditions slowly went down to zero.
-
I'm about 7 days late since my last response on this thread, sorry about that. Thanks for responding @Black-Square Dev. I have about 360 hours on my airframe and running the wear at x1 normal. I try to take good care of my aircraft and airframe and only have had minor exceedances since, usually only minor prop exceedances for a short second generally revving faster than the prop gov can allow on final and only very short minor TRQ exceedance ~under 5 secs before I notice and back off the TRQ during my 300+ hours on the engine.
I'm still at 100% engine health and only have had two failures during my 360 hours, which was a strobe light breaker and my airframe de-ice boots fail on me. I will try to over-torque my engine intentionally to see if this causes abnormal wear tomorrow and will report back. Maybe this is normal behavior ?
Also, to mention I run OnAir Airline Manager program with MSFS to generate my flights and have always wondered if repairing the airframe and engine in OnAir would have any effect on the TBM850, my assumption was always it would not interfere but maybe I'm wrong on that?
-
After testing, I purposely over-torqued my engine in air over 124%, and I noticed after about a minute engine health went from 100% to 99%. I cringed doing this to my engine with 300+ hours, lol. I exited the sim the proper way, (exited through the main menu) and reloaded another flight to see the engine health monitor reset back to 100%. So engine damage at first look doesn't appear to be persisting over for me. I'll do further testing and report back.
-
Thank you for doing some experiments with this. It actually delights me to hear that someone else cares about taking care of their virtual aircraft as much as I do. That was always the intent with my products, so I'm very thankful that you shared it.
Yes, it sounds like everything is working as expected in the code, but the condition is not saving. That's not too unexpected, unfortunately. I began using Asobo's new state saving when I started designing aircraft before I was aware that it works very inconsistently for some users. I've since gone back to using the legacy state saving system for important numbers like the engine condition. So far, my beta testers report that it's substantially more consistent, and even if it does erase your state from a bad simulator crash, you can restore the numbers in files on your computer. I will certainly make this change for the next version of the TBM for you.
Thanks for looking into this with me! Oh, and no OnAir will have no effect on the operation of my aircraft. Thanks again, and I will be thinking of your impressive 300 hours of engine operation when I program this improvement into the TBM for you.
-
@Black-Square hmm, but is it not a bit weird that I could over-torque the engine for 5 minutes without seeing any indication of less engine health?
-
Sorry, I forgot about that. If you saw your engine condition decline when you triggered a catastrophic failure, then the code is working. If you've been flying with real world weather, it's possible that the density altitude in your area is preventing the engine from over-torqueing in those conditions as severely is as it is for others. I'm happy to help, but I don't have much to go on here unless you help me with a little more investigation.
-
Yes, real world weather. It was a grey day.
-
@Black-Square Thank you for your kind words. I really enjoy the work you have done with the TBM and fly pretty much exclusively on Pilotedge (ATC Network) with the aircraft daily. I fly by the book and treat the aircraft as if it were a real airplane and what I would do in the real world. Furthermore, I have to say it comes really close to the numbers of the real TBM850 POH which I use for this aircraft and it's very impressive, despite the turboprop limitations within MSFS. Awesome job!
As far as testing goes, I have tested the engine conditions and failures further in flight and can confirm everything is working the way it should, just purely state saving being an issue upon reload with the engine, which explains why I haven't been seeing a decline in engine health upon reloads.
I will continue to fly and will just overlook the shortcomings with the state saving system in place, now that I understand what is going on. I will be eagerly keeping an eye out for your update. Thank you for your continued support on the TBM. Looking forward to the Duke!
