I see that there are some airports (EGGP Liverpool) for example where VOX doesn't handle the airspace correctly and simply sends you on your way after takeoff without routing you under control out through the CTR. The developer said about a year ago he'd look to fix it but I've not seen anything yet...? Have I missed anything?

 

Also, one particularly good feature for VFR pilots is that airfields can have specific customised VRP's (I think VOX ships with one for EGGD Bristol) but they are done through DLLs, something which the average person can't mess with. It would be a much more attractive solution if the developer would implement a solution where users could themselves create XML scripts to create customised VRP's for airports, then we would be able to get accurate and quick solutions rather than having to wait for the developer to get round to it.. Is there any chance this could be looked at please?

 

I see a huge amount of potential in developing VOX further for VFR but sadly little appetite to realise it properly yet :(

 

Another great idea would be if you create a flight plan, if VOX could check for VATSIM controllers, and then fill in the gaps, sort of automatically defaulting to online where it exists.. ?

 

Cheers k

Great post. I agree 100%.

In respect of the airspace handling I've looked to see if this was due to incorrect airspace classification in FSX/P3D. Decompiling the default data bgl shows that EGGP Liverpool has a class D CTR from surface to 2500ft, which (apart from a minor geographical error) is still correct according to the current UK AIP. Vox should recognise this and provide proper approach control theough the CTR out into uncontrolled airspace but for some reason doesnt. I've shot anothe email to Tegwyn the dev....