Jump to content

TBM 900 v1.1.7 Update Released!


Cameron
 Share

Recommended Posts

I immediately wanted to set rain effect to OFF (because of the latest posts here) but all texts disappeared, the boxes stayed on my screen, doubled, and nothing was clickable. So I have three cascading Garmin screens and two overlapping sidebars and a Gizmo menu with vertical stripes. The only way out was force-quitting X-plane. I guess because it was actually raining and my iMac was on 0.5 frames per second.

So, together with six (!) other payware aircraft, all updated this month, and all updates contained some implementation  of a new rain effect...it is a no-no for mac os x. Some of them, luckily this one too, has the option to turn it off. Thanks for the update though!

I did a test flight Burbank KBUR -sta Catalina KAVX:

- still struggles with frame rates; problematic; above South LA, sky broken: 15-17fps (above sea and island 22-26fps)
(- during roll out after landing, applying reverse, suddenly my setup reversed...throttle back went up, throttle up went back / can also be an incident)

settings: visual effects: High / texture quality: Medium / Anti-alias: FXAA / draw shadows: unchecked / number of world objects: High / reflection details: Minimal / screen: 2048x1152 (cpu 0.056 time, gpu 0.065 time)

system: mac osx 10.14.3 (Mojave) iMac Retina 5K, 27", end2015, 4GHz i7, 32GB, AMD Radeon M395X 4096MB

All the best

Log.txt

Edited by Mindyourstep
Link to comment
Share on other sites

The only way to flight on Mac is setting the rain effect off and don't turn the AoA on...otherwise the frame rate drops to 1 and/or everything becomes irresponsive....

I did KMDW to KOPF and no drops on frame rate or crash...looks like the only problem on Mac version is those effects and AoA.

 

Link to comment
Share on other sites

My VR-mouse is unseable after this update. It appears to be floating only 2 inches from my eyeballs, and no selections are possible. This is the only aircraft where I’ve seen this, and it only happened after the update to 1.1.7

As i have recently upgraded to the Pimax from a Rift, and hence have no VR hand-controllers, I’m kinda stuck for the time being.

 

cheers

Link to comment
Share on other sites

1.6 was rock solid stable and no crash but 1.7 constant CDT after loading. Log file attached

 

1:15:50.714 D/ATC: p=6 (N652YT): Fly Heading: 96
1:15:50.714 D/ATC: p=6 (N652YT): Maintain 6998ft
1:15:50.714 I/ATC: Aircraft p=6 (N652YT) started airborne as an overflight at 41.539482, -88.291061, 2133.600098
1:15:50.738 I/ATC: p=8 (N386NV) Popup FP filed to KGYY at 7000 via 4138N08731W , type=2
1:15:50.738 D/ATC: Validating altitude for p=8 (N386NV): filed: 7000 usable_rte_dist: 32.963177 maxDescent: 8000 maxAlt: 9000 minAlt: 7000 chosen_alt: 7000
1:15:50.738 D/ATC: p=8 (N386NV): Cleared IFR
1:15:50.738 I/FLT: Init dat_p8 type:loc_specify_lle lat:41.873295 lon:-88.379181 ele(ft):7000.000374 psi:109.494110 spd(kts):749.249998
1:15:50.738 D/ATC: p=8 (N386NV): Fly Heading: 101
1:15:50.738 D/ATC: p=8 (N386NV): Maintain 6998ft
1:15:50.738 I/ATC: Aircraft p=8 (N386NV) started airborne as an overflight at 41.873295, -88.379181, 2133.600098
2019-03-20 21:28:10 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FF72CA4D5A7 C:\X-Plane 11\X-Plane.exe+000000000054D5A7 ()
1 00007FF72CA2DC92 C:\X-Plane 11\X-Plane.exe+000000000052DC92 ()
2 00007FF72CA3477F C:\X-Plane 11\X-Plane.exe+000000000053477F ()
3 00007FF72C9FA9F4 C:\X-Plane 11\X-Plane.exe+00000000004FA9F4 ()
4 00007FF72C9FECC4 C:\X-Plane 11\X-Plane.exe+00000000004FECC4 ()
5 00007FF72CA4A6CA C:\X-Plane 11\X-Plane.exe+000000000054A6CA ()
6 00007FF72CA4AACC C:\X-Plane 11\X-Plane.exe+000000000054AACC ()
7 00007FF72C9FF506 C:\X-Plane 11\X-Plane.exe+00000000004FF506 ()
8 00007FF72C5D8AAC C:\X-Plane 11\X-Plane.exe+00000000000D8AAC ()
9 00007FF72C964B6A C:\X-Plane 11\X-Plane.exe+0000000000464B6A ()
10 00007FF72D1D1587 C:\X-Plane 11\X-Plane.exe+0000000000CD1587 ()
11 00007FF72C5DC18C C:\X-Plane 11\X-Plane.exe+00000000000DC18C ()
12 00007FF72D3F0387 C:\X-Plane 11\X-Plane.exe+0000000000EF0387 ()
13 00007FFE4BB481F4 C:\WINDOWS\System32\KERNEL32.DLL+00000000000181F4 ()
14 00007FFE4DE6A251 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006A251 ()
 

