Ok-ran it. Same freeze but saw nothing generated in rxpGTN.xpl.log and rxpGtnSim.dll.log

Did I edit the RealityXP.GTN.ini file right in the Carenado 690B TurboCommander aircraft folder? Red font below is where I put the edit.

_____________________________________________________

[GTN]
; comma separated list of gauges
gauges = GTN_750_1

[GTN_750_1]
; comma separated list of render targets.
drawto = WINDOW, PANEL3D
; is the master device if true.
MasterDevice = true
Rheostat.Display = 0
Rheostat.Buttons = 2
LinkCrs = true
LinkObs = true
LinkVor = true
PowerSource = AVIONICS_BUS
UseRyanTcad = false
FuelType = AVGAS
VoicePref = MALE
LogTrainer = 5
DebugValue = 1
; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2
NavDbType = 1
; connects to: 'PFC_GTN' or any '#PID' (#D067 for PFC_GTN)
; no value connects to first found, 'OFF' disables connection.
HardwareDevice =
; hardware selector number or -1 to disable.
HardwareIdx = -1

[GTN_750_1.WINDOW]
; display window if true.
visible = false
; show screen only gauge if true.
nobezel = false
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = WINDOW
; display position and dimension (left,top,width,height)
frame.rect = 1205,1037,504,480
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; enable mouse clickspots if true, disable if false (use SHIFT to override)
usemouse = true
; display mouse tooltips if true.
tooltips = false
; freeze display position if true.
locked = false
; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button).
popleft = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true
; display as popout window if true (requires XP11.1).
undocked = false
; VR mode position and dimension (left,top,width,height) (requires XP11.20)
vrmode.rect = 0,395,415,395
; auto hide in external view if true.
autohide = true

[GTN_750_1.PANEL3D]
; display window if true.
visible = true
; show screen only gauge if true.
nobezel = true
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = PANEL3D
; display position and dimension (left,top,width,height)
frame.rect = 1218,2048,830,1024
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; enable mouse clickspots if true, disable if false (use SHIFT to override)
usemouse = true
; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button).
popleft = true
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true

I am coming around to the idea this problem is not created by GTN. But by XPLANE 11.50. If that can be settled that is progress of a sorts.

Thank you for the feedback. You've added the settings in the correct lines too.

With these options you should at least see the rxpGtnSim.dll.log file displaying a "GFX Debug" line. Can you spot it?

There are a few customers reporting other sorts of problems with XP11.50, mostly about graphics and related to OpenGL. This could be both with running XP11.50 in OGL mode or in Vulkan because in the later case, XP11.50 is creating an OGL context for plugins so that anything XP11 SDK 'drawing' related is working.

I doubt our plugin is freezing X-Plane as-is. What I  mean is the code in the plugin with is running inside the XP11 process is nearly 100% certainly not causing any freeze otherwise I'd suspect this kind of problem would be reported in our forums much more.

Otherwise the Garmin trainer could freeze but in this case it won't freeze X-Plane because it is a separate process. Instead the RXP GTN screen would freeze and no actions, even cycling power, would give any feedback. If there is such a GTN Trainer problem, enabling the 'debugging' settings I've mentioned may give the chance to write a log trace right before the trainer fails.

Of course the issue can also be related to the video card drivers and/or video card BIOS and you're just hitting a bug which takes a certain time, like the driver allocating more and more at a certain pace (say a buffer of 20 bytes every seconds) and it takes roughly 40 min to hit the threshold (this is just for illustration, I'm not saying this is what is happening in your case).

There remains possible hardware problems which could just be related to a memory module (RAM) having a failure which you're hitting only after a certain time because this is when the simulator has allocated just enough memory to hit the module. It could also be heat in the computer which takes about 40 minutes to build up (you might want to try with the case open and an extra room fan pointing toward the main board / components).

All in all I'm a little bit out of ideas but you might want just to cross check you've updated the OS to the latest fixes, your motherboard and components with their latest BIOS first. Then if someone can lend you a video card (preferably different model) you might want to try out and see if this fails again the same way. You might want to try out a few different video card driver versions and I'd suggest in this case you try the pre-Win10 2004 NVidia driver: 446.14.

Well I have integrated Radeon Vega Graphics -and this problem was happening before and after I updated to latest drivers last week Raedeon 20.9.2 released 9/22/2020. Never upgraded BIOS before but have the HP Help Utility that keeps all my system drivers up-to-date. And nothing shows in the utility needing updating,

Really looked at upgrading all my drivers when this happened

I've run STEAM -ARMA3, IL2 Battle of Stalingrad, DCS modules and my modest rig handles albeit at the low-to mid settings and no problems.

rxpGtnSim.dll.log file merely reads this

