I went to install the 750 in the Turbine Duke and ran into a problem.  I selected "Replace Gauges with Reality XP GTN (auto-detect)", selected the "no-bezel" option (it already has a bezel).  It installed the GTN with a bezel...ugh.  So I selected the "Remove" option so I could re-add now the place where I am installing it is gone from the options so it's not auto-detecting it any more.  Help?  

Hi Gregg,

Whenever the assistant modifies the panel.cfg file, it creates a backup.

You might want to select the last assistant option: 'restore panel (auto-backup)' instead. This option restores the panel.cfg to the state its prior content.

5 minutes ago, RXP said:

Hi Gregg,

Whenever the assistant modifies the panel.cfg file, it creates a backup.

You might want to select the last assistant option: 'restore panel (auto-backup)' instead. This option restores the panel.cfg to the state its prior content.

I don't see that option in the "Setup Aircraft" dialog.  Does it put the backup somewhere?

The backup gets created side-by-side the panel.cfg file in the aircraft folder.

It has a filename set like this: "panel_date_time.rxp" (for example: panel_170824_221407.rxp)

You can open this file with notepad.exe to check its content.

Do you seen a file like this?

 

 

Hi Gregg,

Here's an original panel.cfg for the Turbine Duke v2. It's setup for the F1 750. Ready to configure for the RXP 750.

Spoiler

// Panel Configuration file
// RealAir Simulations Beechcraft Turbine Duke V2 2014 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright (c) 2014 RealAir Simulations

// ===============================================================================
// IMPORTANT - 'Window01' AND 'Window02' BELOW ARE RESERVED FOR GPS POPUPS AND CAN
// BE OVERWRITTEN BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY
// EDITING THIS FILE. IF YOU WANT TO ADD CUSTOM WINDOW ENTRIES, YOU CAN USE ANY
// VALUE FROM 'Window03' TO 'Window 09'.
// ===============================================================================

[Window Titles]
Window00=Main Panel
Window01=Flight1 Garmin GTN750 U1 - DO NOT MODIFY
Window02=Blank

