Rene_Feijen

How to panning the map?

Recommended Posts

How does panning the map or charts work? I seem not to be able to do that? I have the 650 and 750 installed in the A2A Bonanza and C182. All other functions work in the 2D popup panels, but not panning.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

5 hours ago, flopdoc said:

How does panning the map or charts work?

Dragging with the mouse pointer.

Share this post


Link to post
Share on other sites

I tried that of course, but that results in dragging the 2D panel, not the map.

 

In the Bonanza I installed the units with the official A2A installer program btw.

Edited by flopdoc

Share this post


Link to post
Share on other sites
7 hours ago, flopdoc said:

I tried that of course, but that results in dragging the 2D panel, not the map.

What are you using to bring up the 2D popup?   Scrolling is accomplished by using the mouse pointer while holding down the left mouse button.  If you have the popup set to be controlled by the left mouse button then you have a conflict.  Most of us I believe use the right mouse click to control the popup 2D gauge.

Edited by fppilot

Share this post


Link to post
Share on other sites
9 hours ago, flopdoc said:

I tried that of course, but that results in dragging the 2D panel, not the map.

Are you using the left edge of the VC unit bezel to open and close the popup?
When you left click in the screen area does the unit go into Graphically Edit FPL mode? If not, is your mouse programed in any way using the sim controls key assignments or FSUIPC?

Spoiler

yS5t2v9.jpg

 

Edited by BillS511

Share this post


Link to post
Share on other sites

Hi,

Like explained above it is just using your mouse pointer as a 'finder' to touch and drag.

However, should you've edited or are using a RealityXP.GTN.ini whose 'rendering section' settings tell to use the left mouse button to popup the gauge (popleft=), then, you obviously cannot expected the lest mouse button to auto-magically know whether you wish to panning or popup the window.

But we got you covered! Please review your ini file settings and more specifically the embedded settings comments. For popleft it reads:

; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button).

Share this post


Link to post
Share on other sites

I have a solution: it works if I display the 2D popup panel, undock the panel, move it to my second screen, adjust the size and then:

LOCK the window- that is the essential step!

Now it is completely working in the A2A Bonanza.

In the C182 it is also working, only thing is that if I popup 2D window, the image on the VC panel gets black. But that is no big deal, as I use the 2D window.

Edited by flopdoc
test

Share this post


Link to post
Share on other sites
1 hour ago, flopdoc said:

I popup 2D window, the image on the VC panel gets black.

Hi, are you sure you are actually using genuine Reality XP GTN Touch and not another product with a similar name?

Share this post


Link to post
Share on other sites
1 hour ago, RXP said:

Hi, are you sure you are actually using genuine Reality XP GTN Touch and not another product with a similar name?

