Now available on RFN site.
Now available on RFN site.
Scroll to bottom of the page.
Frank Safranek - Alphasim/Virtavia Paint Crew
Very interesting..... love the new gauge. Is it possible to get a IFLOLS or an animated LSO functioning on a moving carrier?
crashAZ- Virtual Navy
Particularly if you build it into the carrier model.
Someone has to have the answer.
crashAZ- Virtual Navy
SkyppiBing is perfectly right: her HMS Victorious integrate Tacan/ILS variables to animate a 3D batman!!
I worked all this last summer in adapting my Clemenceau's miror with this brillant idea: the challenge was, to my point of view, to find a way to improve the visibility of the signal...
I moved to something else before releasing it, but if I find time I'll try to package it and share the result with you...
Anyway, the goal of this small gauge was to allow to add to any aircraft a tacan feature that can work with any list of carriers of your choice (and even with fixed geographical coordinates) thanks to a xml file of parameters. It's the system used by EtendardIVM and Zephyr packaged as a stand alone gauge.
This 2D gauge is done in xml so any airplane creator could look at the variables I used and integrate it in their 3D gauges if they want: feel free to ask me!
Last, with this gauge, you have also a LSO voice simulation during final approach using the standard Acceleration sound file.
At the RFN team, we're looking for recording more realistic sounds for a French navy point of view but I'm sure that one could create a better US Navy and/or RN sound sets?
Sylvain wrote "any list of carriers".
My list of carriers is longer than tcn gauge one.
I may say Mistral, Bonhomme...
Any chance to add them?
In carrier.xml i saw the name of the carrier does not fit with its title in sim.cfg.
Where it comes from?
You can add in Carrier.xml any "carrier" of your choice but... (there's always a "but")
...but not any ship.
The brillant code, wrote by Neutrino (how grateful I am!! Thank you again!!), that I use in my gauge is abble to identify "Carriers" as they are AI objects with 1 catapult at a minimum.
So in order to have the gauge to "catch" a specific ship, check that 1 (or more) catapult is defined into the model whatever it is used... I didn't try to add dummy catapult attachpoints into a ship model but it should work...
For the name used in Carrier.xml , it comes from nowhere... It helps fro reading/managing the file, but as L:Variable don't manage string value the carrier's name is loeaded in the dll but not forward to the xml gauge... I read some interesting way to manage string value from C++ to xml but I don't have time to try it... So, at this point it is a unused field...
Thanks to you Sylvain and Neutrino for this excellent little gauge. It's made our carrier op's much better...
The code in the xml is so easy to replicate that even I managed to make a FCLP zone at a remote field that a few buddies and I use. Also got your gauge working in the 'Sludge' Hornet by merging the .ini file as you suggest.
Best regards and keep up the great work,
A dummy lil tutorial on how to?
I assume you already have your FCLP wire / wires scenery set up and that you have some experience with FSX Coordinates and simple editiing of .xml files.
To determine the exact 'lat' - 'lon' position in FSX and the Runway angle, I recommend using the TCalcX tool - available HERE
The COP3 gauge set made by Rob Barendregt combined with a set of Crosshairs [search Avsim or Fsim.com] work just fine too.
First, BACKUP the file 'Carrier.xml' found in your FSX\Gauges folder.
Now, using Notepad, open the Carrier.xml file. Scroll to the bottom and you'll see this data:
Now, we want to copy, paste and edit this information to suit our FCLP wires. So, doing this we end up with:
Save the modified 'Carrier.xml'
I've put ficticious data above, but you can see the information you need to enter. All entries except the CarrierType and GS_Angle has been edited.
Carrier name - Your choice to match the Airfield / Runway
Frequency - Decide on a unique freq.
RunwayAngle - Get from your actual runway
Lat, Lon and Alt - Get from your FCLP wires scenery using TCalcX
Looking at the original 'Carrier.xml' file, I compared the 'Nimes' data to the actual scenery in FSX and found a slight offset. I hope the picture explains... I don't know how precise the Landing Point / Crash Point has to be, but I found that the LSO is quite happy! I can imagine that the 'Alt' - Runway altitude may need tweaking so the LSO doesn't give a 'Wave off' signal.
Hope this helps - if I can clarify anything then let me know
To successfully add the RFN TACAN gauge to the Sludge Hornet, I merged the 'dsd_sonsRFN.ini' with the Sludge 'Panel_Sounds.ini' files and omitted the 'gauge74' line from the panel.cfg as described by Sylvain in his Readme.
So, I end up with a modified 'Panel_Sounds.ini' file [found in the Sludge Hornet Panel\Sounds folder] that looks like this:
Sound00=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/bingo.wav, 100
Sound01=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/altitude.wav, 100
Sound02=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/roll_out.wav, 100
Sound03=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/power.wav, 100
Sound04=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/fuel_low.wav, 100
Sound05=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/check_gear.wav, 100
Sound06=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/pull_up.wav, 100
Sound07=./SimObjects/Airplanes/Rogues Navy FA-18 FSX/Panel/Sounds/RALT_Tone.wav, 100
Again - hope the information helps. Please let me know how you manage...
But I wrote DUMMY!
Ok now i've something to do in the next hours/days.
When at home i'll have a look at the programs and start working on it.
For now i wonder why do we have lat long coordinates when applying to moving carriers. Most of the time (Bob Dylan's words, btw i'm going to have a nice next wednesday in Padova concert togeter with Mark Knopfler and i'm yet in the right mood) i use AI moving carriers.
The AI carriers don't have lat & long coordinates Roberto, just data for the ILS and TCN etc. I really don't know how these numbers apply, but I guess we can see they're relevant to the carrier model... I use AIBTC and a kml file made in Google Earth [well, my buddy Guy does all the AI boat traffic planning etc. for a group of our friends].
Hope you enjoy the concert! One of my first CD's [wow they seem so old now] was Brothers in Arms. Excellent
to complete what has been said the coordinates entered is the point you want your plane's ref point be when touch down. Regarding altitude, it should be the ground altitude.
Regarding Carrier's parameters:
Note: for the gauge, a "Carrier" is a AI model that contents 1 or more catapult...
- Name="Foch_1975" => free name (unused)
- CarrierType="1" => 1 for carrier / 2 for FCLP zone
- Frequency="109.00" => free but unique frequency
- Radius="148" => property of the carrier model calculated by FSX. You can found it thanks to FSX Explorer Traffic Tools
- RunwayAngle="8.5" => given by the model designer
- GS_Angle="3.6" => glide slope angle, usually dependant to the optical system used
- ILS_Xcoord="-1.574" =>offset (in meter) of the thouch down target point on the flight deck given from the carrier's xyz ref point : (x,y,z)=(right/left, alt, front/rear)
- TCN_Xcoord="15.187" =>offset (in meter) of the Tacan Beacon's location given from the carrier's xyz ref point : (x,y,z)=(right/left, alt, front/rear)
There are currently 1 users browsing this thread. (0 members and 1 guests)