I'm having a slight issue with this gauge in that when I use either method of getting it to display, all that happens is that it briefly appears on screen (for <1 second) and then disappears. I've tried it in the Buccaneer, Goshawk, and the RFN Alize as that comes with the gauge entries already made so it should eliminate any errors on my part!
Any ideas what's going on?
Hi Skippy,Originally Posted by SkippyBing
The more current cause for " a disappearing window" are:
- A pb into the Panel.cfg => Do you use 64bit panel entries (I did some changes in the P3D V4 version)?
- C++ pre requires with MS VC++ redistrib 2013 x64
Regards,
Sylvain
Hi Sylvain,
I copied all the panel entries from the read me so I think they should be fine?
I reinstalled the VC+ redistrib as well, which took a while!
Still no joy though, I'll try fiddling, I've had it before on my own panels so I should be able to figure it out eventually!
Regards,
Skippy
Edited to add:
Ha, so the content error logging helpfully pointed out I was using the 32bit dll! Obviously clicked the wrong download link and then never noticed I'd got the wrong version. Apologies for the confusion.
I love carriers and I love VR. I was wondering if anyone knows of a way to use the RFN Gauge in VR (other than using FlyInside)? If not, would Sylvain et al consider an update to make this possible please?
i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2
Is there a way to change the default frequency (currently tuned to USS Enterprise) so it starts with another carrier of our choice each time?
i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2
I wasn't aware there was a default frequency. But if it can be set it will probably be discussed beginning on page 22 of the RFN Gauge manual.
Did some digging into the xml files included with the gauge and there is nothing in there to define the initial frequency.
So did some testing in the game. Thought it might be based on the order of the vessels in the carrier.xml file cross referenced to what you have installed but that isn't it.
So not sure.
Hi Airtrooper
Try this:
When you begin the flight, turn the frequency on your desired channel (NAV2 if RFN Gauge is setted on NAV2).
Then save this flight as default flight.
Next time you will start, you will be on the new frequency.
Let we know the result?
Regards
Michel
Last edited by mpni; May 9th, 2020 at 07:05.
Sylvain and I emailed back and forth about the frequency. His findings:
It would appear that the P3D default flight has tuned Nav2 frequency on 110.60Mhz which is one of the CVN-65 frequencies.
So any time you load a plane using this default flight you'll have Nav2 tuned on 110.60. If you load another saved flight with a different Nav2 freq, P3D will keep this last one.
The RFN gauge is not changing Nav freq when loading a flight.
I looks weird because default F22 plane shows Nav1 so we have the feeling that RFN gauge modify the freq to tune 110.6Mhz when after having loaded Crusader,
but RFN gauge in the Crusader is mapped with Nav2 and not Nav1 : no freq change just different Nav shown up![/QUOTE]
P3D v5 has kept that same 113.7Mhz for Nav1 and 110.6Mhz for Nav2 when the default F-35 is loaded. If unchanged any follow-on aircraft will use the same frequencies for their starting radio frequencies.
So, as Michel suggested above, maybe change your default startup aircraft and the frequencies it is tuned to and save it as a new startup scenario?
That explains it!
Many thanks!
Andy
i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2
Another way is using the "Previous Flight.fxml" file.
Go to ":\Documents\Prepar3D v4 Files" and make a backup of the "previous Flight.fxml" file.
Then look for
<Section Name="Avionics.0">
and modify the frequency in the line
<Property Name="Nav2Active" Value="110.60" />
Save the file in the same format (UTF-8-BOM for example)
Hi loomy
Unabled to send a private message because your mailbox is full.
Regards.
Michel
Hi Michel,
Thanks for answering my help request. No I am a member+ and can use all tools.
Would you spend some time to exchange some thought of why the ILS signal is not working in my T-45 Goshawk from Dino during an ILS approach on Navier's carriers? That is really giving me a headache.
I am using P3D v4.5 HF3 on Win 10. I reinsatalled my FS yesterday and just now installe the T-45 and the carriers from USS_Nimitz_USS_Eisenhower_v2.zip. According to what I heard, the ILS should work without having Tackpac installed.
Thanks for your reply and stay healthy.
Achim
Seeing this thread reminds me that I've got a bizarre issue with the RFN TACAN v5.00 gauge.
I installed it (Classic view of course ... lol.) into a number of aircraft, and it by and large works fine - TACAN/ILS needles lock on, DME indicates range correctly, etc.
But what is odd is that no LSO sounds are present on any aircraft - except for the Dino TA-4J Skyhawk. Very strange. I get all the callouts when flying that aircraft, but no callouts when I fly any other aircraft that I have installed the TACAN gauge into. That includes the Dino F-14, the Razbam A-7, Razbam T-2, and the RFN F-8, which already had the gauge installed. Am flying P3Dv4.5.
If someone has any ideas, I would love to hear them.
Kind regards, and many thanks in advance.
dl
EDIT - also added it to the FSXBA F/A-18C, and I get the proper sounds. Nothing with the others. Same entries, except for the specific sequence of the windows and gauges as required.
Hi Delta_Lima
1) Could you confirm that the "RFN_Sounds" folder is in the same directory and at the same level as RFN_Resources?
These folders must be at the same place as RFN_carriergauge64.dll
2) If it is OK, try to heard some waw file in RFN_Sounds by double clicking on (US_CallTheball.wav,...).
3) In the RFN_Carrier.xml, have a look on each Carrier or FCLP, at this line Language="FR" or Language="US"
4) All sounds files are called by the section <SoundFileList> in RFN_Parameters.xml file.
Regards
Michel
Hi Michel - thanks for the reply.
1) yes - both those folders are in my gauges folder, at the same level, and it's the same location for the at 64bit dll
2) I've sampled all the .wav files - they're all working. As I mentioned, on two of the aircraft where I have the gauges added, all the callout sounds are working fine.
3) All carriers and FCLPs have a Language entry of either FR or US.
4) Not sure what you mean, but I believe they are all called out, as shown here: this is the full contents of the RFN_Parameters.xml file:
<?xml version="1.0" standalone="no" ?>
<!-- RFN_Parameters.xml file for RFN Carrier Gauge V4.20 -->
<!-- by S.Parouty --- Royale French Navy - July 2015 09-03-2018 -->
<Parameters>
<!-- Define keyboard shortcuts managed by the gauge -->
<!-- By Default ToggleInput="Shift+Ctrl+Z", RefuelInput="Shift+Ctrl+A" and GoToInput="Ctrl+F1" -->
<Keyboard_Commands
ToggleInput="Shift+Ctrl+Z"
RefuelInput="Shift+Ctrl+A"
GoToInput="Ctrl+F1"/>
<!-- Define Wave Off properties -->
<!-- Distance of Wave Off check : in NM (by default 0.2NM) -->
<!-- Glide Slope thresholds : by default : +3.0° max and -1.65° min) -->
<!-- LOC thresholds : by default +1.8°max and -1.8°min -->
<!-- WaveOff duration : by default 5 seconds -->
<WaveOff
Dist_Check_WaveOff="0.20"
GS_Error_Max="3.0"
GS_Error_Min="-1.65"
LOC_Error_Max="1.8"
LOC_Error_Min="-1.8"
WO_Duration="5.0"/>
<!-- Define Meatball movement properties -->
<!-- Distance of activation : in NM (by default 2.0NM)-->
<!-- Amplitude : max/min of GS error (by default : +/-3.0°) -->
<!-- Sensibilty : Meatball % = (Coef*GS Error)^Meatball_Power (by default : 0.5 a square root law) -->
<!-- Duration of the Engine light (by default : 1.0 sec) -->
<Meatball
Dist_Activation="2.0"
Meatball_GS_Max="0.75"
Meatball_GS_Min="-0.75"
Meatball_Power="1.0"
PowerLight_Duration="2.0"/>
<!-- Define Catapult parameters -->
<!-- Speed Margin: speed margin above calculated End Speed (by default : 10 knots) -->
<!-- Catapult Lenght: average lenght of catapult (by default : 70 meters) -->
<!-- Catapult sound file: define the sound name and path relatively to the Gauges folder (by default : ./Sound/CatapultLaunch.wav) -->
<!-- CLaunch delay : define the time delay (in sec) between the request and the launch (by default : 3.5 seconds) -->
<!-- Engine Percent: define the RPM threshold for each type of Engine (by default, Prop:40%, Jet:70%, Turboprop:60% ) -->
<!-- Input that command launch (by default : button 0 of the 1rst defined joystick : joystick:0:button:0) -->
<Catapult
Speed_Margin="10.0"
Catapult_Lenght="70.0"
Catapult_sound_file="CatapultLaunch.wav"
Launch_Delay="3.5"
Engine_Prop_Percent="40"
Engine_Jet_Percent="70"
Engine_Turbo_Percent="60"
Engine_Other_Percent="0"
Launch_Input="joystick:0:button:0"
Steam_Model_32="VEH_Catapult_Steam"
Steam_Effect_64="fx_RFN_Catapult_Steam"/>
<!-- Define distance for each Check to be done (in MN) -->
<LSO_Distance_Check
Check_CallBall="0.90"
Check_Altitude_1="0.80"
Check_LOC_1="0.70"
Check_Altitude_2="0.60"
Check_LOC_2="0.50"
Check_Altitude_3="0.40"
Check_LOC_3="0.30"/>
<!-- Define Thresholds angles (in degrees) -->
<LSO_Thresholds
TooHigh_Angle="1.0"
TooLow_Angle="-0.5"
LOC_Angle="1.5"/>
<!-- Define Long Range Lineup properties -->
<!-- Distances are in nmiles -->
<LR_LineUp
Distance_Max="10.0"
Distance_Min="0.55"
Insert_Dist="0.50"/>
</Parameters>
<!-- Sound File Lists -->
<SoundFileList>
<SoundFiles Language="FR"
Wire1="FR_BrinNumero1.wav"
Wire1_msg="Brin numéro 1!"
Wire2="FR_BrinNumero2.wav"
Wire2_msg="Brin numéro 2!"
Wire3="FR_BrinNumero3.wav"
Wire3_msg="Brin numéro 3!"
Wire4="FR_BrinNumero4.wav"
Wire4_msg="Brin numéro 4!"
TooHigh="FR_TropHaut.wav"
TooHigh_msg="Trop haut!"
TooLow="FR_TropBas.wav"
TooLow_msg="Trop bas!"
LineUp="FR_Alignement.wav"
LineUp_msg="Alignement!"
CallBall="FR_AnnonceMirroir.wav"
CallBall_msg="Annonce miroir!"
WaveOff="FR_WaveOffWaveOff.wav"
WaveOff_msg="Wave Off! Wave Off!"/>
<SoundFiles Language="US"
Wire1="US_TrapOneWire.wav"
Wire1_msg="Wire number 1!"
Wire2="US_TrapTwoWire.wav"
Wire2_msg="Wire number 2!"
Wire3="US_TrapThreeWire.wav"
Wire3_msg="Wire number 3!"
Wire4="US_TrapFourWire.wav"
Wire4_msg="Wire number 4!"
TooHigh="US_YoureHigh.wav"
TooHigh_msg="Too high!"
TooLow="US_YoureLow.wav"
TooLow_msg="Too low!"
LineUp="US_YoureDrifting.wav"
LineUp_msg="Line up!"
CallBall="US_CallTheBall.wav"
CallBall_msg="Call the ball!"
WaveOff="US_WaveOffRepeat.wav"
WaveOff_msg="Wave Off! Wave Off!"/>
</SoundFileList>
Last edited by delta_lima; February 5th, 2021 at 08:01. Reason: added missing info
PS - should add I'm running P3Dv4.5, W7. Yeah, go ahead and laugh ...
Just in case that matters.
dl
All seems OK.
So have a look to the Requirements :
- Redistribuable Microsoft Visual C++ x86 or x64 as system specification
- Microsoft.NET Framework
- Microsoft Flight Simulator SimConnect Client which is installed with the simulator.
Are the msi simconnect installed?
You will find they here:
:\Lockheed Martin\Prepar3D v4\redist\Interface (ESPv1, FSX-RTM, FSX-SP1)
Regards
Michel
Hi Michel,
So yes and no. Those were installed in my default install - here: C:\P3DV4\redist\Interface. I have 6 folders there - the 3 you mention, plus 3 more (FSX-RTM-JPN, FSX-SP1-RUS, and FSX-SP2-XPACK).
My addons normally get added here: C:\Users\ME\Documents\Prepar3D v4 Add-ons
Thanks,
Daniel
Not necessary installing Japan, Russian and Xpack.
Fair enough, it’s where it was all installed by default, though I mentioned only to aid in troubleshooting.
More importantly, though, is that not where those folders should be located?
You can open your control panel and see at the program list if Microsoft Flight Simulator SimConnect Client and Microsoft ESP SimConnect Client are present.
Confirmed.
ESP client v1.0.0.20.0
SimConnect clients v10.0.61259.0, v10.0.60905.0, v10.0.61242.0
C++ redistributable v14.28.29325
dl
All seems OK too
"...But what is odd is that no LSO sounds are present on any aircraft - except for the Dino TA-4J Skyhawk..."
Could you confirm that the sounds you heard are sounds which they are in \Gauges\RFN_Sounds?
Do you have the right version of vLSO installed? There were errors, so it's been rolled back - see here.
Dave
Members who have read this thread: 0
Posting Permissions
Reply With Quote
Bookmarks