Yes I am pretty sure! (also if I check my bank account! 😉

Share this post


Link to post
Share on other sites
2 hours ago, flopdoc said:

Yes I am pretty sure! (also if I check my bank account! 😉

Could you post the contents of your A2A Bonanza Panel.cfg and RealityXP.GTN.ini files this could help us identify the issue your having.

Share this post


Link to post
Share on other sites
5 hours ago, flopdoc said:

Yes I am pretty sure! (also if I check my bank account! 😉

Unlike other 'similarly named' products limited in their abilities to render in FltSim, our gauges in the VC cannot turn black whenever you open another instance of our gauge as a popup window. This is simply something 3rd party vendors cannot influence nor something inherent to our products, on the contrary, we take pride and brag about it:

Unless you've found a bug of course... 

Best way to ensure this is to just check your order receipt in your emails. If the product is labeled 'Reality XP' this is ours.

Share this post


Link to post
Share on other sites
18 hours ago, BillS511 said:

Could you post the contents of your A2A Bonanza Panel.cfg and RealityXP.GTN.ini files this could help us identify the issue your having.

This is the C182 panel (the Bonanza is fine)

 

// F1 dual
[Window Titles]
Window00=Main panel
Window01=Clipboard
Window02=Mini controls
Window03=Payload and fuel manager
Window04=Map
Window05=Quick radios
Window06=Maintenance hangar
Window07=Pre-flight inspection
Window08=AFK
Window09=none2    
Window10=dbg
Window11=none3
Window12=none4
Window13=GTN 650
Window14=GTN 750

[VIEWS]
VIEW_FORWARD_WINDOWS=10,20,30,FUEL_PANEL,40,50,51,52,53,54,100,101,102,103,104,105

//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1024,768
position=1
visible=0
ident=10

//gauge00=tester!tester, 420, 50, 400, 1000         //Comment for release

[Window01]
Background_color=0,0,0
size_mm=322,615
pixel_size=322,615
window_pos= 0.0, 0.2      
position=0
visible=0
ident=20
sizable=0

gauge00=A2A_C182!clipboard,  1,0,322,615

[Window02]
Background_color=0,0,0
size_mm=392,315
pixel_size=392,315
window_pos= 0.51, 0.2      
position=0
visible=0
ident=30
sizable=0

gauge00=A2A_C182!controls,   1,0,392,315

[Window03]
Background_color=0,0,0
size_mm=649,689
pixel_size=649,689
window_pos= 0.51, 0.2      
position=1
visible=1
ident=FUEL_PANEL
sizable=0

gauge00=A2A_C182!manager,  1,0,649,689


[Window04]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=1
ident=40
sizable=0

gauge00=A2A_C182!mapscreen,  255,1,770,766
gauge01=A2A_C182!map_settings,  1,50,246,232

[Window05]
Background_color=0,0,0
size_mm=187,392
pixel_size=187,392
position=6
window_pos= 0.025, 0.9
visible=1
ident=50
sizable=0

gauge00=A2A_C182!radios,  1,0,


[Window06]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=51
sizable=0

gauge00=A2A_C182!maint_hangar,  1,0,1024,768


[Window07]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=53
sizable=0
nomenu=1
type=special

gauge00=A2A_C182!walkaround,  0,0,1024,768


[Window08]
Background_color=0,0,0
size_mm=321,321
pixel_size=321,321
position=5
visible=1
ident=54
sizable=0

gauge00=A2A_C182!afk,  1,1,321,321


[Window09]
Background_color=0,0,0
ident=100
render_3d_window=1
nomenu=1
type=special

gauge00=A2A_C182!keys,  1,1,1,1
//gauge01=A2A_C182!cockpitBuilder, 2,2,2,2 //For cockpit builders only.

[Window10]
Background_color=0,0,0
size_mm=330,450
pixel_size=330,450
position=5
visible=0
nomenu=1
ident=101
sizable=0

//gauge00=dbg!panel,  144,0             //Comment for release

[Window11]
Background_color=1,1,1
ident=102
window_size=1.000,1.000
nomenu=1
zorder=100

gauge00=A2A_C182!blackout,  0,0

[Window12]
Background_color=0,0,0
size_mm=650,624
pixel_size=650,624
position=3
visible=0
ident=103
nomenu=1
zorder=99

gauge00=A2A_C182!engine_details,  1,1,650,624        

[Window13]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

[Window14]
Background_color=0,0,0
size_mm=937,390
ident=14403
window_pos= 0.660, 0.740
window_size= 0.340, 0.260
zorder=99
gauge00=rxpGTN!GTN_650_1, 0, 0,937,390

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle

gauge01=A2A_C182!code_c182t_r, 1,1,1,1
gauge02=A2A_C182!status1,2,2,2,2
gauge03=A2A_C182!damage,    3,3,3,3
gauge04=accusim_xml!code_s,    4,4,4,4
gauge05=A2A_Accusim!lua,    5,5,5,5
gauge06=A2A_Accusim!AVS,    6,6,6,6
gauge07=A2A_Accusim!events,    7,7,7,7
gauge08=A2A_Accusim!random,    8,8,8,8
gauge09=A2A_Accusim!storage,    9,9,9,9
gauge10=A2A_C182!code_c182t_m, 1,1,1,1
gauge11=gps!gps_500,    0,0,1065,675
gauge12=C182!avionics, 0, 576, 1024,447
gauge13=A2A_C182!annunciator, 1, 454, 854,120
gauge14=A2A_C182!number, 794, 0, 228,77
gauge15=A2A_C182!aoa_indexer, 993, 79, 29, 58
gauge16=A2A_C182!GPS_F1_dual, 1, 1, 1, 1

[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle1

gauge00=C182!lightmap, 0, 576, 1024,447

[VCockpit02]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0

gauge00=F1GTN!GTN750VC, 0,0,677,794,UNIT1

[VCockpit03]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN650
background_color=0,0,0

gauge00=F1GTN!GTN650VC, 0,0,677,297,UNIT1

[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c1_l

gauge00=C182_Illumination!c1, 0, 0, 1024, 1024

[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c2_l

gauge00=C182_Illumination!c2, 0, 0, 1024, 1024

[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c5_l

gauge00=C182_Illumination!c5, 0, 0, 1024, 1024

[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c7_l

gauge00=C182_Illumination!c7, 0, 0, 1024, 1024

[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c9_l

gauge00=C182_Illumination!c9, 0, 0, 1024, 1024

[Vcockpit09]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$vc_gxml_l

gauge00=C182_Illumination!vc_gxml, 0, 0, 1024, 1024

[Vcockpit10]
Background_color=0,0,0
size_mm=2048,2048
visible=0
pixel_size=2048,2048
texture=$rain
gauge00=Windshield!main,0,0,0,0
texture00=Windshield, 0,0,2048,2048

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

 

Edited by RXP

Share this post


Link to post
Share on other sites

This is the Realityxp.gtn.ini in the  A2A C182 folder (there is also one in the users/doc folder

   

[GTN_750_1]
; is the master device if true.
MasterDevice = true
; selects COM/NAV Radios '1' or '2'.
RadiosPair = 1
; uses computer time if true, simulator time otherwise.
ComputerTime = false
; connects GPS to Autopilot if true.
LinkOto = true
; connects GPS to HSI if true.
LinkHsi = true
; connects GPS to HSI course motor if true.
LinkCrs = false
; connects GPS to OBS input if true (LinkHsi/OBS or AutoNavSource/OBS) (NB: HSI/OBS = NAV1 OBS).
LinkObs = false
; connects GPS to VOR if true.
LinkVor = false
; override VLOC NAV# (1 or 2) or use 'RadiosPair' (0).
AutoNavSource = 0
; connects CDI mode to NAV/GPS switch if true.
AutoNavGps = true
; HSI lateral deviation scale factor.
CdiScale = 1
; HSI vertical deviation scale factor.
GsiScale = 1
; connects GPS to Audio Panel if true.
UseAudioPanel = true
; connects GPS to Transponder if true.
UseTransponder = true
; enables Shadin Air Data computer if true.
UseAirData = true
; enables Shadin Fuel Data computer if true.
UseFuelData = true
; enables RYAN 9900BX TCAD if true.
UseRyanTcad = false
; sets TCAD sound alerts volume in percent: 0 to 100.
RyanTcadVolume = 50
; enables device failures if true.
UseFailures = false
; uses Simulator GPS commands if true.
UseSimGpsCmds = false
; updates Simulator GPS flight plan if true.
LinkSimGps = false
; saves the active route as a flight plan file if true (.PLN)
AutoSavePln = false
; uses legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; sets fuel type: AVGAS,JETA,JETB,DIESEL
FuelType = AVGAS
; use transponder VFR code: USE_CODE,VFR_US,VFR_EUR
VFRmode = VFR_US
; sets transponder VFR code (octal default: #1200).
VFRcode = #1200
; sets device power source:
; ALWAYS_ON,AVIONICS_ON,PANEL_ON,BUS_MAIN,BUS_AVIONICS,BUS_BATT,BUS_HOTBATT,BUS_1,BUS_2,BUS_3,BUS_4
PowerSource = AVIONICS_ON
; sets ownship icon type:
; AUTO,LOW_WING,HIGH_WING,KIT_PLANE,TURBOPROP,TWIN_ENGINE,SINGLE_JET,BUSINESS_JET,2BLADES,3BLADES,4BLADES,ARROW
OwnshipIcon = AUTO
; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2
NavDbType = 1
; sets TAWS type: TERR,TAWS_B,TAWS_A
TawsMode = TERR
; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY
TawsSurface = HARD_SOFT
; TAWS minimum runway length (feet)
TawsMinLength = 40
; TAWS approach air speed (knots), or -1 (auto detect Vref: 65)
TawsApprSpeed = -1
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 120)
TawsFlapSpeed = -1
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 0)
TawsGearSpeed = -1
; reduce screen update rate by half.
ReduceRate = false
; integral lighting percent (0 to 100) or index (-1) (using rxp.panel.rheostat_screen)
Rheostat.Display = 100
; integral lighting percent (0 to 100) or index (-1) (using rxp.panel.rheostat_integral)
Rheostat.Buttons = 75
; sets voice type: MALE,FEMALE
VoicePref = MALE
; sets master sound volume in percent: 0 to 100.
MasterVolume = 100
; mute sound when simulator window looses focus if false.
NoAudioFocus = false
; sets trainer process CPU: 1 to 32 (0: last core, -1: automatic).
CpuAffinity = -1
; main: CDI Key (0: disable)
AFMS.cdi_key =
; main: Selected Course for GPS (0: disable)
AFMS.sel_crs_gps =
; main: Selected Course for VLOC (0: disable)
AFMS.sel_crs_vloc =
; main: V-Flag State (1: declutter)
AFMS.v_flag_declutter =
; main: GPS Selected (0: prompt)
AFMS.gps_selected =
; main: Airspace Labels (0: disable)
AFMS.airspace_labels =
; nav : Mark On Target (1: enable)
AFMS.mark_on_target =
; nav : RF Procedure Legs (1: enable)
AFMS.rf_procedure_legs =
; vnav: Vertical Navigation Type (0: VCALC, 1: VNAV)
AFMS.vnav_enabled =
; vnav: Transition To Approach (0: disable)
AFMS.vnav_trans_to_appr =
; vnav: VDI Scale (default: 500ft)
AFMS.vnav_vdi_scale_factor =
; vnav: Transition Altitude (default: FL180)
AFMS.vnav_trans_altitude =

[GTN_750_1.DEFAULT]
; show screen only gauge if true.
nobezel = false
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; display mouse tooltips if true.
tooltips = false
; enable mouse clickspots if true, disable if false.
usemouse = true
; enable alternate click-spots (left CCW, right CW, middle Push) if true.
usealtmouse = false
; enable touch beyond screen bounds if true (2D only), clip if false (GTN native).
extendtouch = true
; auto-resize dimension (width,height)
refsize =
; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button).
popleft =
; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popright =
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

[GTN_650_1]
; is the master device if true.
MasterDevice = false
; selects COM/NAV Radios '1' or '2'.
RadiosPair = 1
; uses computer time if true, simulator time otherwise.
ComputerTime = false
; connects GPS to Autopilot if true.
LinkOto = true
; connects GPS to HSI if true.
LinkHsi = true
; connects GPS to HSI course motor if true.
LinkCrs = false
; connects GPS to OBS input if true (LinkHsi/OBS or AutoNavSource/OBS) (NB: HSI/OBS = NAV1 OBS).
LinkObs = false
; connects GPS to VOR if true.
LinkVor = false
; override VLOC NAV# (1 or 2) or use 'RadiosPair' (0).
AutoNavSource = 0
; connects CDI mode to NAV/GPS switch if true.
AutoNavGps = true
; HSI lateral deviation scale factor.
CdiScale = 1
; HSI vertical deviation scale factor.
GsiScale = 1
; connects GPS to Audio Panel if true.
UseAudioPanel = true
; connects GPS to Transponder if true.
UseTransponder = true
; enables Shadin Air Data computer if true.
UseAirData = true
; enables Shadin Fuel Data computer if true.
UseFuelData = true
; enables RYAN 9900BX TCAD if true.
UseRyanTcad = false
; sets TCAD sound alerts volume in percent: 0 to 100.
RyanTcadVolume = 50
; enables device failures if true.
UseFailures = false
; uses Simulator GPS commands if true.
UseSimGpsCmds = false
; updates Simulator GPS flight plan if true.
LinkSimGps = false
; saves the active route as a flight plan file if true (.PLN)
AutoSavePln = false
; uses legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; sets fuel type: AVGAS,JETA,JETB,DIESEL
FuelType = AVGAS
; use transponder VFR code: USE_CODE,VFR_US,VFR_EUR
VFRmode = VFR_US
; sets transponder VFR code (octal default: #1200).
VFRcode = #1200
; sets device power source:
; ALWAYS_ON,AVIONICS_ON,PANEL_ON,BUS_MAIN,BUS_AVIONICS,BUS_BATT,BUS_HOTBATT,BUS_1,BUS_2,BUS_3,BUS_4
PowerSource = AVIONICS_ON
; sets ownship icon type:
; AUTO,LOW_WING,HIGH_WING,KIT_PLANE,TURBOPROP,TWIN_ENGINE,SINGLE_JET,BUSINESS_JET,2BLADES,3BLADES,4BLADES,ARROW
OwnshipIcon = AUTO
; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2
NavDbType = 1
; sets TAWS type: TERR,TAWS_B,TAWS_A
TawsMode = TERR
; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY
TawsSurface = HARD_SOFT
; TAWS minimum runway length (feet)
TawsMinLength = 40
; TAWS approach air speed (knots), or -1 (auto detect Vref: 65)
TawsApprSpeed = -1
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 120)
TawsFlapSpeed = -1
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 0)
TawsGearSpeed = -1
; reduce screen update rate by half.
ReduceRate = false
; integral lighting percent (0 to 100) or index (-1) (using rxp.panel.rheostat_screen)
Rheostat.Display = 100
; integral lighting percent (0 to 100) or index (-1) (using rxp.panel.rheostat_integral)
Rheostat.Buttons = 75
; sets voice type: MALE,FEMALE
VoicePref = MALE
; sets master sound volume in percent: 0 to 100.
MasterVolume = 100
; mute sound when simulator window looses focus if false.
NoAudioFocus = false
; sets trainer process CPU: 1 to 32 (0: last core, -1: automatic).
CpuAffinity = -1
; main: CDI Key (0: disable)
AFMS.cdi_key =  
; main: Selected Course for GPS (0: disable)
AFMS.sel_crs_gps =  
; main: Selected Course for VLOC (0: disable)
AFMS.sel_crs_vloc =  
; main: V-Flag State (1: declutter)
AFMS.v_flag_declutter =  
; main: GPS Selected (0: prompt)
AFMS.gps_selected =  
; main: Airspace Labels (0: disable)
AFMS.airspace_labels =  
; nav : Mark On Target (1: enable)
AFMS.mark_on_target =  
; nav : RF Procedure Legs (1: enable)
AFMS.rf_procedure_legs =  
; vnav: Vertical Navigation Type (0: VCALC, 1: VNAV)
AFMS.vnav_enabled =  
; vnav: Transition To Approach (0: disable)
AFMS.vnav_trans_to_appr =  
; vnav: VDI Scale (default: 500ft)
AFMS.vnav_vdi_scale_factor =  
; vnav: Transition Altitude (default: FL180)
AFMS.vnav_trans_altitude =  

[GTN_650_1.DEFAULT]
; show screen only gauge if true.
nobezel = false
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; display mouse tooltips if true.
tooltips = false
; enable mouse clickspots if true, disable if false.
usemouse = true
; enable alternate click-spots (left CCW, right CW, middle Push) if true.
usealtmouse = false
; enable touch beyond screen bounds if true (2D only), clip if false (GTN native).
extendtouch = true
; auto-resize dimension (width,height)
refsize =
; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button).
popleft =
; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popright =
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

 

Edited by RXP

Share this post


Link to post
Share on other sites
47 minutes ago, RXP said:

Unlike other 'similarly named' products limited in their abilities to render in FltSim, our gauges in the VC cannot turn black whenever you open another instance of our gauge as a popup window. This is simply something 3rd party vendors cannot influence nor something inherent to our products, on the contrary, we take pride and brag about it:

Unless you've found a bug of course... 

Best way to ensure this is to just check your order receipt in your emails. If the product is labeled 'Reality XP' this is ours.

The receipt says

 

Thank you for you Flight1.com electronic software purchase! Here is your purchase information:

 

Order Number: xxxxxxx
Feb 4 2:59:24 AM 2019
Vendor: RealityXP  

 

Quantity
Product
Price ($cur)
1
RealityXP Garmin GTN 650 (FltSim)
$24.95
Total:
$24.95

Share this post


Link to post
Share on other sites
4 hours ago, flopdoc said:

[Window13]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

[Window14]
Background_color=0,0,0
size_mm=937,390
ident=14403
window_pos= 0.660, 0.740
window_size= 0.340, 0.260
zorder=99
gauge00=rxpGTN!GTN_650_1, 0, 0,937,390

 

4 hours ago, flopdoc said:

[VCockpit02]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0

gauge00=F1GTN!GTN750VC, 0,0,677,794,UNIT1

[VCockpit03]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN650
background_color=0,0,0

gauge00=F1GTN!GTN650VC, 0,0,677,297,UNIT1

Are you running 2 GTN's RXP and F1?

Windows 13 & 14 (popups) are correct for RXP units.

But...

VCockpit 2 & 3 are F1 gauges.

My suggestion is to run the A2A 182 Configurator again. Then load aircraft and run the RXP panel wizard making sure it looks like this:
o9tUy4w.png

 

  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites

Hi,

No I am only running the RXP gauges, but per instructions somewhere else on a forum I first pretended to install the F1 gauges (which I do not own)  via A2A config and then automatically detect and replace with RXP gauges via Rxp in addon menu within P3D. And I found that installation config panel somewhat confusing.

I will try your recommendations.

Edited by flopdoc

Share this post


Link to post
Share on other sites

@flopdoc Indeed it is.a genuine Reality XP GTN, only the panel.cfg file is just half-correct like Bill is pointing up.

Can you please help us better our products and detail a little more what do you find 'somewhat confusing'?

Share this post


Link to post
Share on other sites

Wow, it now works! I did what Bill suggested with the A2A configurator. I also had to tick the No bezel marks.

I would not have come up with the idea to first fake-install F1 instruments and then replace them with RXP versions.

Confusing is: what is 750 1 and 750 2? No clue as to which one to chose. And: with bezel or without? What are the consequences? Why do I see 625 etc?

I now managed with trial and error.

Edited by flopdoc

Share this post


Link to post
Share on other sites
24 minutes ago, flopdoc said:

Confusing is: what is 750 1 and 750 2? No clue as to which one to chose.

Your purchase includes (2) gauges.  Like you just purchased two television sets where one can go in your family room and the other in your bedroom.  In this case you can install 750_1 in some aircraft and 750_2 in other aircraft.  Or you can in some aircraft, where the panel and support allow for it, install both _1 and _2 in the same panel and use each one for different GTN functions.

I use my 750_1 in longer range aircraft models and store in it associated flight plans for long flights. Conversely, for my 750_2, I use it in smaller, short range aircraft models and accordingly store shorter flight plans in _2.  Just my personal choice.

To contrast. You could also use 750 _1 in aircraft you use on say the USA west coast, and store appropriate flight plans according to that location, and perhaps use 750_2 in aircraft you use in the Caribbean, storing Caribbean flight plans there.  Just a couple of possibilities on use.

Be aware that currently you cannot crossfill flight plans direct from one to the other.  So if you are using both in a single panel and wish to use flight plan capabilities in both you must enter that flight plan individually into both.

Edited by fppilot
  • Like 2

Share this post


Link to post
Share on other sites
3 minutes ago, fppilot said:

Your purchase includes (2) gauges.  Like you just purchased two television sets where one can go in your family room and the other in your bedroom.  In this case you can install 750_1 in some aircraft and 750_2 in  [ ...]. direct from one to the other.  So if you are using both in a single panel and wish to use flight plan capabilities in both you must enter that flight plan individually into both.

Thanks for the clear explanation!

Share this post


Link to post
Share on other sites
48 minutes ago, flopdoc said:

Why do I see 625 etc?

The 625 and 635 have fewer features than the 650. If your aircraft has a nav, or comm radio or both you could choose to install the 625 or 635.

625 GPS/MFD. 635 GPS/COMM/MFD. 650 GPS/NAV/COMM/MFD.

725 GPS/MFD. 750 GPS/NAV/COMM/MFD.

On your desktop you should find a shortcut to the Garmin trainers that include these different versions.

Also check out the tutorial videos.

 

Edited by BillS511
  • Like 2

Share this post


Link to post
Share on other sites

You might want to also run the Garmin Trainer standalone and open the Garmin GTN Pilot's Guide. Differences between these device models is explained in great details, along with all there is to know about the various GTN functions.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now