20/10/20 15:36:18.032 09080 -    ] # rxpGtnSim64.dll version 2.5.27.0
20/10/20 15:36:18.032 09080 INFO ]
20/10/20 15:37:04.913 09080 INFO ] GTN 750.1 - TRAINER 6624

Later this week I can take the RAM chips out and put them back in.[Remember years ago I had some problem and this trick fixed it]

I will try the fan trick you mentioned also. Since I'm running the same flight plan it always happens at the same time in the same coastal area of the map. (I've used different real and custom weather settings). So the amount of data the computer processes would be different...yet it always the exact same place-unless I run the sim at 2x the ground speed-but freezes after 40 minutes.

I have a Win7 backup machine but it would really chug along so I won't try that.

There are freezing incidents I have read about in the XPlane forum-but nothing like this. Ill try RAM chip take out-put back in and cooling this weekend.

What I will also do is clean out all my GTN750 folders and clean the registry of that application and then reinstall. Is their a particular key I should look for in the registry (I know -backup😆).

 

 

10 hours ago, Tempest555 said:

.yet it always the exact same place

And just to make sure I'll cross-check these first:

• is this over an area which is covered by a custom scenery?
• Or with a custom airport nearby (nearby could be 100nm away though)?
• What about flying over the same area with stock X-Plane scenery?
• Otherwise what about flying over another area?

Otherwise, I've helped once a relative with a computer which was randomly crashing or locking up, usually after a certain amount of time while 'gaming'. It turned out the RAM module was too close to the CPU heat sink and was causing a hardware problem with the RAM once past a certain temperature.

I've also personally had locks up and similar problem with XP11.50 during the beta and besides the ones I could document being caused by XP11 Vulkan WIP, there were some solely related to the scenery which needed to be updated in order to cure these problems most of the time.

I don't believe there is any need to 'cleanup' the RXP installation but the Garmin trainer only. Sometimes the trainer may 'damage' its own non-volatile memory file causing crashes or locks up. It is very rare but a bad combination of anti-virus or disk access could happen and the trainer code might fail. Usually you can solve this in deleting the file entirely and letting the trainer recreate one brand new (loosing all your stored routes and settings though).

@GiuseppeL98 Hi, I've merged your post into this discussion about what seems to be a similar problem.

Can you please first modify the RealityXP.GTN.ini file in your aircraft folder like illustrated in this post:

https://www.avsim.com/forums/topic/587230-xplane-11-freezes-now-with-gtn750-after-40-minutes/page/2/?tab=comments#comment-4383580

