EGT

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.

I think it's the same size as the TBM 850. It's tiny (no, seriously). I can't even get down the cabin without getting wedged in. The pilot door is a must for people like me. When sat in the pilot's seat, you can reach out and touch the other side of the cockpit with an out-stretched hand. The top of the panel is about eye-height. I hit the yoke with my knees, and hardly clear the bottom of the panel when operating the rudder. Officially: Cabin Height: 4 ft Cabin Width: 3 ft 11" Yeah... and this is "spacious" compared to the Meridian (I can't fly it because I can't get in it). Pro tip: be short if you want to be a pilot. The sim feels spacious vs. reality. Once seated it's OK, but getting in (especially up-front) takes some dexterity if you're 6 ft 4" tall.

I saw the range ring once last night, and it went from expanded to zero for no good reason.

OK! I ask because when flying at dusk last night, the windows on the right looked misty, but the window on the left looked clear. It cleared up after dusk. I had the AC set cool, and had kept climbing to altitude for a bit then descending again, landing occassionally (island hopping, with 70 NM legs).

Hi, If you're able to modify the texture sheet of the G1000, are you able to read the whole area, darken it, and write it back, to implement dimming? Just a thought.

Hi, Do the windows mist at all?

According to the POH, the green arc for Ng is 51 to 104%. Red line is 104%.

You're not accidentally moving the gear lever before exiting the sim? I haven't even tried that to see what happens...

There are some bugs with the G1000. I'm not sure HotStart's or LR's. For example, if you enter "KJFK" it should only enter 4 characters, but the display shows "KJFKA" and tries to search waypoints, not airports. This is a bug. I've also found it necessary to clear the flight plan, enter the route, then tell it to use the FMS for pressurization schedule before it shows the correct destination and elevation. I think it should do this as soon as the destination is selected.

It's wrong for me the majority of the time. Where do you file bug reports with LR?

That sounds like the GPU is running out of memory. I get glitching of the propeller spinner in external view with icing present. It's fine the rest of the time. This is on PC/Windows 10 with a GTX1080 (not Ti). I was told to update my graphics drivers, but I doubt very much that is the problem. Are we allowed multiple installs of the TBM? If so, I'll install it on my iMac 5K and test, but IIRC your symptom of a total lock-up is what happens when XP exhausts the video memory. I must hard reset the computer in this case.

Why is it "off"? I thought it was supposed to be centered on aircraft position, and based on current vertical speed, ground speed, and altitude? Are Laminar fixing this?

I'm running 11.40b7 and hear it.

I've found the gens trip if the RPM surges. I'm not sure if there is an over-speed disconnect or not. I encountered some mild turbulence where the engine RPM surged, and then icing conditions. A bit later I noticed the gen had tripped, though there was no reason for it to have done (that I saw). While the engine audibly surged, the engine instruments didn't really support this (prop RPM did fluctuate slightly but remained in the green). I did get popping from the turbine (intake icing?). I powered back, switched on all the de-ice systems, and held on. I had deliberately flown into icing to see what happens. I've never had a situation like that in the sim where I was actually wondering if I'd make it out the other side. I also lost the gen once sometime around landing or shortly afterwards. Again, not sure why, and didn't see anything that indicated it should trip. I now keep an eye on the voltages and the gen bus during icing and other engine events to check it is still connected.

31000 ft and 50% torque will result in a fuel burn of about 35 gal./hr and 252 kts TAS. That gives an estimated range of 1800 NM with 1 hour reserve.

Hi, A couple of G1000 bugs: * If you're in a sub menu (soft keys, not pages), and you switch major mode (e.g. from the map to the weather RADAR), if a sub page is open when you switch, the sub page remains partially visible and does not update to the correct page state. To test: on the main map page press SYS and display the electrical page. Switch to the weather RADAR and back again. Observe partial SYSTEM page captions on the root menu. * When in the DIRECT TO page of the main MFD, typing MYBG results in LYBG. Typing NYBG results in MYBG. There is an indexing problem with the keyboard. Typing A when no airport exists types a 1. * Typing KJFK should result in the text KJFK. Instead, it results in the text KJFKA because the 5th character is populated instead of being blank. This means you can only enter the first 3 characters and then you must scroll the 4th or you end up with too many characters. It should be possible to type 4 characters and only get 4 characters. The cursor should move to a blank space and not auto-populate it.