miro pacheco

Hi all, I got a crash flying the CL-650. Here's the log. The last entry with the stacktrace: 2022-04-24 15:55:41 CL650[gps4000s.c:2917]: WAAS data download successful 2022-04-24 15:56:41 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 500 (Internal Server Error) 2022-04-24 15:59:41 CL650[waas_api.c:205]: Failed to download WAAS API data: server responded with error 500 (Internal Server Error) 2022-04-24 15:59:57 CL650[except.c:213]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FFBD5640C7D C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F10C7D () 1 00007FFBD56419C3 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F119C3 () 2 00007FFBD564F8CF C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F1F8CF () 3 00007FFBD5640411 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F10411 () 4 00007FFBD563EB1C C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F0EB1C () 5 00007FFBD5640FB5 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F10FB5 () 6 00007FFBD56431A7 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F131A7 () 7 00007FFBD5642D8B C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F12D8B () 8 00007FFBD55D1EE5 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000EA1EE5 () 9 00007FFBD563FF67 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+0000000000F0FF67 () 10 00007FFBD5926011 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+00000000011F6011 () 11 00007FFBD591F843 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+00000000011EF843 () 12 00007FFBD595AB31 C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+000000000122AB31 () 13 00007FFBD589E4AD C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_bcadf751977be2f7\nvoglv64.dll+000000000116E4AD () 14 00007FF7C8AD2B8B E:\X-Plane 11\X-Plane.exe+0000000000E22B8B () 15 00007FF7C82C79BF E:\X-Plane 11\X-Plane.exe+00000000006179BF () 16 00007FF7C817C9A8 E:\X-Plane 11\X-Plane.exe+00000000004CC9A8 () 17 00007FF7C81B455B E:\X-Plane 11\X-Plane.exe+000000000050455B () 18 00007FFC465A7034 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017034 () 19 00007FFC47E02651 C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000052651 () --=={This application has crashed!}==-- (Art controls are modified.) Log.txt

Ok, so I will stick with my workaround. It might serve other P2ATC users. Just extend the "error" range for altitude and increase the time P2ATC nags about it.

This option should be flagged before starting the flight? Changing during flight didn't make much difference for me. What I did to workaround was to make a 4000ft difference in P2ATC, so it wouldn't complain about it.