N602AC Posted November 1, 2018 Report Posted November 1, 2018 (edited) Happened to me just now while I was doing a short 80NM flight. 2018-10-31 23:00:53 TBM900[fail.c:931]: Component fuel nozzles has failed due to excessive wear (worn: 0.282943%, slope 1.0, rate: 0.000%/s). You can prevent this by observing performance limitations and servicing the aircraft regularly in the maintenance hangar. 2018-10-31 23:00:53 TBM900[fail.c:934]: Failure impact: tbm900/failures/fuel/noz_clog_part Lost the engine at 11,000ft, had to deadstick to the nearest field 8nm away. It would restart in flight and on the ground, but it wouldn't run properly, and would shut down upon adding power. (Acting as if it had clogged fuel nozzles, I'd imagine) Maintenance manager showed fuel nozzles were "as new". I damaged my turbine discs from my inflight restart attempt, on an airframe I have more than 50 hours in at this point. Considering I spent 65 dollars of my hard earned money on this, I'd like to see this get fixed. I'm definitely starting to get pissed off at this point. Failures are happening, on components showing less than 1 percent total wear, and then they don't show up in the maintenance manager, and remain failed until the sim is restarted. Seriously, this should be the biggest concern as far as fixing bugs as of right now. I had one opportunity to do a short flight tonight, and it got ruined. Here's some links to threads for other similar issues I've had. http://forums.x-pilot.com/forums/topic/14989-elec-feath-fault-and-loss-of-trq-reading/ http://forums.x-pilot.com/forums/topic/14889-feedback-something-that-happened-to-me-once/ http://forums.x-pilot.com/forums/topic/15021-solved-state-between-flights/?do=findComment&comment=133087 I look forward to hearing back. Edited November 4, 2018 by skiselkov Quote
falcon1823 Posted November 1, 2018 Report Posted November 1, 2018 I would head on over to their discord channel. https://discord.gg/7egEpuZ I find that is where support seems to be fastest and the devs see the support request more quickly. Quote
N602AC Posted November 3, 2018 Author Report Posted November 3, 2018 Was this issue addressed in 1.0.9? I read the changelog of course, but wasn't sure from reading it whether it was fixed or not. I'd love to know..Thanks. Quote
skiselkov Posted November 4, 2018 Report Posted November 4, 2018 Build 1.0.9b should fix these issues. Found the crucial piece in the failure simulation code which was triggering too eagerly. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.