November 3, 20196 yr Hello Everyone I need help with that issue. I ran VoxATC on Prepar3D V4 PC all FIR Agencies are in correct handover, but when i run it over network it work with me except the FIR handover is not correct it switch me to Oceanic Center instead of the FIR i am flying over. any idea to fix it is there any contact with VoxATC publisher i am trying to contact him no response. anyone have idea for future update? many thanks best regards Edited November 3, 20196 yr by Jellybaby
November 3, 20196 yr 4 hours ago, Jellybaby said: anyone have idea for future update? not me ...... just fixes to repair what does not perform in V7 as it did in V6, particularly in the arrival phase (weather / assignments) updates if there are to be any can wait. to your question on ARTCC's, there should not be a difference but might be if the indexer import is not complete / corrupt (but then again, i prefer vox on server, so just guessing). for now, cheers john martin
November 13, 20196 yr This happens if your aircraft enters a region for which Vox ATC doesn't find a matching FIR entry in its bglcenters.dat file. It then defaults to "Anchorage Oceanic Center". If you use fsaerodata by any chance, the problem is that they use incomplete and inaccurate FIR boundaries (which default FSX does at well) and still haven't fixed this (although it's payware!). My workaround was to define my own FIR regions with correct frequencies over the whole world which is, of course, a lot of tedious work. I did it gradually, flight by flight during the last year and by now I have about 90% of the global FIR's covered. I wrote my own little program to match the bglcenters.dat structure, and used a combination of Google earth and internet resources to define the FIR polygons to match the FIR boundaries correctly. I can confirm that after indexing VoxATC uses my FIRData correctly. draci
November 14, 20196 yr 13 hours ago, bmaik said: I did it gradually, flight by flight draci me too as best i can find the details on sectors borders & frequencies within an FIR (but mostly asian skies to date). i found a few glitches in those borders & frequencies of fsad's update of the stock bcvf,bgl file which i "correct" (decompile/edit xml/recompile) including in some instance the sectors name (eg hongkong radar) always thought vox indexer reads & uses this file & saw/see no use of the bglcenters.dat's. good to hear another is keen to use vox's "potential / classy" features ...... we just need to find which bush TW is hiding under (hopefully fit for a few fixes & upgrades) for now, cheers john martin
Archived
This topic is now archived and is closed to further replies.