RFN v5.2 gauge (adding to non RFN aircraft)

[YoYo]

Hi,
firstly Id like thank you for this great gauge and next update.

Id like to ask you about procedures to add to non RFN airplane. For Crusader it works perfect for me. Now Im testing RFN v5.2 in Dino's A-4E Skyhawk and I noticed that glide slope doesnt work. Maybe I miss something?

I added to panel.cfg this:

Window01=RFN Tacan Indicator with the rest for sure, in VC section (yes, this model has gap between 20 and 90 number):

....
gauge00=Gauges!DisplayRadioFrequencies,0,0,512,512
gauge01=Gauges!SystemAutopilot,0,0
gauge02=Gauges!SystemAnalogAvionics,0,0
gauge03=Gauges!SystemAPC,0,0
gauge04=Gauges!SystemBDHI,0,0
gauge05=Gauges!SystemCanopy,0,0
gauge06=Gauges!SystemChaffFlares,0,0
gauge07=Gauges!SystemControlSurfaces,0,0
gauge08=Gauges!SystemElectrical,0,0
gauge09=Gauges!SystemEngine,0,0
gauge10=Gauges!SystemFuel,0,0
gauge11=Gauges!SystemIFF,0,0
gauge12=Gauges!SystemLights,0,0
gauge13=Gauges!SystemNavigation,0,0
gauge14=Gauges!SystemNWS,0,0
gauge16=Gauges!SystemRadio,0,0
gauge17=Gauges!SystemSMS,0,0
gauge18=Gauges!SystemTACAN,0,0
gauge19=Gauges!SystemTacpackAndSWSNavaids,0,0
gauge20=Gauges!SystemRadarService,0,0,0,0
//gauge20=IFE_A4_RDR!Sys,0,0,0,0 // New radar scope

//-------------Gauge Carrier Operations-------------------

gauge81=RFN_CarrierGauge64!TACAN_Navigation, 0, 0, 0, 0, Nav1
gauge82=RFN_CarrierGauge64!CustomCatapult, 0, 0,
gauge83=RFN_CarrierGauge64!Approach_Ctrl, 0, 0, 0, 0, 7.5

//--------------------------------------------------------

//gauge90=Sound/CustomSound_x86!Sound,0,0,0,0,.\SimObjects\Airplan es\A-4E\Panel\Sound\Sound.ini
gauge90=Sound/CustomSound_x64!Sound,0,0,0,0,.\SimObjects\Airplan es\A-4E\Panel\Sound\Sound.ini


gauge95=Config!AircraftInitialization,0,0
gauge96=Config!InitialSettings,0,0
gauge97=Config!Keystrokes,0,0
gauge98=FuelDumpx64!fuel_dump, 0,0,0,0
gauge99=Gauges!A4Tactical,0,0

In aircraft cfg:

Nav.1 = 1, 0, 0
Nav.2 = 1, 0, 0

tested too:

Nav.1 = 1, 0, 1
Nav.2 = 1, 0, 0

in orginal aircraft.cfg was:

Nav.1 = 1, 0, 1

and it works:



however, you can notice that glide slope (the biggest red box) doesnt work so no any approach datas.

If I swich after this to "normal" VOR it works:



2/ btw. pls to check how code of freq works in current version of RFN gauge: XXX.YY, if you swiitch the end (Y figure, bolded), near 30 to 20, the main, last, bolded X changes too. Looks like a bug for me. Example. 109.35, right knob to 25. it will look immediately like 110.25, not 109.25.

[YoYo]

Also - is it possible in the next version to do possibility to add FCLP "in the air"?
Now it needs always airport as background, without this its a problem (like putting it on static carriers or other parts of scenery) what is case of next problem - unexpected mesh on the water in some situations (what I see after some tests). Parts to hide in this situation could be hide deeper (30 meters will be very ok).

[fsafranek]

I think you are expecting it to do more than it is designed to do.
It works in the RFN Crusader because the aircraft was designed to work with the gauge, not the other way around. Same, IIRC, with the RFN Etendard IVM and IVP.
Dino's A-4's aren't integrated with the RFN gauge. But the gauge will work as a stand-alone with whatever you put it in.

2/ btw. pls to check how code of freq works in current version of RFN gauge: XXX.YY, if you swiitch the end (Y figure, bolded), near 30 to 20, the main, last, bolded X changes too. Looks like a bug for me. Example. 109.35, right knob to 25. it will look immediately like 110.25, not 109.25.

If I understand the question, see the note on the bottom of page 12 of the manual.

Hope this helps.

[YoYo]

I think you are expecting it to do more than it is designed to do.
It works in the RFN Crusader because the aircraft was designed to work with the gauge, not the other way around. Same, IIRC, with the RFN Etendard IVM and IVP.
Dino's A-4's aren't integrated with the RFN gauge. But the gauge will work as a stand-alone with whatever you put it in.

Thx, I thought glide slope indicator is some kind of standard and will always work like for the default frequency (ILS works here) and gauge only forces it to work.
So maybe I was wrong and in fact it still requires some changes in the panel by developer, pity.

About second, I see something like this:

For channels 17 to 19 and 121 to 126 select the whole units first and then the tens

I will double check again and back. TY!

[YoYo]

I think you are expecting it to do more than it is designed to do.
If I understand the question, see the note on the bottom of page 12 of the manual.

No it wasnt this, my freq on example was for channel 36 X and Y, looks like a small glitch with spontaneously skipping digits.

[YoYo]

To clarify (about this jump of digit):

It looks like intended effect because the TACAN digits are arranged sequentially but the VOR (for preview) digits are not always (two systems in one) and first you should look at TACAN.
Thx RFN Team!