Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GTN750 Black Screen with F33A and EMB-120 (resolved)

Featured Replies

Hi, 

I have issues with the GTN750. I only get a black screen in the 3D model of the device in the cockpit. The pop up window works fine and both, GTN and XP logs are clean. I have made sure it is set to power always on, to eliminate this issue. So far, I have found two aircraft, where it doesn´t work. However, I also use it in 3 other aircraft without any issues at all. 

Any ideas, what I am missing? I thought it might be the config I downloaded, but it seems to work fine for others. So maye I am missing something? Right now, I am dealing with the Carenado F33A and with the EMB-120. 

 

  • Author

Never mind. 

I solved it myself. There has been an issue with the .ini file. Sorry about that. 

  • 6 months later...

I have this exact issue with the Carenado Bonanza. It took me a while to figure out but if I delete the GTN…ini file and reload the airplane, opening the GTN plug-ins results in the 750 performing normal again. For some reason the black “rebooting…” screen is present on ever load of the plane unless I delete the ini file prior to loading. Not the end of the world as reloading the 750 plug-in upon opening the aircraft works but super annoying and clearly a bug somewhere. Happy to share my ini file is someone can figure out where the problem is.

Hey what did you fix in the ini file? I have the same issue also with the F33a. If I delete the ini file I can get the 750 to work upon reloading the plugin in XP11 but I have to do this ever time I close out XP.

Edited by Airmanf117
Notify me of replies

@Airmanf117 please do not cross post.

Is there any RealityXP.GTN.defaults.ini file in the aircraft folder?

  • 2 weeks later...

Thank you for the response. I would have replied sooner had if I known how to work the forum better. There is a RealityXP.GTN.ini file but not that says ‘default.’ I’ll include the content in a reply tomorrow. I’ve found that if I delete the ini file and reload the airplane, I’m able to fire up the 750/650 from the plug-in. It gets to be a pain having to go through this every time I want to use the simulator (and I’m sure that’s not how it was intended to work). 

 

 

 

 

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

[GTN_750_1]
; comma separated list of render targets.
drawto = WINDOW, PANELS
; is the master device if true.
MasterDevice = true
; 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 = true 
; 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 = -2357,1722,1032,1036
; 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 = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true 
; VR mode position and dimension (left,top,width,height) (requires XP11.20)
vrmode.rect = 0,395,415,395
; display as popout window if true (requires XP11.1).
undocked = true 
; display mouse tooltips if true.
tooltips = false
; freeze display position if true.
locked = false
; auto hide in external view if true.
autohide = false

[GTN_750_1.PANELS]
; display window if true.
visible = false
; show screen only gauge if true.
nobezel = true
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = PANELS
; display position and dimension (left,top,width,height)
frame.rect = 0,0,0,0
; 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 = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true

[GTN_650_2]
; comma separated list of render targets.
drawto = WINDOW, PANELS
; is the master device if true.
MasterDevice = false
; 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_650_2.WINDOW]
; display window if true.
visible = true
; 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 = -2351,688,1027,431
; 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 = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true
; VR mode position and dimension (left,top,width,height) (requires XP11.20)
vrmode.rect = 0,175,415,175
; display as popout window if true (requires XP11.1).
undocked = true
; display mouse tooltips if true.
tooltips = false
; freeze display position if true.
locked = false
; auto hide in external view if true.
autohide = false

[GTN_650_2.PANELS]
; display window if true.
visible = false
; show screen only gauge if true.
nobezel = true
; display type: WINDOW,PANEL2D,PANEL3D,PANELS
frame.type = PANELS
; display position and dimension (left,top,width,height)
frame.rect = 0,0,0,0
; 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 = false
; right mouse button on the screen toggles popup window if true (requires XP11.1).
popright = true
 

The ini file looks correct, except both [XXX.PANELS] sections are set with visible=false and frame.rect = 0,0,0,0 which means they won't draw on the 3D cockpit.

- I believe this is the auto generated default, not the one included with the Carenado isn't it?
- Actually is there any included with the Carenado?

If the GTN is "stuck" in "rebooting..." it really means it is rebooting (shutting down the garmin trainer in the background and restarting it) and if this keep displaying it means it hasn't completed this task yet, or got stucj doing so.

The only reason I can think could be causing this, because it has happened already with a few aircraft but corrected since, is when the aircraft code logic is fiddling with the GTN plugin, trying to enable/disable it. There have been a few aircraft where the developers are trying to control the GTN from their aircraft utility panels, instead of letting the user controlling this via the RXP menu and dynamically adapt the aircraft around it, and due to the very asynchronous nature of the plugin, you can't expect a good outcome if you do this thinking it will react synchronously. Unfortunately I don't have this aircraft to try repro.

 

10 hours ago, RXP said:

The ini file looks correct, except both [XXX.PANELS] sections are set with visible=false and frame.rect = 0,0,0,0 which means they won't draw on the 3D cockpit.

- I believe this is the auto generated default, not the one included with the Carenado isn't it?
- Actually is there any included with the Carenado?

If the GTN is "stuck" in "rebooting..." it really means it is rebooting (shutting down the garmin trainer in the background and restarting it) and if this keep displaying it means it hasn't completed this task yet, or got stucj doing so.

The only reason I can think could be causing this, because it has happened already with a few aircraft but corrected since, is when the aircraft code logic is fiddling with the GTN plugin, trying to enable/disable it. There have been a few aircraft where the developers are trying to control the GTN from their aircraft utility panels, instead of letting the user controlling this via the RXP menu and dynamically adapt the aircraft around it, and due to the very asynchronous nature of the plugin, you can't expect a good outcome if you do this thinking it will react synchronously. Unfortunately I don't have this aircraft to try repro.

 

I appreciate the response. I’m actually not sure if there is an ini file from Carenado. I’m not actually concerned about it not drawing to the 3D cockpit. I’m using it in pop out mode as part of a home cockpit so I don’t actually view the 3D cockpit. Something is certainly off because the 650 starts up every time while the 750 is stuck rebooting. In addition, the 750 loads fine in other planes which leads me to think there is an error with the specific plane. I’d transition to another plane but I’m too invested in the Bonanza in the home cockpit to do that.

If you try replacing the GTN 750 #1 with a GTN 650 #1 instead, what does it give?

If this is the aircraft trying to control our GTN 750, this would show. However if the aircraft is trying to control any #1 unit, this won't show much difference.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.