[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[Window01]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos=0.660, 0.000
window_size=0.340, 0.580
zorder=99
gauge00=F1GTN!GTN750,  0,0,937,887,UNIT1.POP

[Window02]
size_mm=1,1
position=0
visible=0
ident=15600
BACKGROUND_COLOR=0,0,0
gauge00=RASDuke!Blank, 0, 0, 1, 1

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=Config!RadioLayout, 1027, 1023, 1, 1

gauge04=RASDuke!InitVars, 1022, 1023, 1, 1
gauge05=RASDuke!1hzCode, 1023, 1023, 1, 1
gauge06=RASDuke!2hzCode, 1024, 1023, 1, 1
gauge07=RASDuke!18hzCode, 1025, 1023, 1, 1

gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!KA285_Annun, 512,2,337,108
gauge15=RASDuke!Annunciator_Turbine, 516, 111, 226, 245
gauge16=RASDuke!Moritz_LCD, 808, 133, 214, 259
gauge17=RASDuke!Fuel_Qty_LCD, 410, 128, 105, 86
gauge18=RASDuke!Master_Warn, 893, 1, 130, 129

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN
// BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE
// IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY
// CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22'
// ===============================================================================

gauge19=F1GTN!GTN750VC, 2,563,390,460,UNIT1
gauge20=RASDuke!Blank, 0, 0, 1, 1

gauge21=RASDukeTv2_Sound!Sound, 1,1,2,2, \Sound\RASDukeTv2_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1
gauge24=Config!ModelOptions, 1020, 1023, 1, 1

Day=255,255,255
Night=225,117,89
Luminous=200,200,101

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6144

 

 

44 minutes ago, RXP said:

The backup gets created side-by-side the panel.cfg file in the aircraft folder.

It has a filename set like this: "panel_date_time.rxp" (for example: panel_170824_221407.rxp)

You can open this file with notepad.exe to check its content.

Do you seen a file like this?

 

 

I got it.  Also found out that the "No Bezel" is a checkbox...aha.  I restored the file.  Thg GTN750 is there now...I think.  The dialog box says it is but it won't come on.  The popup comes up by clicking the left side of the bezel.

14 minutes ago, Gregg_Seipp said:

won't come on

Can you post the panel.cfg contents?

Here you go...

Quote

// Panel Configuration file
// RealAir Simulations Beechcraft Turbine Duke V2 2014 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright (c) 2014 RealAir Simulations

// ===============================================================================
// IMPORTANT - 'Window01' AND 'Window02' BELOW ARE RESERVED FOR GPS POPUPS AND CAN 
// BE OVERWRITTEN BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY 
// EDITING THIS FILE. IF YOU WANT TO ADD CUSTOM WINDOW ENTRIES, YOU CAN USE ANY 
// VALUE FROM 'Window03' TO 'Window 09'.
// ===============================================================================

[Window Titles]
Window00=Main Panel
Window01=Flight1 Garmin GTN750 U1 - DO NOT MODIFY
Window02=Blank

[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[Window01]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos=0.660, 0.000
window_size=0.340, 0.580
zorder=99
gauge00=F1GTN!GTN750,  0,0,937,887,UNIT1.POP

[Window02]
size_mm=1,1
position=0
visible=0
ident=15600
BACKGROUND_COLOR=0,0,0
gauge00=RASDuke!Blank, 0, 0, 1, 1

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=Config!RadioLayout, 1027, 1023, 1, 1

gauge04=RASDuke!InitVars, 1022, 1023, 1, 1
gauge05=RASDuke!1hzCode, 1023, 1023, 1, 1
gauge06=RASDuke!2hzCode, 1024, 1023, 1, 1
gauge07=RASDuke!18hzCode, 1025, 1023, 1, 1

gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!KA285_Annun, 512,2,337,108
gauge15=RASDuke!Annunciator_Turbine, 516, 111, 226, 245
gauge16=RASDuke!Moritz_LCD, 808, 133, 214, 259
gauge17=RASDuke!Fuel_Qty_LCD, 410, 128, 105, 86
gauge18=RASDuke!Master_Warn, 893, 1, 130, 129

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN 
// BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE
// IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY 
// CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22'
// ===============================================================================

gauge19=F1GTN!GTN750VC, 2,563,390,460,UNIT1
gauge20=RASDuke!Blank, 0, 0, 1, 1

gauge21=RASDukeTv2_Sound!Sound, 1,1,2,2, \Sound\RASDukeTv2_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1
gauge24=Config!ModelOptions, 1020, 1023, 1, 1

Day=255,255,255
Night=225,117,89
Luminous=200,200,101

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6144
 

 

[Window01]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos=0.660, 0.000
window_size=0.340, 0.580
zorder=99
gauge00=F1GTN!GTN750,  0,0,937,887,UNIT1.POP

Change to;

gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

 

under [VCockpit01]:

gauge19=F1GTN!GTN750VC, 2,563,390,460,UNIT1

Change to;

gauge19=rxpGTN!GTN_750_1, 2,563,390,460,NO_BEZEL

 

 

Also you should have this file; RealityXP.GTN.ini in your main  RealAir Duke Turbine V2 folder.

Contents of RealityXP.GTN.ini

Spoiler

[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
; reduce screen update rate by half.
ReduceRate = false
; integral lighting percent (0 to 100)
Rheostat.Display = 100
; integral lighting percent (0 to 100)
Rheostat.Buttons = 75
; connects GPS to HSI if true.
LinkHsi = true
; connects GPS to HSI course if true.
LinkCrs = false
; connects HSI OBS to GPS if true.
LinkObs = false
; connects GPS to VOR if true.
LinkVor = false
; connects GPS to Autopilot if true.
LinkOto = true
; connects CDI key to NAV/GPS switch if true.
AutoNavGps = true
; enables automatic GPS/VLOC selection.
AutoSelect = true
; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'.
AutoNavSource = 0
; sets device power source: ALWAYS_ON,AVIONICS_BUS,MAIN_BATTERY
PowerSource = AVIONICS_BUS
; connects GPS to Shadin Air Data computer if true.
UseAirData = true
; connects GPS to Shadin Fuel Data computer if true.
UseFuelData = true
; connects GPS to Audio Panel if true.
UseAudioPanel = true
; connects GPS to Transponder if true.
UseTransponder = true
; connects GPS to RYAN 9900BX if true.
UseRyanTcad = true
; sets TCAD sound alerts volume in percent: 0 to 100.
RyanTcadVolume = 50
; enable 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 Simulator flight plan if true.
AutoSavePln = true
; use legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; sets transponder VFR code (octal default: #1200).
VFRcode = #1200
; sets fuel type: AVGAS,JETA,JETB,DIESEL
FuelType = AVGAS
; sets ownship icon type:
; AUTO,LOW_WING,HIGH_WING,KIT_PLANE,TURBOPROP,TWIN_ENGINE,SINGLE_JET,BUSINESS_JET,2BLADES,3BLADES,4BLADES,ARROW
OwnshipIcon = AUTO
; sets TAWS type: TERR,TAWS_B,TAWS_A
TawsMode = TAWS_A
; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY
TawsSurface = HARD_SOFT
; TAWS minimum runway length (feet)
TawsMinLength = 40
; TAWS approach air speed (knots), -1 (auto detect Vref: 0)
TawsApprSpeed = 0
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 0)
TawsFlapSpeed = 0
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 0)
TawsGearSpeed = 0
; HSI lateral deviation scale factor.
CdiScale = 1
; HSI vertical deviation scale factor.
GsiScale = 1
; sets voice type: MALE,FEMALE
VoicePref = MALE
; sets master sound volume in percent: 0 to 100.
MasterVolume = 100
; selects the default database: 0: 'Garmin (North America)', 1: 'Jeppesen (Worldwide)'
NavDbType = 0
; selects the CPU running the trainer process: 1 to 32
; 0: last core, -1: automatic.
CpuAffinity = -1

[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 popup ident  (ex: GPS_PANEL or 225) (disables touchscreen when set).
popleft =
; right mouse button popup ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

 

35 minutes ago, bills511 said:

Also you should have this file; RealityXP.GTN.ini in your main  RealAir Duke Turbine V2 folder.

Contents of RealityXP.GTN.ini

  Hide contents

[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
; reduce screen update rate by half.
ReduceRate = false
; integral lighting percent (0 to 100)
Rheostat.Display = 100
; integral lighting percent (0 to 100)
Rheostat.Buttons = 75
; connects GPS to HSI if true.
LinkHsi = true
; connects GPS to HSI course if true.
LinkCrs = false
; connects HSI OBS to GPS if true.
LinkObs = false
; connects GPS to VOR if true.
LinkVor = false
; connects GPS to Autopilot if true.
LinkOto = true
; connects CDI key to NAV/GPS switch if true.
AutoNavGps = true
; enables automatic GPS/VLOC selection.
AutoSelect = true
; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'.
AutoNavSource = 0
; sets device power source: ALWAYS_ON,AVIONICS_BUS,MAIN_BATTERY
PowerSource = AVIONICS_BUS
; connects GPS to Shadin Air Data computer if true.
UseAirData = true
; connects GPS to Shadin Fuel Data computer if true.
UseFuelData = true
; connects GPS to Audio Panel if true.
UseAudioPanel = true
; connects GPS to Transponder if true.
UseTransponder = true
; connects GPS to RYAN 9900BX if true.
UseRyanTcad = true
; sets TCAD sound alerts volume in percent: 0 to 100.
RyanTcadVolume = 50
; enable 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 Simulator flight plan if true.
AutoSavePln = true
; use legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; sets transponder VFR code (octal default: #1200).
VFRcode = #1200
; sets fuel type: AVGAS,JETA,JETB,DIESEL
FuelType = AVGAS
; sets ownship icon type:
; AUTO,LOW_WING,HIGH_WING,KIT_PLANE,TURBOPROP,TWIN_ENGINE,SINGLE_JET,BUSINESS_JET,2BLADES,3BLADES,4BLADES,ARROW
OwnshipIcon = AUTO
; sets TAWS type: TERR,TAWS_B,TAWS_A
TawsMode = TAWS_A
; sets TAWS surface: HARD,HARD_SOFT,WATER,ANY
TawsSurface = HARD_SOFT
; TAWS minimum runway length (feet)
TawsMinLength = 40
; TAWS approach air speed (knots), -1 (auto detect Vref: 0)
TawsApprSpeed = 0
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 0)
TawsFlapSpeed = 0
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 0)
TawsGearSpeed = 0
; HSI lateral deviation scale factor.
CdiScale = 1
; HSI vertical deviation scale factor.
GsiScale = 1
; sets voice type: MALE,FEMALE
VoicePref = MALE
; sets master sound volume in percent: 0 to 100.
MasterVolume = 100
; selects the default database: 0: 'Garmin (North America)', 1: 'Jeppesen (Worldwide)'
NavDbType = 0
; selects the CPU running the trainer process: 1 to 32
; 0: last core, -1: automatic.
CpuAffinity = -1

[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 popup ident  (ex: GPS_PANEL or 225) (disables touchscreen when set).
popleft =
; right mouse button popup ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

 

That did it!  Thanks again Bill!  Wow, this is a nice unit.

3 minutes ago, Gregg_Seipp said:

That did it!  Thanks again Bill!  Wow, this is a nice unit.

Awesome! Glad you got it working.

Do the Home, DirectTo, Volume and Large/Small Knob actually work when you use the above integration technique? Because they don't for me - and I assume this is because these controls are part of the Duke 3D model and don't pass clicks to the RealityXP gauge?

If this is the case, how do you set comms frequencies etc on the RXP GTN in the Duke virtual cockpit? (Or is the idea to use the popop 2D version of the GTN for this?)

 

Thanks
Peter Jones

@paj 

 

2 hours ago, paj said:

Do the Home, DirectTo, Volume and Large/Small Knob actually work when you use the above integration technique? Because they don't for me - and I assume this is because these controls are part of the Duke 3D model and don't pass clicks to the RealityXP gauge?

If this is the case, how do you set comms frequencies etc on the RXP GTN in the Duke virtual cockpit? (Or is the idea to use the popop 2D version of the GTN for this?)

 

Thanks
Peter Jones

No. The virtual cockpit knobs and buttons do not work with my RXP GTN configuration and they do work with my F1 GTN configuration.  To add to that however is that the GTN 750 in either case is so small in my virtual cockpit that for most purposes I must pop it up to use it.  And even when popped up I find I use the on-screen keypad functions to change frequencies instead of the knobs.  I also find that I seldom use the Home button.  The Direct button works with the F1 virtual cockpit configuration, but once pressed the ability to select a waypoint using the smallish virtual cockpit gauge defaults me again to the popup.  No difference between the two, F1 or RXP.

Of interest is that with the RXP GTN 750, in the virtual cockpit, if you zoom in and try the Home or D-> buttons you can see them move in and pop back out. They just do not function other than those movements.  Would think there would be a fix for that.

The screenshot below is an earlier one and shows the F1, but the size and perspective is the same.

http://