See 

Log.txt

Link to comment
Share on other sites

39 minutes ago, Sims Smith said:

1.6 was rock solid stable and no crash but 1.7 constant CDT after loading. Log file attached

 

1:15:50.714 D/ATC: p=6 (N652YT): Fly Heading: 96
1:15:50.714 D/ATC: p=6 (N652YT): Maintain 6998ft
1:15:50.714 I/ATC: Aircraft p=6 (N652YT) started airborne as an overflight at 41.539482, -88.291061, 2133.600098
1:15:50.738 I/ATC: p=8 (N386NV) Popup FP filed to KGYY at 7000 via 4138N08731W , type=2
1:15:50.738 D/ATC: Validating altitude for p=8 (N386NV): filed: 7000 usable_rte_dist: 32.963177 maxDescent: 8000 maxAlt: 9000 minAlt: 7000 chosen_alt: 7000
1:15:50.738 D/ATC: p=8 (N386NV): Cleared IFR
1:15:50.738 I/FLT: Init dat_p8 type:loc_specify_lle lat:41.873295 lon:-88.379181 ele(ft):7000.000374 psi:109.494110 spd(kts):749.249998
1:15:50.738 D/ATC: p=8 (N386NV): Fly Heading: 101
1:15:50.738 D/ATC: p=8 (N386NV): Maintain 6998ft
1:15:50.738 I/ATC: Aircraft p=8 (N386NV) started airborne as an overflight at 41.873295, -88.379181, 2133.600098
2019-03-20 21:28:10 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FF72CA4D5A7 C:\X-Plane 11\X-Plane.exe+000000000054D5A7 ()
1 00007FF72CA2DC92 C:\X-Plane 11\X-Plane.exe+000000000052DC92 ()
2 00007FF72CA3477F C:\X-Plane 11\X-Plane.exe+000000000053477F ()
3 00007FF72C9FA9F4 C:\X-Plane 11\X-Plane.exe+00000000004FA9F4 ()
4 00007FF72C9FECC4 C:\X-Plane 11\X-Plane.exe+00000000004FECC4 ()
5 00007FF72CA4A6CA C:\X-Plane 11\X-Plane.exe+000000000054A6CA ()
6 00007FF72CA4AACC C:\X-Plane 11\X-Plane.exe+000000000054AACC ()
7 00007FF72C9FF506 C:\X-Plane 11\X-Plane.exe+00000000004FF506 ()
8 00007FF72C5D8AAC C:\X-Plane 11\X-Plane.exe+00000000000D8AAC ()
9 00007FF72C964B6A C:\X-Plane 11\X-Plane.exe+0000000000464B6A ()
10 00007FF72D1D1587 C:\X-Plane 11\X-Plane.exe+0000000000CD1587 ()
11 00007FF72C5DC18C C:\X-Plane 11\X-Plane.exe+00000000000DC18C ()
12 00007FF72D3F0387 C:\X-Plane 11\X-Plane.exe+0000000000EF0387 ()
13 00007FFE4BB481F4 C:\WINDOWS\System32\KERNEL32.DLL+00000000000181F4 ()
14 00007FFE4DE6A251 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006A251 ()
 

See 

Log.txt

First step I would ask you to do is to update your GPU drivers.  

