Martin_1970

Thx for the update :) If now the stability (CTD) is also improved, i´m the happiest man on earth :)

Hello All, i have a question to the available flight range display in the MFD: The 2 circles show the normal range without the 45(?)minutes (dashed line) reserve and the range inclusive the 45minutes (solid circle). (???) This is normally calculated on the current fuel flow and the available fuel in the tanks. In the default G1000 i can adjust the fuel in the "system" tab of the MFD. Is there a similar option for the TBM? Problem with the actual calculation: Fuel available: roundabout 154 gal Fuel consumption: 58 gal/h -> Flight time: 2,5h (rounded) With actual speed of 272kts: Range should be 476nm / 680nm (with/without reserve) But the displayed range circles are quite closer. regards, Martin

I use "Toggle thrust reversers" to go in the beta/taxi range.

Hello all, i had many CTD (nearly every flight) and did some testing the last days. I reduced the amount of crashes (nearly to zero), by: Start X-Plane as administrator !! Please report in this thread only, if this workaround is working and brings improvements in stability. regards, Martin

Hi, i found a way, to reproduce another CTD: 0:01:23.082 D/ATC: Validating altitude for p=1 (N01XP): filed: 36000 usable_rte_dist: 438.638519 maxDescent: 109000 maxAlt: 109000 minAlt: 36000 chosen_alt: 36000 0:01:23.082 D/ATC: p=1 (N01XP): Cleared IFR 0:01:23.082 D/ATC: p=1 (N01XP): Squawk 4701 0:01:23.199 D/ATC: p=1 (N01XP): Taxi (23 points issued) G64: 83.507: Plugin Disabled. 0:01:25.808 D/ATC: p=2 (N02XP): Fly Heading: 214 0:01:25.808 D/ATC: p=2 (N02XP): Maintain 1998ft G64: 87.298: Boot Count: 3 G64: 89.920: Plugin Enabled. G64: 98.897: Boot Count: 4 G64: 101.511: Run: OnKickStart.. 2018-10-31 22:39:44 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FF978E4BCF0 C:\WINDOWS\System32\KERNELBASE.dll+ebcf0 () 1 00007FF97BE02717 C:\WINDOWS\SYSTEM32\ntdll.dll+a2717 () 2 00007FF97BDEAB36 C:\WINDOWS\SYSTEM32\ntdll.dll+8ab36 () 3 00007FF97BDFED2D C:\WINDOWS\SYSTEM32\ntdll.dll+9ed2d () 4 00007FF97BD66C86 C:\WINDOWS\SYSTEM32\ntdll.dll+6c86 () 5 00007FF97BDFDC5E C:\WINDOWS\SYSTEM32\ntdll.dll+9dc5e () 6 00007FF63FC15467 D:\X-Plane 11\X-Plane.exe+ef5467 () 7 00007FF63F6F4A6E D:\X-Plane 11\X-Plane.exe+9d4a6e () 8 00007FF63F6F6FE0 D:\X-Plane 11\X-Plane.exe+9d6fe0 () 9 00007FF96DCD158A D:\X-Plane 11\Resources\plugins\XPLM_64.dll+1158a () 10 00007FF9556BFED6 D:\X-Plane 11\Resources\plugins\Gizmo64.plugin\64\win.xpl+1fed6 () 11 00007FF9556C3B6E D:\X-Plane 11\Resources\plugins\Gizmo64.plugin\64\win.xpl+23b6e () 12 00007FF96DCD0C4D D:\X-Plane 11\Resources\plugins\XPLM_64.dll+10c4d () 13 00007FF96F9A3095 D:\X-Plane 11\Resources\plugins\PluginAdmin\64\win.xpl+3095 () 14 00007FF96FAE9CEA D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+9cea () 15 00007FF96FAE1873 D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+1873 () 16 00007FF96FAE7865 D:\X-Plane 11\Resources\plugins\XPWidgets_64.dll+7865 () 17 00007FF96DCC6675 D:\X-Plane 11\Resources\plugins\XPLM_64.dll+6675 () 18 00007FF63F77B110 D:\X-Plane 11\X-Plane.exe+a5b110 () 19 00007FF63F1B7D9A D:\X-Plane 11\X-Plane.exe+497d9a () 20 00007FF63FA0C903 D:\X-Plane 11\X-Plane.exe+cec903 () 21 00007FF97A706CC1 C:\WINDOWS\System32\USER32.dll+16cc1 () 22 00007FF97A70688B C:\WINDOWS\System32\USER32.dll+1688b () 23 00007FF9635D8BC1 C:\WINDOWS\SYSTEM32\OPENGL32.dll+38bc1 () 24 00007FF97A706CC1 C:\WINDOWS\System32\USER32.dll+16cc1 () 25 00007FF97A706693 C:\WINDOWS\System32\USER32.dll+16693 () 26 00007FF63FA0B23B D:\X-Plane 11\X-Plane.exe+ceb23b () 27 00007FF63EE5B41C D:\X-Plane 11\X-Plane.exe+13b41c () 28 00007FF63FBF38C7 D:\X-Plane 11\X-Plane.exe+ed38c7 () 29 00007FF97A643034 C:\WINDOWS\System32\KERNEL32.DLL+13034 () 30 00007FF97BDD1461 C:\WINDOWS\SYSTEM32\ntdll.dll+71461 () I can reproduce this easy with deactivating gizmo plugin and reactivating it (sometimes this must be done twice). Attached the complete log.file (x-plane clean installation) Log.txt Sometimes i get also a CTD wehen i choose "reboot scripts" from the gizmo plugin menue, or combination with the en-/disable of the plugin. And a small voice in my head say's, the other CTD (those without trace / debug information) are also related to gizmo... I wanted to try a flight without active gizmo plugin, but the license check seems not to be only on start, it seems to be permanent. What happens, if the license server is not available (e.g. instable internet connection) while i´m flying? regards, Martin

