Jump to content

N602AC

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by N602AC

  1. I just bought the MU2 the other day, as I had the original one for XPlane a looooong time ago. It has come pretty far! Love it.

    I'd also messed around trying to get the GTN750 to power on and off with the avionics switches and failed. Then I found this thread.

    So I guess you can add me to the list of people concerned about that aspect functioning correctly. I understand what you're saying about XPlane's limitations

    Beyond that, wonderful aircraft! Excellent work.

    Dan

  2. I've had numerous cases of this type of thing happening. Take a look for the other threads I've created about it. The worst one was when the fuel nozzles got considered as clogged with less than 1 percent of wear, causing a flameout in flight, and restart attempts were not successful. After that I had to make a deadstick landing at the nearest field. I guess it wasn't fixed in 1.0.9 after all then....?

  3. 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.

  4. This same thing happened to me just now while I was doing a short 80NM flight. Never overtorqued the engine.

    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.

  5. On 10/29/2018 at 12:46 PM, skiselkov said:

    I believe we have a fix in the pipeline for this. Should be in your inbox before the week is out.

    Can I get the same fix in my inbox too? I haven't flown the TBM in 2 days, just loaded up and the engine is still hot like I left it. Specifically the midframe temp, and the other components touching that are shown to be heating up as I look at the engine temps screen.

  6. I want to first say that I absolutely LOVE this product and think it's worth every penny.

    Anyway, I'm cruising at 30,000ft enroute from Daytona Beach to Pender Nebraska..I was working on a friend's car outside. When I came back in, I was basically over my destination. What is weird was, the TRQ readout on the MFD was a red X, and there was a CAS warning message "ELEC FEATH FAULT". The engine and propeller were behaving completely as normal. I checked the FEATHER circuit breaker, it was not tripped. I pulled it out and reset it, no difference. So I'm like okay whatever, just gotta not use a high power setting. I land at Pender, shut down the plane, check the maintenance manager, nothing. Everything "as new". I turned the battery back on, still red X for the TRQ readout.

    I had recently posted about loading up the TBM and getting nothing but red X's on the MFD, with nothing wrong in the maintenance manager. Here is a link to that thread. This was fixed by restarting XPlane.

    Also, as I promised with the previous similar issue, I'm attaching the Log.txt. I skimmed the Log and saw something referencing a bad metar XML. While probably unrelated, I have attached that as well for your convenience.

    Edit: I am running 11.26. I am considering updating to 11.30 beta. Should I? Should I wait?

    Edit 2: I found this in the log:

    2018-10-27 16:55:31 TBM900[fail.c:931]: Component reduction gearbox has failed due to excessive wear (worn: 0.733499%, 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-27 16:55:31 TBM900[fail.c:934]: Failure impact: sim/operation/failures/rel_TRQind0

    It should be noted that the reduction gearbox had certainly not failed. I was still at 200 knots indicated when I came back in the room. Also at 30,000 feet my torque never got above 91 percent to have even caused the gearbox to fail in the first place. And it certainly wasn't worn, it was and still is "as new".

    Edit 3: Just FYI, restarting Xplane, the issue was gone, as with my previous similar issue.

    Here are 2 pictures of today's issue.

    89a78c868ca3b25b38e049afebbe3419.jpg

    f4a7102f5d1bbbcfba4238d259e27709.jpg

    Log.txt

    metar.xml

  7. I have no way of knowing why it happened, but I actually got a BSOD while in cruise on a 700nm/3hr flight, about 75% of the way through it. Part of why I can't tell you anything is I wasn't in the room when it happened but my fiance noticed the screeching sound the computer speakers started making, before the PC shut down automatically.

    Running Win7 if that means anything. My immediate thought is one of my RAM sticks might be going bad, so this probably isn't the aircraft. But I don't know.

  8. Not sure what it was, but I just loaded up and when I turned the power on, no matter what I did (checking the breakers and the maintenance manager were the things I thought to definitely do) I couldn't get it to stop, I actually even started the engine and it ran fine but it was just X's on the display. I closed X-Plane and loaded up a 2nd time, the problem was gone. :blink:

     

    e5c9efe24a38b6d94bccbebd932cf2c3.png

     

    Any thoughts? Was there something I could have checked or done?

    Thanks,

    Dan

×
×
  • Create New...