If it crashes again, please post back.

Link to comment
Share on other sites

13 hours ago, Shafs64 said:

Hi mate yes i did have  it on. will have a look after work today to trouble shoot the issue.

Found out  i didn't the setting turned up in X plane. And now its frigging great i will be flying in rain and ice all the time now.

What a great team thanks guys

Edited by Shafs64
dumb thumbs
Link to comment
Share on other sites

8 hours ago, Goran_M said:

First step I would ask you to do is to update your GPU drivers.  

If it crashes again, please post back.

I updated the GPU driver and it still Crash to Desktop. I see a lot of TBM Error. Full log attached also.

2019-03-21 06:47:08 TBM900[xplane.c:1329]: BOOT: fms_init
2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 1051

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2000

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2011

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2043

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2069

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2094

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2259

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2834

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3314

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4606

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5552

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5563

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5594

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5621

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5646

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5809

2019-03-21 06:47:08 TBM900[navaiddb.c:512]: Error parsing C:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6386

2019-03-21 06:47:08 TBM900[xplane.c:1332]: BOOT: fuel_init
2019-03-21 06:47:08 TBM900[xplane.c:1334]: BOOT: ecs_init
2019-03-21 06:47:08 TBM900[xplane.c:1337]: BOOT: ap_init
2019-03-21 06:47:08 TBM900[xplane.c:1339]: BOOT: adc_init
2019-03-21 06:47:08 TBM900[xplane.c:1341]: BOOT: ckpt_anim_init
2019-03-21 06:47:08 TBM900[xplane.c:1343]: BOOT: reg_init
2019-03-21 06:47:08 TBM900[xplane.c:1345]: BOOT: effects_init
2019-03-21 06:47:09 TBM900[xplane.c:1348]: BOOT: ice_init
2019-03-21 06:47:09 TBM900[xplane.c:1352]: BOOT: snd_sys_init
2019-03-21 06:47:09 TBM900[xplane.c:1356]: BOOT: audio_init
2019-03-21 06:47:09 TBM900[xplane.c:1358]: BOOT: efis_utils_init
2019-03-21 06:47:09 TBM900[xplane.c:1362]: BOOT: efis_sys_init
2019-03-21 06:47:09 TBM900[xplane.c:1366]: BOOT: drawer_init
2019-03-21 06:47:09 TBM900[xplane.c:1370]: BOOT: xp_state_init
2019-03-21 06:47:09 TBM900[xplane.c:1372]: BOOT: maint_init
2019-03-21 06:47:09 TBM900[xplane.c:1375]: BOOT: maintlog_init
2019-03-21 06:47:09 TBM900[xplane.c:1377]: BOOT: taws_init
2019-03-21 06:47:09 TBM900[xplane.c:1380]: BOOT: wxr_init
2019-03-21 06:47:09 TBM900[xplane.c:1383]: BOOT: tas_init
2019-03-21 06:47:09 TBM900[xplane.c:1386]: BOOT: adf_dme_init
2019-03-21 06:47:09 TBM900[xplane.c:1389]: BOOT: efis_init
2019-03-21 06:47:09 TBM900[libsvs.c:4765]: libsvs(PFD): utilizing background rendering
2019-03-21 06:47:10 TBM900[xplane.c:1392]: BOOT: tablet_init
2019-03-21 06:47:10 TBM900[libsvs.c:4765]: libsvs(tablet): utilizing background rendering
2019-03-21 06:47:10 TBM900[xplane.c:1395]: BOOT: xpdr_init
2019-03-21 06:47:10 TBM900[xplane.c:1397]: BOOT: elt_init
2019-03-21 06:47:10 TBM900[xplane.c:1399]: BOOT: hypoxia_init
2019-03-21 06:47:10 TBM900[xplane.c:1402]: BOOT: notif_init
2019-03-21 06:47:10 TBM900[xplane.c:1405]: BOOT: fctl_init
2019-03-21 06:47:10 TBM900[xplane.c:1407]: BOOT: loadmgr_init
2019-03-21 06:47:10 TBM900[xplane.c:1410]: BOOT: charts_init
2019-03-21 06:47:10 TBM900[helpers.c:1027]: Cannot stat C:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1811: Access is denied.

