EGT

The aircraft remembers its last state. I haven't even bothered to check if there is a fast way to set a cold and dark state because I treat it like a real aircraft (I fly IRL and to do otherwise is actually dangerous - try driving a racing them then immediately get into a real car - it isn't pretty). The TBM is one of the easiest aircraft to get started. So long as you follow procedures and set things in the correct sequence, she'll start. What this aircraft does have is lots of LIMITS and LIMITATIONS. These are the things that cause fires/burned engines/engine to be flooded. I suggest just getting it loaded for a start, and accepting whatever state it is in. Next, manually shutdown the engine (pull the power lever to CUTOFF and close the fuel valve). On the overhead, leave the batteries ON (crash bar UP), but switch everything else OFF. Once that is done, set the crash bar to OFF. If you have a fire, now is the time to go into the maintenance hangar and repair everything. After this, she should be far better behaved when loading up. Let us know if you can't stop the sim and reload without an issue.

I wish the motion under friction was about 1/10th what it is now. It's a great system they added but the throttle still moves too quickly.

I agree. I can't help but think they're one of the few that survived the axing of the studio, and they've got a chance to make another sim. Just watching the video I linked, it's clear Asobo are just the hired guns to write the software, and MS have total control.

I welcome the light-touch of the moderators, but personal insults/attacks cross the line. If you think my info is BS:

Hi, No. Just the TBM, JR SF260, and DF B407. Everything else is stock. The aileron roll issue was a consequence of setting rudder trim for takeoff. I have since read that you removed p-factor, and consequently setting rudder trim just meant I was slipping the aircraft during takeoff, hence the weird behavior. The pitch issue still persists however. It seems related to ground effect. Once out of ground effect and climbing away, elevator pressure required is forward, but constant until trimmed. The pitch trim is extremely sensitive, too. I am flying a light aircraft - 100 gal. fuel, one pilot, minimal baggage (30 lbs) in the aft hold. CoG is displaying as dead-center to the allowable range.

Nothing ironic. We're RL pilots who noticed it's missing. It's a major feature of these aircraft (and most propeller aircraft generally). If it can be an option, even better. Thank you for looking at this!

Check your graphics settings? I don't see any issues here when it appears.

I see this as well. It's as if it can't tell there is a fuel imbalance.

It's silly to have removed it. The real thing pulls, and people need to learn to fly properly. It's not a SIM unless it SIMULATES REALITY. Single-engine turboprops are known for pulling - they have the greatest torque and power of any single-engine propeller driven aircraft. People must learn to handle it.

Did you pay close attention to the videos? They all show the same few carefully edited pieces of footage. Hardly anyone free-flies, you don't get to see anything of the aircraft, and what I've seen, there are severe deficiencies in the flight modelling. FS2020 is STILL using the FS flight model from FS98. The SIMULATOR has not progressed. They've added a few things on top, but it is still the same heavily limited and defective flight model it always was. FS2020 looks impressive, but as a simulator, it's going to be nothing but a disappointment. X-Plane has nothing to worry about. (Before anyone gets excited, I'm NOT a tester. These opinions are just based off what I have seen of the simulator, and interviews I've watched of the developers).

Fly high! No good cruising at 10000 ft if you want the range.

It wasn't "too strong" - people need to learn how to use the rudder and rudder trim! I'd argue it wasn't enough (takeoff rudder trim still overpowered p-factor). If the aircraft is trimmed correctly, the rudder input required should be minimal, except for the initial roll before the rudder becomes effective. As a real-life pilot, this dumbing of simulators in this way really grinds. The real thing pulls, and requires the pilot to be...a pilot, and actually fly the thing.

