Sound problem in Duke only with RXP?

[Dean33 69]

I have a problem using the RXP750 in the Realair Turbine Duke.

It loads with the F1 fine, but if I switch to the RXP750 (using the auto detection conversion) the aircraft restarts with the RXP and there is an electrical clicking noise in the aircraft that continues indefinitely. 

I thought it was a problem with the Turbine Duke but it is only there when I'm flying the RXP. 

I am sure it is not an RXP problem as that works great in my other aircraft but it seems to be causing this problem.

This clicking sound is even there in cold and dark!

Any suggestions would be appreciated.

 

Edited January 8, 2019 by RXP

[fppilot 4,337]

Can you post your entire [vcockpit01] contents from the panel.cfg file?  It will be rather long, so click on the eye icon to open the spoiler window and post it in that window. That eye icon is just to the right of the Font selector in the message editing tools area just above where you type your message.

[Dean33 69]

Having looked into this deeper I have found that there are other ways to make the Duke click!

Strangely it clicks with NO GPS, GNS500 and RXP 750 (replacing F1GTN750) BUT NOT F1GTN750 direct from TD configurator.  Wierd!

 

I'll try the Vcockpit01 content next. Thanks.

[Dean33 69]

Spoiler

[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=rxpGTN!GTN_750_1, 2,563,390,460
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

Here thanks Frank!

Dean

[fppilot 4,337]

Your gauge21= and mine look a bit different, but that may be due to how we each have FSX installed.  My FSX is located at c:\fsx.

Do you have a backup of your original panel.cfg to see how that gauge entry originally read?  It should not have been affected by the RXP install routines.

Try saving a backup copy of the panel.cfg file when you have the F1 GTN configured and then compare it to the panel.cfg file when you have the RXP installed, particularly looking at the gauge entries beginning with gauge19.  Note  that warning box that talks about the fact that gauges can be overwritten....  Also note that at least two and perhaps three of the gauges in that range are sound related.

 

 

[Dean33 69]

Thanks Frank

I've looked at all three variants and the Guage 21 remains identical.

I've switched all Sounds Off (Engines, Environment and Cabin and Voice) and yet the clicking is still there when the aircraft is in focus.

If I had to guess the sound is the same as the Avionics master switch repeatedly switching. But no animation.

Appreciate your efforts.

Dean

[fppilot 4,337]

Dean,
Post your RealityXP.GTN.ini file from the main Turbine Duke folder and let's look at it.

 

[Dean33 69]

Thanks I’ll post later. 

[Bert Pieke 7,584]

Just a guess.. could it be that the NAV/GPS switch and the GTN are fighting each other?

Edited January 6, 2019 by Bert Pieke

[Dean33 69]

5 hours ago, Bert Pieke said:

Just a guess.. could it be that the NAV/GPS switch and the GTN are fighting each other?

Thanks for the input Bert but I also get the sound when I have no GPS unit in the TD.

[Dean33 69]

7 hours ago, fppilot said:

Dean,
Post your RealityXP.GTN.ini file from the main Turbine Duke folder and let's look at it.

 

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) 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
; 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
; connects CDI key to NAV/GPS switch if true.
AutoNavGps = true 
; selects VLOC NAV '1' or '2'. '0' selects same source as 'RadiosPair'.
AutoNavSource = 0
; 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 = false
; 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 = false
; use legacy mouse (left CCW, right CW, middle Push) (override instances settings)
UseAltMouse = false
; 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 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
; 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: 104)
TawsApprSpeed = -1
; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 152)
TawsFlapSpeed = -1
; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 200)
TawsGearSpeed = -1
; 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
; 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
AFMS.cdi_key =  
; main: Selected Course for GPS
AFMS.sel_crs_gps =  
; main: Selected Course for VLOC
AFMS.sel_crs_vloc =  
; main: V-Flag State (1: declutter
AFMS.v_flag_declutter =  
; main: GPS Selected (0: prompt, 1: auto)
AFMS.gps_selected = 1
; main: Airspace Labels
AFMS.airspace_labels =  
; nav : Mark On Target
AFMS.mark_on_target =  
; nav : RF Procedure Legs
AFMS.rf_procedure_legs =  
; vnav: Vertical Navigation Type (0: VCALC, 1: VNAV)
AFMS.vnav_enabled =  
; vnav: Transition To Approach
AFMS.vnav_trans_to_appr =  
; vnav: VDI Scale (ft)
AFMS.vnav_vdi_scale_factor =  
; vnav: Transition Altitude (180 = 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
 

Here is the RXP.GTN.ini

 

Thanks 

[fppilot 4,337]

Do not see anything amiss there.  Is this the Turbine Duke? or is it the Turbine Duke v2? Not occurring with any other aircraft?  If no one else recognizes what may be the cause then you may wish to uninstall then reinstall the model, making sure to clean up any artifacts.

[RXP 2,336]

On 1/6/2019 at 5:39 PM, Dean33 said:

; connects CDI key to NAV/GPS switch if true.
AutoNavGps = true 

Like Bert suggested, tried at least setting this to false (whether in the ini file or via the Settings panel) just to make sure it is not a 'fight' between gauges.

Some developers trigger a sound upon an actual action on a switch, some others trigger a sound upon a change of value between 2 update cycles (event-based vs poll-based). Should the aircraft sound is programmed in 'poll' based fashion, anything making a change of value will trigger a sound even if you don't click it, hence, it is better to actually code one's aircraft to produce sounds upon situation you control...