JetBlack

I've investigated further since my last post. E45 is an atypical example. As I mentionned before Oakland center is also providing an approach service to this airfield. This dual function unsurprisingly is not understood by FSX/VoxATC. This issue wouldn't be a big deal but it highlights something really messy with VoxATC. Centers handoff management doesn't work properly (in not-expert mode at least) as long as the arrival airport is not fitted of approach frequencies. And most of small airfields have no departure/arrival service. In another vein, this also partially explains the bug of handoff from center to arrival airfields when the latter is equiped with unicom frequency only . If you want to get the right text on prompter you must disable/enable VoxATC before enterring the destination airfield area (5nm) you'll then be asked for an intial contact to the current center and so the procedure will be correct until the end of flight.

Unfortunately as instructive as it could be puzzle solving doesn't fix bugs... it just gives you a clue to bypass them. And at the end when you add up the whole time you spent for so few it's just frightening. Gardening is a more reliable hobby...😏

Ok, here is a part of the story... In real life Oakland center 121.25 provides aproach/departure services to E45. In FSX, (default bgl) E45 owns a center frequency (Oakland center 126.85) which seems confusing the Sim. I turned it into an approach type frequency (Note I've also changed frequency to the real one: 121.25). It doesn't crash anymore in VFR at now ! But it also means that other airfields of this area must be fitted with an aproach/dept frequency in order to avoid VoxATC crashing (maybe excepted those with no CTAF. I've not tested yet). Unfortunaley once under the approach service' control you can't access to any requests such as emergency or position/bearing. Handoff to approach is made 40nm from your destination so you must pray not to get any problems all along this distance...

BTW I've noted that handoff from the last center to E45'(virtual) approach is done at the same place where VFR flight crashes. I'm gonna add a real approach frequency on E45 and see what happens.

Well, IFR flight is OK, I mean it doesn't crash and executes handoff where it is supposed to do so. The last handoff is made to the destination UNICOM as if it was an approach frequency and provides standard approach options (by pressing 0). Of course trying these options has no effect on UNICOM controller but it doesn't crash the process. You just have to do the standard non towered procedures (without any help from the prompter as we already know).

Ok Mac I agree with you at 100% but... for most of us FSX pilots are not real life pilot. I think most of us want to get it as realistic as possible but at our own learning rythm (which is not necerraly possible in real life). VoxATC could be a great learning tool if all its "helpers" worked correctly. For virtual pilots these bugs make things more confusing than they are in reality. Nobody can't use VoxATC in expert mode from the start. Also think that things get hardest for non-english speaking people (at the first stages at least) without writting help.

Hi, No,I'm not using Navigraph data. Just the default stuff. I think it has something to do with ARTCC boundaries reading/processing. Is there any pre-existing data in VoxATC installation process or does it take all its data from FSX ?

Hi, Well spotted ! Using expert mode prevent VoxATC from crashing. However it still doesn't detect some centers' boundary crossing (mainly KZOA3232, KZOA3217, KZOA3219) unless you travel far deep into them. Anyway this is at leat "playable" in expert mode and that's a good news. I'm terribly afraid the developer's cadaver is rotting behind his desktop so better let him rest in peace. This bug will join the pile... Thanks a lot for your help.

Interesting but... I did remove centers' radio with ADE from KCPU, O22, E45 and even from O68 with same bad result at the same place. Well, will see what happen on your P3D system later. As you said previously it's maybe a specific bug to FSX-SE version.

Ok let's see. Thanks

Hi , Here is an illustration of my problem. This is a direct VFR flight between Lincoln (KHLM) and Pile Mountain Lake (E45). After leaving the airfield area( about 5 nm from the airfield) you are prompted to contact Oakland Center 119.75 which is fine but when you enter in Oakland Center 126.85 area nothing happens until you reach the position shown on the picture. There, are asked to contact Oakland Center 126.85 and the horrible fatal error message is displayed... Maybe someone could try the attached flightplan and tell me if the same thing happens ?😎 Flight Plan Thanks in advance.

Jay, I disabled all my 3rd party add-ons. No sucess. And even after a fresh reinstalling of FSX(SE) and then VoxATC I get the same disappointing result. VOXATC is unable to perform any handover between centers.

Hi, No I'm not using fsAerodata. Actually VoxATC seems not to read correctly data from bvcf.bgl. However the latter looks right in LittleNavMap or PlanG... Some suggestions ?

Hi All, A quite long time after crossing ARTCC boundary VoxATC suddenly awakes and realises I'm in another ARTCC area so it asks me to switch to the current ARTCC frequency and then displays the famous "FATAL ERROR" message and finally it crashes. If I disable/reenable it then it reworks properly untill to a next ARTCC change. Is that a know problem?

Ah! OK, so just another disappointment...😒 Thanks