2019-03-21 06:47:10 TBM900[helpers.c:1027]: Cannot stat C:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1812: Access is denied.

2019-03-21 06:47:10 TBM900[helpers.c:1027]: Cannot stat C:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1813: Access is denied.

2019-03-21 06:47:10 TBM900[helpers.c:1027]: Cannot stat C:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1901: Access is denied.

2019-03-21 06:47:10 TBM900[helpers.c:1027]: Cannot stat C:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1902: Access is denied.

2019-03-21 06:47:10 TBM900[xplane.c:1413]: BOOT: chklist_init
2019-03-21 06:47:10 TBM900[xplane.c:1415]: BOOT: flightlog_init
2019-03-21 06:47:10 TBM900[xplane.c:1417]: BOOT: crash_init
2019-03-21 06:47:10 TBM900[xplane.c:1419]: BOOT: mfd_page_ind_init
2019-03-21 06:47:10 TBM900[xplane.c:1421]: BOOT: prp_anim_init
2019-03-21 06:47:10 TBM900[xplane.c:1423]: BOOT: axis_init
2019-03-21 06:47:10 TBM900[xplane.c:1425]: BOOT: hud_init
2019-03-21 06:47:10 TBM900[xplane.c:1429]: BOOT: fail_mgr_init
2019-03-21 06:47:10 TBM900[xplane.c:1432]: BOOT: g1000_popup_init
2019-03-21 06:47:10 TBM900[xplane.c:1435]: BOOT: rand_fail_init
2019-03-21 06:47:10 TBM900[xplane.c:1438]: BOOT: tutorial_init
2019-03-21 06:47:10 TBM900[xplane.c:1441]: BOOT: xplane_fdr_find
2019-03-21 06:47:10 TBM900[xplane.c:1498]: Systems plugin enable complete
2019-03-21 06:47:48 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FFFE8D3C6A6 C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000001C6A6 ()
1 00007FFFE8D2FF5C C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000000FF5C ()
2 00007FFFE8D3E030 C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000001E030 ()
3 00007FFFE8D3A56B C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000001A56B ()
4 00007FFFE8D2CC37 C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000000CC37 ()
5 00007FFFE8D2BF43 C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000000BF43 ()
6 00007FFFE8D2BFFC C:\WINDOWS\SYSTEM32\DINPUT.DLL+000000000000BFFC ()
7 00007FFFF4030B05 C:\WINDOWS\SYSTEM32\winmmbase.dll+0000000000010B05 ()
8 00007FFFF403022B C:\WINDOWS\SYSTEM32\winmmbase.dll+000000000001022B ()
9 00007FFFF40316BF C:\WINDOWS\SYSTEM32\winmmbase.dll+00000000000116BF ()
10 000001C93976126A C:\X-Plane 11\Resources\plugins\XPUIPC\64\win.xpl+000000000002126A ()
11 00007FFFF8C981F4 C:\WINDOWS\System32\KERNEL32.DLL+00000000000181F4 ()
12 00007FFFFA78A251 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006A251 ()
 

Log.txt

Link to comment
Share on other sites

I had stable luck with few previous builds, but now I got this:

2019-03-21 17:55:53 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 000001C767950C6C C:\X-Plane 11\X-Plane.exe+000001C767950C6C ()
1 000001CBEB69AB7C C:\X-Plane 11\X-Plane.exe+000001CBEB69AB7C ()

Log.txt

Link to comment
Share on other sites

Greetings fellow aviators.

After browsing this forum for a little over a week now, I've decided to create an account because I have had my eyes on this plane for awhile.  Longtime flight simmer (early 1980's) and a longtime user of X-Plane, as well as a real world private pilot with G1000 experience . 

I have a home cockpit and dedicated PC that I've built. (i7-7700k OC'd to 5GHz. 500gb SSD, 32GB DDR4, GTX-1080Ti).  Warthog HOTAS, Saitek rudder pedals, GoFlight TQ6, MCP, etc. Oculus Rift CV1.

Recently I bought a YOKO Yoke which is an incredible piece of gear!  Sooo much better than the CH and Saitek yokes I've owned over the years!

