Hi, has anyone here built a custom airport with a VOR, and successfully compiled it?
I am trying to add a VOR to a custom airport. Everything else is working, including the ILS, but when I try to add a VOR, the compiler keeps insisting that VOR’s need lat, lon, alt, ident, magvar, and frequency as the minimum input. Well, I have those inputs in place, plus the range. Here’s the text:
<Vor lat="-49.344174" lon="70.233187" alt="28.058497" ident="PAFV1" magvar="56.0000" frequency="108.400" range="80000.000">
<Dme lat="-49.344174" lon="70.233187" alt="28.058497" range="50000.0000"/>
</Vor>
The other question I have: is there a particular place this has to go in the XML file? I’ve tried putting it near the bottom, between Airport and FSData, and at the top, right after FSData version=“9.0”, with the rest of the scenery objects, and it doesn’t work anywhere, I keep getting the same compiler error.
So this leads to the question: Why isn’t VOR in the Scenery editor? The only radio nav aid that I have been able to find in the SDK Objects lists are ILS, which you can add to a runway. I have not been able to find VOR, or NDB. Is this just something that’s missing from the SDK that will be added in a later update?
1 Like
- Try to use this template:
< Vor lat="" lon="" alt="" type="" frequency="" range="" magvar="" region="" ident="" name="" dme=“TRUE” dmeOnly=“FALSE” >
< Dme lat="" lon="" alt="" range="" />
< /Vor>
VOR Type needed is: ‘LOW’, ‘HIGH’, ‘TERMINAL’ or ‘VOT’.
Region is 2-letter country code agreed by ISO.
- VOR data should be placed within FSData node but it can be outside your Airport.
2 Likes
Thanks! Your template worked - after I fixed a couple of other problems. It took a while, but I finally figured out what the SDK compiler was complaining about: the quote marks! Apparently, not all of the quote marks in my VOR data were coded as ASCII 0034, a few of them were Unicode characters 201D and 201F, which look like plaintext quote marks except with a curve to them. MS-Word uses these as default quote marks unless you tell it to stick to the ASCII character set. I’m using TextPad to edit my KML files, and I guess it allows Unicode characters. Anyway, I now know that the SDK compiler doesn’t like Unicode, so I will be on the lookout for this problem the next time I design custom scenery. Thank you for your quick reply!
1 Like
OK. With regard to XML files, my favorite tool is MS Notepad. It never let me down since the introduction of XML language in MS flight simulator.
Wish you good luck in implementing your baby project.
Hi, I can’t insert a VOR, I write it in the xml file after airport, but then in the REBUILD phase I find it deleted. Could you write the script with your VOR to be able to copy it? thanks a lot
POL
Hi, I can’t insert a VOR, I write it in the xml file after airport, but then in the REBUILD phase I find it deleted. Could you write the script with your VOR to be able to copy it? thanks a lot
POL
Hello
I read your post about adding VOR syntax
I placed some additional objects in an existing airport, no problem with objects, no problem with adding a runway, no problem about waypoints and ILS, but I fail adding a VOR
My syntax is as follow:
<Waypoint lon="3.74815000000000" lat="45.52329500000000" magvar="2.0" waypointType="VOR" waypointRegion="LF" waypointIdent="AMB"/>
<DeleteAirport deleteAllApproaches="TRUE" deleteAllApronLights="TRUE" deleteAllAprons="TRUE" deleteAllFrequencies="TRUE" deleteAllHelipads="TRUE" deleteAllRunways="TRUE" deleteAllStarts="TRUE" deleteAllTaxiways="TRUE" deleteAllBlastFences="TRUE" deleteAllBoundaryFences="TRUE" deleteAllJetways="TRUE" deleteAllControlTowers="TRUE" deleteAllDepartures="TRUE" deleteAllArrivals="TRUE" deleteAllPaintedElements="TRUE" deleteAllLightSupports="TRUE" deleteAllTaxiwaySigns="TRUE" deleteAllILSs="TRUE" deleteAllTerminalWaypoints="TRUE" deleteAllTerminalNDBs="TRUE"/>
</Airport>
<Vor lat="45.5322950000" lon="3.748150000" alt="562.9657" frequency= "117.55000" range="20000.000" magvar= "2.0" region="LF" ident="AMB" name="Poyet" dme="TRUE" dmeOnly="FALSE">
<Dme lat="45.5322950000" lon="3.748150000" alt="562.9657" range="20000.000"/>
and the compiler answers :
^
20000.000 />
? false returned by Command=BuildPackages Comment=Rebuild the packages whose name correspond to the given filter, and for the given project (default fs-project.xml) NbParam=2 Line=BuildPackages ac-ambert-modifie * “E:/Creation Scenes/ac-airport-LFHT-modif/AmbertModifie.xml” “E:/Creation Scenes/ac-airport-LFHT-modif” 1 1 0
[Packages] Package content mounted: ‘package://edition/ac-ambert-modifie’ @ ‘E:\Creation Scenes\ac-airport-LFHT-modif\Packages\ac-ambert-modifie’
[Packages] Package content unmounted: ‘package://edition/ac-ambert-modifie’ @ ‘E:\Creation Scenes\ac-airport-LFHT-modif\Packages\ac-ambert-modifie’
Error while parsing XML data from E:\Creation Scenes\ac-airport-LFHT-modif\PackageSources\scene\objects.xml
Failed to read E:\Creation Scenes\ac-airport-LFHT-modif\PackageSources\scene\objects.xml as XML
PackageBuilder | Building assets for the package ac-ambert-modifie…
PackageBuilder | Done, 4 asset groups registered.
PackageBuilder | Failed to spawn lister for asset group mascene (type BGL) (package: ac-ambert-modifie)
PackageBuilder | Finished, 4 skipped, 0 done and 1 failed, took 0s799ms.
PackageBuilder | Generating commands for package ac-ambert-modifie…
PackageBuilder | Generating package information (layout from disk) …
PackageBuilder | Preparing asset groups…
PackageBuilder | Preparing commands for asset group ContentInfo…
PackageBuilder | Preparing commands for asset group mascene…
PackageBuilder | Preparing commands for asset group monmodellib…
PackageBuilder | Reading E:\Creation Scenes\ac-airport-LFHT-modif\AmbertModifie.xml…
PackageBuilder | Ready, 4 commands added.
PackageBuilder | Reloading assets for the package ac-ambert-modifie…
PackageBuilder | Starting the build…
parser said : unexpected end of data
zHave you any idea of what could be wrong ?
the VOR deletes them in the xml, for now they cannot be inserted, old story