December 2, 20178 yr Author 3 hours ago, jabloomf1230 said: It does have a facility for replacing the navaids names attached to a specific airport BGL file and that involves creating a file named <ICAO code>.xml. This process is documented in the manual and there is a sample file included. Thanks for the info ! Do you mean the Voxatc manual, I could not find anything related to an xml file. Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
December 2, 20178 yr 2 hours ago, mikealpha said: Thanks for the info ! Do you mean the Voxatc manual, I could not find anything related to an xml file. Mike The sample file EDDK.xml is located at: C:\Users\<username>d\AppData\Roaming\Internal Workings\VoxATC P3D 4\apdata <?xml version="1.0" encoding="utf-8" ?> <Airport ReplaceUnits="true"> <ATSUApproach Name="cologne" Frequency="121.05" /> <ATSUApproach Name="langen radar" Frequency="126.325" /> <ATSUTower Name="cologne" Frequency="124.975" /> <ATSUClearance Name="cologne" Frequency="121.85" /> <ATSUGround Name="cologne" Frequency="121.725" /> <ATIS Name="cologne" Frequency="119.025" /> </Airport> This is a shortcut around editing an airport file with ADE. Keep in mind it won't either add or modify approaches, navaids, etc., just the names and frequencies.
December 3, 20178 yr Author Ok ! I also found NameProcessor.xml in that folder, with a Langen radar entry. <NameProcessorItem Replacement="langen" Original="langen radar"/> I assume that's to avoid something like "Langen Radar Center" being said. Anyway, have to experiment with that and find out what has priority. I'm getting there, thanks to your help ! Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
December 3, 20178 yr Author Some more tests : Almost as expected, removing the above mentioned line in the NameProcesser.xml has just the effect Voxatc says "Langer Radar Center" now. FSAerodata has also COM frequencies included or corrected, e.g. Frankfurt Apron. A good thing, but Voxatc now says "Frankfurt Apron Ground". Putting just "Frankfurt Apron" in an EDDF.xml also doesn't change that. Seems there is no way to convince Voxatc to just say what is defined in the ATC callsign. It consequently adds it's own ground or center. Probably it's too much I'm expecting to get this correct, but just thought I mention it. Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
March 21, 20197 yr Hello everyone i have tried to contact them too with no luck , i don't know what they are doing but its bad customer service for what seems like a good product !
March 21, 20197 yr Wellcome to us 😂 i9 14900KF 64 Gb DDR5 @ 6 Ghz CAS 32 Asus Apex Z790 W11 64 bits pro sur Kingston FURY Renegade 2 To, MSFS 2024 sur 2 ème Kingston FURY Renegade 2 To, RTX 5090 Alim Asus Thor 1600 W Gold Ecran Samsung G9 57 pouces 8K WC AIO ARTIC liquid freezer II 420 Boitier Gigabyte 3d mars https://www.youtube.com/channel/UCEFAk464aSg22aGFZ2LxeFg/videos
Archived
This topic is now archived and is closed to further replies.