Hi, I have the latest version of the TBM900 (fantastic aircraft) but I'm having a few "minor" issues with it... 1) Setting the correct rudder for takeoff (blue index) results in incorrect takeoff behavior 2) Yaw due to thrust (P-Factor) appears to be backwards (pulls right instead of left) 3) The aircraft initially rotates correctly, but as it gains speed through 100-120 kts there is a sharp pitch-up tendency requiring a lot of down elevator to counter after lift-off which is unnatural 4) The aircraft has some torque induced roll, but this seems very...chaotic and requires a lot of correction which seems to just disappear I'm running the latest version (1.1.12), and I'm *NOT* using the experimental flight model. Anyone any suggestions? EDIT: Seems I posted in the wrong forum. Can this be moved to support, please?

Learning opportunity missed.

Hi, I have some issues since the update to 1.1.10: * Aircraft pitches up wildly after lift-off requiring nose-down trim * Aircraft pitch response is too sensitive to airspeed, and results in the wild pitch up with only a 1 kt increase in speed * What happened to P-Factor?! * Aircraft now bounces like a kangaroo on touchdown * Maintenance manager green health bars are offset from the window and draw outside of it The P-Factor in 1.1.9 was already too low (I understand there was a problem with takeoffs prior to 1.1.9 but I only bought it recently), but now it seems non-existent. The blue line for rudder takeoff trim setting is completely irrelevant (it was in 1.1.9 as well), but now it seems rudder isn't required at all? I don't know what broke in 1.1.10 but it feels worse now than 1.1.9 did. Please fix the P-Factor and the pitch-up problems! These aircraft pull to the side like crazy. The sim doesn't. Aside from the lack of yaw she flew really nicely in 1.1.9.

Log file is useless because I've run XP since the crash, so the data is useless.

The map shows traffic if it's enabled in the display options.

OK! I'll raise a ticket with LR.

Please see the attached. TBM900_Log.txt

Hi, When flying in a multiplayer environment, the TBM cockpit lights and sometimes the displays flicker. This happens when both computers are running the TBM, or only one. Both aircraft see the same issue. There were only two of us, and when one of us entered the XP menu it stopped the flickering on the other side. It didn't matter what the other person was flying - the TBM would flicker while MP was connected. Other aircraft are unaffected. Is this a TBM issue or an XP issue?

That is everything relevant to the crash. There is a log entry for the previous day - irrelevant surely? It's not edited.

Didn't Apple drop 32-bit support in Catalina?