Your TBM900 looks like an amazing accomplishment and I am seriously considering purchasing it, however, I am a little concerned to read the numerous post here about bugs, particularly the large number of folks experiencing CTDs.  As a longtime PC and flight simulator hobbyist, I am used to tinkering and tweaking hardware/software and beta testing. However, due to my very busy work schedule and family life, I have very little time to actually sit down and enjoy my hobby (which includes DCS World and AFS2).  So the last thing I want is a CTD in the middle of a short flight in X-Plane!

Currently in X-Plane, I fly the Carenado B58 almost exclusively in VR (with no CTDs).  If I purchase your TBM, how can I minimize the chances of experiencing X-Plane crashes?  Are the majority of current users flying it without issue?

Thanks for your input.

 

Edited by Redtail_Pilot
Link to comment
Share on other sites

I would say as a fellow real world pilot. you are wasting your time thinking about it just buy it. it can be a pain to take off and land which is a good thing. it keeps you on your toes like in real aircraft not all your landings will be great. Also it will give you unexpected failures. I have had LG fail to come down and auto pilot fail in IMC. sure its has its issue's but the hot start team are very dedicated to this aircraft  and have been quick to fix bugs. I have been flying sim since fs98 and i would say this is one of the best GA sim aircraft out there for X Plane. And In VR i would say it is the best with the rain and ice effect. 

Link to comment
Share on other sites

1 hour ago, Redtail_Pilot said:

Greetings fellow aviators.

After browsing this forum for a little over a week now, I've decided to create an account because I have had my eyes on this plane for awhile.  Longtime flight simmer (early 1980's) and a longtime user of X-Plane, as well as a real world private pilot with G1000 experience . 

I have a home cockpit and dedicated PC that I've built. (i7-7700k OC'd to 5GHz. 500gb SSD, 32GB DDR4, GTX-1080Ti).  Warthog HOTAS, Saitek rudder pedals, GoFlight TQ6, MCP, etc. Oculus Rift CV1.

Recently I bought a YOKO Yoke which is an incredible piece of gear!  Sooo much better than the CH and Saitek yokes I've owned over the years!

Your TBM900 looks like an amazing accomplishment and I am seriously considering purchasing it, however, I am a little concerned to read the numerous post here about bugs, particularly the large number of folks experiencing CTDs.  As a longtime PC and flight simulator hobbyist, I am used to tinkering and tweaking hardware/software and beta testing. However, due to my very busy work schedule and family life, I have very little time to actually sit down and enjoy my hobby (which includes DCS World and AFS2).  So the last thing I want is a CTD in the middle of a short flight in X-Plane!

Currently in X-Plane, I fly the Carenado B58 almost exclusively in VR (with no CTDs).  If I purchase your TBM, how can I minimize the chances of experiencing X-Plane crashes?  Are the majority of current users flying it without issue?

Thanks for your input.

 

In many cases, the problem is due to some conflicting plugin or hardware issue.  Sometimes, the fault is with us, and we address those as quickly as possible.  Most of the latest issues are due to outdated graphics drivers. 
By all means, wait until you are comfortable in getting it.  It can only get better and more trouble free from here.  
There are quite a few streamers on twitch who regularly stream the TBM.  I think I've only seen 2 or 3 crashes in all the TBM streams I've seen.  

Link to comment
Share on other sites

Hi!

I did two legs back and forth without any issue and the last one I got a CTD:

2019-03-22 18:15:32 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

Lastest Nvidia Drivers 419.35.

For information my plugin Better push back never hurt any guy on my side so I have no idea what could cause this bug that I already had in the past with the last version by the way.

Tks

Link to comment
Share on other sites

5 hours ago, LKN said:

Hi!

I did two legs back and forth without any issue and the last one I got a CTD:

2019-03-22 18:15:32 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

Lastest Nvidia Drivers 419.35.

For information my plugin Better push back never hurt any guy on my side so I have no idea what could cause this bug that I already had in the past with the last version by the way.

Tks

Did you try the "remove all plugins except Gizmo" routine?

Link to comment
Share on other sites

21 hours ago, Shafs64 said:

I would say as a fellow real world pilot. you are wasting your time thinking about it just buy it. it can be a pain to take off and land which is a good thing. it keeps you on your toes like in real aircraft not all your landings will be great. Also it will give you unexpected failures. I have had LG fail to come down and auto pilot fail in IMC. sure its has its issue's but the hot start team are very dedicated to this aircraft  and have been quick to fix bugs. I have been flying sim since fs98 and i would say this is one of the best GA sim aircraft out there for X Plane. And In VR i would say it is the best with the rain and ice effect. 

Well, just within the 20 or so hours since my post, there have been several new "crash (CTD)" post on this forum. So I don't really think I'm wasting my time thinking about it, as you say.  What would be a waste of my time, is dealing with the same!

I think I'll sit it out a bit longer and let this bird cook in the oven a little more before having dinner:D.

Thanks guys.

 

Edited by Redtail_Pilot
Link to comment
Share on other sites

20 hours ago, Goran_M said:

In many cases, the problem is due to some conflicting plugin or hardware issue.  Sometimes, the fault is with us, and we address those as quickly as possible.  Most of the latest issues are due to outdated graphics drivers. 
By all means, wait until you are comfortable in getting it.  It can only get better and more trouble free from here.  
There are quite a few streamers on twitch who regularly stream the TBM.  I think I've only seen 2 or 3 crashes in all the TBM streams I've seen.  

Thanks for your reply. 

Link to comment
Share on other sites

On 3/23/2019 at 12:26 AM, Goran_M said:

Did you try the "remove all plugins except Gizmo" routine?

Hi Goran,

I only have Better Push Back and the necessary one to me: Xp Realistic  that never caused any issue with other birds or else so far. And flying without is a no go.

But let's speculate for a minute that Xp Realistic is the main cause of CTD of my TBM which I guess you and I don't really believe because it will be known for each other if that plugin was the guilty guy?

So let's imagine that is the one who creates the conflict of incompatibility therefore it will simply mean that I can't use both in the same time which will be very inconvenient to me. I'd of course like to stick with them!

I really understand that the TBM has his own engine system which makes that bird exceptional and certainly the most complex and complete in our Xplane's world but maybe also more vulnerable about issues, matching it with Xplane plateform is not an easy way I guess... Well I'm not sure that Better for Push back or/and Xp realistic are here the cause of CTD. I already had CTD with the TBM without this plugin by the way... Well it could come from plugins indeed but on my side I don't have a plenty of plugs and the ones I have don't look like they are confrontational so  it could come from my TBM as well ...? I have no idea my plugs seem to be gentle with m Xplane config, my Nvidia drivers are updated (they are always updated, got notifications and it works perfectly in any circumstance)

Also I have the lastest FlyWithLua that I really do need that again didn't create any conflict so far.

I pay attention for my own comfort not to add a bunch of plugins or scenes in order to fly hours without getting back to my desk in general... That is maybe the reason why I have a PC only dedicated for sim. (no stutter, no lost of frame with XP beta or ctd, I don't think it's luck it's just making a decision to fly with only Orbx and Ortho scenery, using Xorganiser to manage things to avoid conflict and so far no CTD anyways since I decided not to have a collection of plugs/scenes/freeware etc just some library freeware objects etc to put some life here and that works good)

Oh I forgot that I just added the plugin Live Traffic but I had CTD with my tbm before I installed it so I believe that this guys is not on the black list as well.

I use XPUIPC that I also do need for my virtual airline, so far it never creates any CTD except one because of my bad. By all means I'm inclined to believe that the issue don't come from my Nvida drivers, plugins or FlywithLua... It could be... but it looks like it doesn't feel efficient if I dig more into those ways: drivers and plugs,  I'm not inspired to think that my plugs are the cause.

Cheers and thanks again for your support, always fully appreciated!

Lkn

PS my config:

Processor Intel (R) Core i7-6700 CPU @ 4.00GHz RAM 16,0 Go ,Window 8.1 Pro 64 bits, Nvidia 1080GTX, Screen LCD Philips 4K 127cm (50 inches),resolution 3840/2160 60htz, 8 Goflight modules,CH Product Yoke, throttles and rudders.

Plugins: FlywithLua, Better For Push Back, Live Traffic, XP Realistic

Engine weather: Active Skyxp, Xenviro, FSGRW

Edited by LKN
  • Like 1
Link to comment
Share on other sites

  • Cameron locked and unpinned this topic
Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...