Hi, thanks for the reply. As this kind of crash even doesn´t create a report in /output/crah_reports and even windows itself doesn´t report something like "...has stopped working" i think i can only wait and hope for the best. I aggree with you it could also be a problem of X-plane itself, maybe you use a feature, no other aircraft used before? who knows. As some other user have similar CTD (but a little bit different) with some more information / backtrace, maybe this CTD is fixed if you could fix the other CDT. I hope so, because i can´t use the aircraft in this state. I hope for 1.0.9

Hi, sorry for repeating my post but: I tried it on a clean xplane installation, this means there are no other plugins. And i get the CTD there too. How can i produce / where to find the stack trace ? Update: Crashed again on the clean installation logfile added. You can see there are no other plungins installed than yours. Log.txt

Hello, i get the CTD with the same log entry, ...often (startet 20 Flights, but could only finish 4, 16 CDT) This is the only entry in the log concerning the CTD: 2018-10-29 17:25:08 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 No crash_report from X-plane or windows. The crash is more like "someone closes the application" For the question about conflicting plugins: I tested the aircraft on my secondary, clean, xplane installation, and there i get the crashes too Find attached the logfile from the "clean installation" crash. If i could help in finding this bug, please tell me. It is very frustrating to have this really cool aircraft and then it crashes so often Some question to the other guys with CDT issues: When you crash: - Do you have "NEXRAD" activated in the MAP settings of the G1000? - Do you use some kind of dynamic weather, e.g: built in "Match real world conditions" or something like xEnviro, FS_Global_Real_Weather or something else what changes the weather? - Do you have the G1000 weather radar activated? I have the feeling the bug could be located in the weather change, but i´m not sure (have to do more tests...) regards, Martin edit: during writing this post, another crash in my "unclean" installation happened, and i got a debug.log this time. Hope this helps Log.txt debug.log Log_plugins.txt