And then report the content of the RXP log files? (see user's manual for file/path).

 

 

Answers are Bold FONT

And just to make sure I'll cross-check these first:

• is this over an area which is covered by a custom scenery? Yes-but I ran it without the custom mesh (HAWAII). I'll run Calif and Washington this weekend.
• Or with a custom airport nearby (nearby could be 100nm away though)? Only custom airport scenery is NavAids scenary everything else is stock. Had that from the beginning. Flying off Oahu shore over Ocean is the flight plan.

https://store.x-plane.org/Global-Library-Enhancement-Replacements_p_555.html

• What about flying over the same area with stock X-Plane scenery? Try that tonight -but I know flew with stock GPS in T210. No problem with flight plan I built in stock xPlane GPS.
• Otherwise what about flying over another area? I will try it over Washington Cascades and California Sierras this weekend.

Otherwise, I've helped once a relative with a computer which was randomly crashing or locking up, usually after a certain amount of time while 'gaming'. It turned out the RAM module was too close to the CPU heat sink and was causing a hardware problem with the RAM once past a certain temperature. My HP case is a bit smaller then my Win 7 case.  Ill have it off and run a fan on it this weekend. I live in Hawaii-but room is cool with ceiling fan always running.

I've also personally had locks up and similar problem with XP11.50 during the beta and besides the ones I could document being caused by XP11 Vulkan WIP, there were some solely related to the scenery which needed to be updated in order to cure these problems most of the time. Using freeware-mesh for Hawaii, Calif and Washington State by - X-Plane 11 HD Mesh Scenery v4 -by Andras Fabian (www.alpilotx.net). ill fly trip with and without Calif and Washington Mesh 

https://flyawaysimulation.com/downloads/137/x-plane-11-hd-mesh-scenery-v4/

I don't believe there is any need to 'cleanup' the RXP installation but the Garmin trainer only. Sometimes the trainer may 'damage' its own non-volatile memory file causing crashes or locks up. It is very rare but a bad combination of anti-virus or disk access could happen and the trainer code might fail. Usually you can solve this in deleting the file entirely and letting the trainer recreate one brand new (loosing all your stored routes and settings though). My Anti Virus is Microsoft Defender . Ran sfc /scannow -nothing found missing and corrupted. Ran CCleaner. Didn't solve problem.

An AH HA! Moment last night..my STEAM XP11 exe. when I right clicked Properties I saw didn't have all the blocks checked for PERMISSIONS FOR ALL APPLICATIONS. I checked them all. No luck -same freezing.

We'll get to the bottom of it. Like what  my girlfriend and I say about COVID lockdown chores..."what else you got to do?" LOL

 

Thank you for the follow up.

Usually the only way to eliminate any side effect is to eliminate possible causes, which means running vanilla XP11 with default aircraft.

I understand the same scenery with stock GPS is working fine but it might just be the combination of the two (RXP+scenery) or just the RXP GTN and you can't tell apart unless you isolate components on their own. Therefore I'd still recommend you try without any 3rd party scenery of any sort first.

I thank you for your enduring patience with this!

Not a FREEZE but a crash.

Actually generated a log with data that asks you to email to LAMINER. Never had that before.

Vanilla STEAM XP11:50..No ANYTHING-Only GTN plugin. Flying a direct GTN 750 Flight Plan between San Luis Obispo,CA  KSBP --> Monterey, CA KMRY-roughly 35 minutes into flight (using G1000 timer.)

What was I doing? Flying stock Cessna 172 SP with custom weather [no real-time updates] using popup GTN750 screen. I tried zooming in on G1000 right screen to make a/c icon bigger on nav map *CRASH*

No Freeze.

Bad news I forgot to add in those 2 items in the GTN750ini.

LogTrainer = 5
DebugValue = 1

I will fly it again with those additional lines.

_________________________________________________

FROM rxpGtnSim.dll.log

20/10/24 21:27:47.568 10092 -    ] # rxpGtnSim64.dll version 2.5.27.0
20/10/24 21:27:47.567 10092 INFO ]
20/10/24 21:30:44.160 10092 INFO ] GTN 750.1 - TRAINER 6624
20/10/24 21:30:48.204 10092 INFO ] GTN 750.2 - TRAINER 6624
20/10/24 22:00:23.885 10092 INFO ] GTN 750.1 - TRAINER 6624
20/10/24 23:13:08.472 04620 INFO ] GTN 750.1 host application exited unexpectedly.
20/10/24 23:13:08.472 08072 INFO ] GTN 750.2 host application exited unexpectedly.
20/10/24 23:13:13.919 08072 INFO ] self-terminating orphaned GTN 750.2

____________________________

Portion of XPLANE LOG below-{usually Freezes and nothing produced in log}

1:40:49.708 D/ATC: Validating altitude for p=3 (N032JR): filed: 35000 usable_rte_dist: 1840.884399 maxDescent: 460000 maxAlt: 460000 minAlt: 35000 chosen_alt: 35000
1:40:49.708 D/ATC: p=3 (N032JR): Cleared IFR @ 10668FT
1:40:49.708 I/FLT: Init dat_p3 type:loc_specify_lle lat:35.728691 lon:-121.781105 ele(ft):35000.000267 psi:84.943687 spd(kts):299.250011
1:40:49.708 D/ATC: p=3 (N032JR): Fly Heading: 101
1:40:49.708 D/ATC: p=3 (N032JR): Maintain FL35000
1:40:49.708 I/ATC: Aircraft p=3 (N032JR) started airborne as an overflight at 35.728691, -121.781105, 10668.000000
1:42:32.327 W/ATC: Altitude Alert: p=3 (N032JR), Needs to CLIMB to 35000.000000, Cur_Indi: 34521.957031, Cur_Pres: 34682.722656, Last: 34827.703125
1:42:32.327 D/ATC: p=3 (N032JR): Maintain FL35000
1:42:32.327 I/ATC: BOEING 747-400 (international, winglets) 2JR, Climb and maintain FL 3 5 0.
1:42:32.327 E/ATC: Tried playing a wave file that doesn't exist: ')'
1:42:38.319 I/ATC: Up to FL 3 5 0, BOEING 747-400 (international, winglets) 2JR.
1:42:38.319 E/ATC: Tried playing a wave file that doesn't exist: ')'
1:45:09.584 E/SYS: MACIBM_alert: rel_assert Error! Possibly an out of range vector! Attach the debugger and see who called this!
1:45:09.584 E/SYS: MACIBM_alert: m_vbo
1:45:09.584 E/SYS: MACIBM_alert: setup_for_draw
1:45:09.584 E/SYS: MACIBM_alert: Please report this to Laminar Research.
1:45:09.584 E/SYS: MACIBM_alert: C:\jenkins\design-triggered\source_code\core\OGL\OGL_vbo.cpp:111
1:45:20.902 E/SYS: +-------------------------------------------------------------------------------
1:45:20.902 E/SYS: | rel_assert Error! Possibly an out of range vector! Attach the debugger and see who called this!
1:45:20.902 E/SYS: | m_vbo
1:45:20.902 E/SYS: | setup_for_draw
1:45:20.902 E/SYS: | Please report this to Laminar Research.
1:45:20.902 E/SYS: | (OGL_vbo.cpp:111)
1:45:20.902 E/SYS: +-------------------------------------------------------------------------------
--=={This application has crashed!}==--

 