Found it. 2019-10-30 06:49:16 TBM900[xplane.c:1160]: This is the TBM900 (v1.1.9) libacfutils-62765a8 2019-10-30 06:49:16 TBM900[xplane.c:1205]: BOOT: glew_init 2019-10-30 06:49:16 TBM900[xplane.c:1219]: BOOT: glutils_sys_init 2019-10-30 06:49:16 TBM900[xplane.c:1221]: BOOT: lr_init 2019-10-30 06:49:16 TBM900[xplane.c:1223]: BOOT: gl_pic_sys_init 2019-10-30 06:49:16 TBM900[xplane.c:1226]: BOOT: acf_mgr_init 2019-10-30 06:49:16 TBM900[xplane.c:1234]: BOOT: updater_init 2019-10-30 06:49:16 TBM900[xplane.c:1237]: Systems plugin load complete 2019-10-30 06:49:16 TBM900[xplane.c:1299]: Systems plugin is enabling 2019-10-30 06:49:16 TBM900[xplane.c:1303]: BOOT: mtcr_glob_init 2019-10-30 06:49:16 TBM900[xplane.c:1310]: BOOT: fontmgr_init 2019-10-30 06:49:16 TBM900[xplane.c:1313]: BOOT: pulldown_init 2019-10-30 06:49:16 TBM900[xplane.c:1315]: BOOT: efis_widget_sys_init 2019-10-30 06:49:16 TBM900[xplane.c:1317]: BOOT: util_init 2019-10-30 06:49:16 TBM900[xplane.c:1321]: BOOT: sys_disp_glob_init 2019-10-30 06:49:16 TBM900[xplane.c:1323]: BOOT: scr_cap_init 2019-10-30 06:49:16 TBM900[xplane.c:1326]: BOOT: fail_init 2019-10-30 06:49:16 TBM900[xplane.c:1328]: BOOT: seats_init 2019-10-30 06:49:16 TBM900[xplane.c:1331]: BOOT: cas_init 2019-10-30 06:49:16 TBM900[xplane.c:1333]: BOOT: airframe_init 2019-10-30 06:49:16 TBM900[xplane.c:1335]: BOOT: doors_init 2019-10-30 06:49:16 TBM900[xplane.c:1337]: BOOT: gse_init 2019-10-30 06:49:16 TBM900[xplane.c:1339]: BOOT: sensors_init 2019-10-30 06:49:16 TBM900[xplane.c:1341]: BOOT: gear_init 2019-10-30 06:49:16 TBM900[xplane.c:1344]: BOOT: elec_init 2019-10-30 06:49:16 TBM900[xplane.c:1347]: BOOT: engine_init 2019-10-30 06:49:16 TBM900[xplane.c:1350]: BOOT: fms_init 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 1053 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2005 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2016 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2048 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2098 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2866 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3334 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4625 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5574 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5585 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5616 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5667 2019-10-30 06:49:16 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6435 2019-10-30 06:49:16 TBM900[xplane.c:1353]: BOOT: fuel_init 2019-10-30 06:49:16 TBM900[xplane.c:1355]: BOOT: ecs_init 2019-10-30 06:49:16 TBM900[xplane.c:1358]: BOOT: ap_init 2019-10-30 06:49:16 TBM900[xplane.c:1360]: BOOT: adc_init 2019-10-30 06:49:16 TBM900[xplane.c:1362]: BOOT: ckpt_anim_init 2019-10-30 06:49:16 TBM900[xplane.c:1364]: BOOT: reg_init 2019-10-30 06:49:16 TBM900[xplane.c:1366]: BOOT: effects_init 2019-10-30 06:49:17 TBM900[xplane.c:1369]: BOOT: ice_init 2019-10-30 06:49:17 TBM900[xplane.c:1373]: BOOT: snd_sys_init 2019-10-30 06:49:17 TBM900[xplane.c:1377]: BOOT: audio_init 2019-10-30 06:49:17 TBM900[xplane.c:1379]: BOOT: efis_utils_init 2019-10-30 06:49:17 TBM900[xplane.c:1383]: BOOT: efis_sys_init 2019-10-30 06:49:17 TBM900[xplane.c:1387]: BOOT: drawer_init 2019-10-30 06:49:17 TBM900[xplane.c:1391]: BOOT: xp_state_init 2019-10-30 06:49:17 TBM900[xplane.c:1393]: BOOT: maint_init 2019-10-30 06:49:17 TBM900[xplane.c:1396]: BOOT: maintlog_init 2019-10-30 06:49:17 TBM900[xplane.c:1398]: BOOT: taws_init 2019-10-30 06:49:17 TBM900[xplane.c:1401]: BOOT: wxr_init 2019-10-30 06:49:17 TBM900[xplane.c:1404]: BOOT: tas_init 2019-10-30 06:49:17 TBM900[xplane.c:1407]: BOOT: adf_dme_init 2019-10-30 06:49:17 TBM900[xplane.c:1410]: BOOT: efis_init 2019-10-30 06:49:17 TBM900[libsvs.c:4857]: libsvs(PFD): utilizing background rendering via share lists 2019-10-30 06:49:17 TBM900[xplane.c:1413]: BOOT: tablet_init 2019-10-30 06:49:17 TBM900[libsvs.c:4857]: libsvs(tablet): utilizing background rendering via share lists 2019-10-30 06:49:17 TBM900[xplane.c:1416]: BOOT: xpdr_init 2019-10-30 06:49:17 TBM900[xplane.c:1418]: BOOT: elt_init 2019-10-30 06:49:17 TBM900[xplane.c:1420]: BOOT: hypoxia_init 2019-10-30 06:49:17 TBM900[xplane.c:1423]: BOOT: notif_init 2019-10-30 06:49:17 TBM900[xplane.c:1426]: BOOT: fctl_init 2019-10-30 06:49:17 TBM900[xplane.c:1428]: BOOT: loadmgr_init 2019-10-30 06:49:17 TBM900[xplane.c:1431]: BOOT: charts_init 2019-10-30 06:49:17 TBM900[xplane.c:1434]: BOOT: chklist_init 2019-10-30 06:49:17 TBM900[xplane.c:1436]: BOOT: flightlog_init 2019-10-30 06:49:17 TBM900[xplane.c:1438]: BOOT: crash_init 2019-10-30 06:49:17 TBM900[xplane.c:1440]: BOOT: mfd_page_ind_init 2019-10-30 06:49:17 TBM900[xplane.c:1442]: BOOT: prp_anim_init 2019-10-30 06:49:17 TBM900[xplane.c:1444]: BOOT: axis_init 2019-10-30 06:49:17 TBM900[xplane.c:1446]: BOOT: hud_init 2019-10-30 06:49:17 TBM900[xplane.c:1450]: BOOT: fail_mgr_init 2019-10-30 06:49:17 TBM900[xplane.c:1453]: BOOT: g1000_popup_init 2019-10-30 06:49:18 TBM900[xplane.c:1456]: BOOT: rand_fail_init 2019-10-30 06:49:18 TBM900[xplane.c:1459]: BOOT: tutorial_init 2019-10-30 06:49:18 TBM900[xplane.c:1462]: BOOT: xplane_fdr_find 2019-10-30 06:49:18 TBM900[xplane.c:1289]: Boot complete 2019-10-30 06:49:18 TBM900[xplane.c:1520]: Systems plugin enable complete 2019-10-30 07:01:10 TBM900[elec.c:1202]: MAIN GEN tripped (20.3A, 28.4V, rpm: 0) 2019-10-30 07:02:39 TBM900[elec.c:1202]: MAIN GEN tripped (0.0A, 27.9V, rpm: 0) 2019-10-30 07:10:39 TBM900[elec.c:1202]: MAIN GEN tripped (11.7A, 28.4V, rpm: 0) 2019-10-30 07:25:15 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FF7824A4957 D:\X-Plane 11\X-Plane.exe+0000000000F54957 () 1 00007FF781F162EE D:\X-Plane 11\X-Plane.exe+00000000009C62EE () 2 00007FF781F18860 D:\X-Plane 11\X-Plane.exe+00000000009C8860 () 3 00007FF8A950158A D:\X-Plane 11\Resources\plugins\XPLM_64.dll+000000000001158A () 4 0000000021DC03B8 D:\X-Plane 11\X-Plane.exe+0000000021DC03B8 ()

Hi, Seems it is too late (I've run the sim several times since). It only crashed once so far. It's generally been solid. I'll reply here again if it happens. The above was the only thing of interest. Nothing else appeared unusual.

0:36:09.641 I/SIM: User confirmed they want to quit 0:36:09.648 D/STM: Transitioning from state state_Normal to state_ShuttingDown 2019-10-30 07:25:15 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FF7824A4957 D:\X-Plane 11\X-Plane.exe+0000000000F54957 () 1 00007FF781F162EE D:\X-Plane 11\X-Plane.exe+00000000009C62EE () 2 00007FF781F18860 D:\X-Plane 11\X-Plane.exe+00000000009C8860 () 3 00007FF8A950158A D:\X-Plane 11\Resources\plugins\XPLM_64.dll+000000000001158A () 4 0000000021DC03B8 D:\X-Plane 11\X-Plane.exe+0000000021DC03B8 () This is the first crash I've seen with the TBM. It occurred quitting the sim. The only add-on I have is X-RAAS.