Hello all,May I suggest something to the devs (it is relevant only to users flying in Europe where trans levels differ from place to place signifiacantly).Since, VoxATC does use the concept of regional transition altitudes (in %appdata%\Internal Workings\VoxATC X\VASettings.xml) then it might be possible to expose through flight planner extra three text boxes to let the user insert the transition altitude for the departure, destination and alternate. Three separate Regional sections could be formed inside the xml for each place (differing in the TransitionAltitude attribute, being identical to UK/EU otherwise). The boundaries of these sections could be calculated based on the airport coordinates and a 40nm radius for instance or something similar. Further customization of the regional features could also be added if needed in the future. This would add to realism significantly (for instance when I fly LGTS-LGAV, the transAlt in LGTS is 6000ft and 9000ft in LGAV). Thanks, KostasPS: Don't forget to add a MSA in the future (though I know this requires some extra coding)

Hi Kostas,Transition Altitude values that differ from airport to airport are relevant in other areas of the world as well - not only Europe. :( I also hope that a future version of VoxATC could handle such differing values even without user input.Real-world MSA values would be much more difficult to track and maintain - requiring not just coding but considerable data accumulation. Other similar (almost as relevant) values such as MOCA and MEF can be derived from standard DEM data.(AAMOF, a still-in-testing version of AivlaSoft's Electronic Flight Bag includes Transition Altitude for individual airports as well as MOCA/MEF values. Also, a still-in-testing version of FS Captain handles Transition Altitudes for individual airports as well.)Regards,

Hi Kostas,Transition Altitude values that differ from airport to airport are relevant in other areas of the world as well - not only Europe. :(

You're right, getting fixated from time to time :-)

I also hope that a future version of VoxATC could handle such differing values even without user input.Real-world MSA values would be much more difficult to track and maintain - requiring not just coding but considerable data accumulation. Other similar (almost as relevant) values such as MOCA and MEF can be derived from standard DEM data.(AAMOF, a still-in-testing version of AivlaSoft's Electronic Flight Bag includes Transition Altitude for individual airports as well as MOCA/MEF values. Also, a still-in-testing version of FS Captain handles Transition Altitudes for individual airports as well.)Regards,

I know this would be fantastic, it seems a lot of work from the developer perspective though. I just suggested a quick and easy way of programming this(so that would get this sooner :-) )