EGT

Hi, I was flying the RNAV RNP Z RW19 approach into Teterborough this evening (KTEB) when during approach the sim started freezing. Concurrent with this, the aircraft had extremely low fuel quantity (200 lbs) and the APU fuel pump fault light (in the left switch) started flickering (which was odd as it was NOT running) generating an associated CAS message. Simultaneously, the FMS seemed to be struggling with the idea of whether it had a VNAV PTH or not. It did, and was descending between 6000 ft (manual constraint on the STAR) and 3000 ft (altitude constraint on the approach). I suspect the APU at fault due to the fact once the fuel dropped sufficiently, the APU fault state became steady and the freezing stopped as well. I have saved the aircraft state at the moment it was doing this. Please see the attached. state.bin

Hi, When loading a saved aircraft state, the left EGT is zero. Also, the engine EGT is always zero, regardless of outside air temperature (before start). It does not reflect current conditions.

Was it precipitating? e.g. snow or freezing rain? I have seen it during such conditions.

Mine wants to LRC at M0.37...

I can see the XML in my browser but also get no chart avail in the aircraft.

Good to know! Correct - no SID (there isn't one) but due to terrain there is a required visual climb around the valley until > 1200 ft. I entered a PBD waypoint for the waypoint at which you're supposed to climb above 1200 ft before continuing on course, and entered /1200 for the altitude there. I was unaware of the climb/descent constraint logic or the fact it treats it as descent by default! Good to know. Thanks!!!

Hi, This is the 2nd/3rd consecutive flight without a restart. I diverted from the 1st flight due to fuel (ooops) and re-programmed the FMS with a new dest/route while airborne. All seemed to go well. It was direct to the field, with a visual runway centerline extension. The rest of the LEGS page was cleared out. Aircraft was landed, re-fuelled, and re-programmed with a new route (after reset by switching the databases). PFD still showed the altitude constraint from the last arrival. Unable to clear. Programmed the new route and added a custom PBD waypoint at LSK2L. I ended up with a waypoint sequencing problem (it wouldn't insert correctly) but managed to clear it and sent the FMS direct to the new waypoint (it was first on the route). PFD now showed this altitude constraint as 1200 in magenta. It initially wanted to DESCEND when this altitude constraint was first added, and it set all subsequent waypoints to 1200 ft also (instead of computing a climb profile). I changed it /1200A and all seemed well... I took off and started to climb. Aircraft performance was such that the visual circuit of the valley was not required so proceeded direct on course (departure of out of BGBW RW24). I went to engage VNAV but it said 112 kts, not the expected 250/280 kts of the climb profile. Please see the current state of the FMS. Aircraft is currently in cruise at FL410 at M0.82. https://imgur.com/a/Ejy63MN

Whether you know it or not, you have something running in the background that is either a forgotten AV or AM program, Windows Defender, or you have malware installed. There is absolutely no reason or way that X-Plane is deleting itself.

I'm blown away. Super fast and smooth performance, and she flies like a dream. Outstanding work!

That FS2020 is rubbish.

I moved the EICAS without using the reversionary panel, yet it still inhibited the charts on the left MFD?

I get a CTD using the 2D control panel to achieve the same thing. It crashed after the last checklist item was "completed" (green).

I agree - the library ultimately needs to be fixed so it doesn't choke on unexpectedly long names.

1*10^inf

I see... My original purchase was to fly on PC (no issues there), but I'm trying to get it going on the Mac. Not a big deal, but annoying. Thanks for the help, and Merry Christmas!

Seriously?? Please explain just what the operating system has to do with X-Plane and a crash in a module?

Hi, I can't run the TBM on Mac (Mojave). Every time I try and load it I get an instant crash the second it switches to loading the .acf file. I tried to remove X-TCAS from the plugins folder, but then it just hung instead. I've searched for solutions to this, but it seems very few if anyone has either encountered this, or that there is any way to update X-TCAS. From what I have discovered, it is likely related to FMOD conflict with X-Plane itself (I did see an fmod crash as well). It's a clean install of the TBM on a clean install of X-Plane.

All I can say to this thread is: LOL. I told you...

You mis-understood me. This aircraft should require lots of rudder trim for takeoff, yet the developers essentially eliminated P-factor to satisfy some users who have no clue about single-engine propellor aircraft, or even why they yaw so hard at takeoff (a major feature of aircraft such as the TBM). If you are going to "dumb down", at least be honest, and please provide those of us with understanding of aerodynamic principles the option to run "hardcore mode". If I wanted an unrealistic and easy-to-fly flight model, I'd fly another sim besides X-Plane...

I'm guessing this is never going to be addressed now? Years this has been complained about.

I most definitely have, and it works great!

My drivers were 3 years old...until last week. Drivers are rarely the real problem. More likely is there is an add-on/plug-in creating a problem with the TBM.

I'll check here shortly. First step: remove all plug-ins, except for the TBM stuff. Plug-ins are 99% of the problem.

Thank you. What approach speed are you using? I approach at 90 kts. The trim is still sensitive, though improved with the experimental flight model. Decelerating particularly through around 120 kts and config changes does require some careful trimming.

Hmm. Sure! Joined.