OOps I was flying Cessna 172SP GTN

8 minutes ago, Tempest555 said:

1:45:09.584 E/SYS: MACIBM_alert: rel_assert Error! Possibly an out of range vector! Attach the debugger and see who called this!
1:45:09.584 E/SYS: MACIBM_alert: m_vbo
1:45:09.584 E/SYS: MACIBM_alert: setup_for_draw
1:45:09.584 E/SYS: MACIBM_alert: Please report this to Laminar Research.
1:45:09.584 E/SYS: MACIBM_alert: C:\jenkins\design-triggered\source_code\core\OGL\OGL_vbo.cpp:111
1:45:20.902 E/SYS: +-------------------------------------------------------------------------------
1:45:20.902 E/SYS: | rel_assert Error! Possibly an out of range vector! Attach the debugger and see who called this!
1:45:20.902 E/SYS: | m_vbo
1:45:20.902 E/SYS: | setup_for_draw
1:45:20.902 E/SYS: | Please report this to Laminar Research.
1:45:20.902 E/SYS: | (OGL_vbo.cpp:111)
1:45:20.902 E/SYS: +-------------------------------------------------------------------------------

Thank you for the additional information!

The XP11 log file clearly shows a problem internal with XP11 related to its OpenGL code and more particularly a Vertex Buffer Object. This looks like XP11 was trying to read or write too much data in a buffer (out of range error).

This could be a bug in their code (almost certainly), or something with your driver causing their code to fail (unlikely but possible).

NB: should you still want to do the test again with the 172SP, I'd suggest doing it with the non-G1000 variant because the G1000 is taking full control over the GPS (and is not granting the override_gps rights for 3rd party plugins).

PS: I'd suggest you file this to XP11 devs as a bug report.

Glad you responded when you did-I was about to fly. Will fly steam gauge XP Cessna 172 now. Same flight plan. Vanilla everything.

With regards to your P.S.

PS: I'd suggest you file this to XP11 devs as a bug report.

As soon as it crashed a wizard popped up asking for my email and what I was doing (typed: Tracking down freeze using GTN 750) and it was successfully sent to LAMINEAR per wizard notification.

Will edit ini for steam gauge XP Cessna 172 per earlier instructions

 

9 minutes ago, Tempest555 said:

typed: Tracking down freeze using GTN 750

Let's hope they won't just discard it prior reading the content because it is implying it might be crashing because of a plugin.

I'll probably read your next report not until tomorrow.

Edited October 25, 20205 yr by RXP

I have copy of that LOG text if you want me to send or post with no reference to GTN 750.

_______________________________________

Uneventful 2nd flight with excellent landing in steam gauge XP Cessna 172  using GTN 750 as pop-out.

Same route and weather. Acted normal.

 

This uneventful 2nd flight log from rxpGtnSim.dll.log

_________________________________________________

20/10/25 00:35:48.046 09500 -    ] # rxpGtnSim64.dll version 2.5.27.0
20/10/25 00:35:48.046 09500 INFO ]
20/10/25 00:37:20.417 09500 INFO ] GTN 750.1 - TRAINER 6624
20/10/25 00:37:20.477 09500 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin
20/10/25 00:37:20.517 09500 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\data
20/10/25 00:37:20.557 09500 INFO ] C:\ProgramData\Garmin\Trainers\Databases
20/10/25 00:37:20.598 09500 INFO ] C:\ProgramData\Garmin\Trainers\GTN\nonvol
20/10/25 00:37:21.444 09500 INFO ] GTN 750.2 - TRAINER 6624
20/10/25 00:38:39.831 09500 INFO ] GFX Debug: enabled.
20/10/25 03:53:52.682 01720 INFO ] GTN 750.2 - TRAINER 6624
20/10/25 03:54:01.547 01720 INFO ] GTN 750.1 - TRAINER 6624
20/10/25 03:54:01.598 01720 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\Bin
20/10/25 03:54:01.618 01720 INFO ] C:\Program Files (x86)\Garmin\Trainers\Packages\GTN\data
20/10/25 03:54:01.657 01720 INFO ] C:\ProgramData\Garmin\Trainers\Databases
20/10/25 03:54:01.689 01720 INFO ] C:\ProgramData\Garmin\Trainers\GTN\nonvol