Has anyone successfully declared and performed one?  I tried tonight settings some predetermined failures.  I ran the "Mayday Mayday Mayda, Callsign, emergency and requested vectors to the nearest airport.  After having to repeat myself twice - the controller acknowledged the mayday and requested for me to state my intentions.  I wasn't 100% sure what to say next as I thought I stated them by requesting vectors.  I requested vectors again, and was just met with a last aircraft - say again.  It eventually went to FATAL ERROR.  I re-initialized, tried again and with the FO on this time, hoping the FO would reply correctly, however Vox would never acknowledge my mayday and only ask to repeat.  Did I skip a step or something?

By accident, I checked this out today, since I was testing out REX Sky Force with the RealAirTD and experienced a port engine failure. The VOXATC emergency procedures do work correctly. What I would try is to first use First Officer mode. Then use the "0" key to open the menu and then hit "4" to have your FO for call an emergency. Let the FO handle the comms with ATC. See if that works for you.

On 1/2/2018 at 11:12 PM, jabloomf1230 said:

By accident, I checked this out today, since I was testing out REX Sky Force with the RealAirTD and experienced a port engine failure. The VOXATC emergency procedures do work correctly. What I would try is to first use First Officer mode. Then use the "0" key to open the menu and then hit "4" to have your FO for call an emergency. Let the FO handle the comms with ATC. See if that works for you.

Ill give that a shot - funny enough I saw your post in the other thread about SF and you mentioned the engine failure and declaring an emergency with vox - I was meaning to PM you lol!  I'll give that a try.  I was in the FSL A320 and undercalculated my fuel.  I tried the emergency function but it did all sorts of weird stuff.  Luckily I had enough fueld to reach my destination.  Although since I was close to the destination airport maybe that is why it didn't work properly?

If all else fails, uninstall VOXATC and reinstall it. Make sure that you also delete its hidden subfolder in your user roaming appdata folder. 

Generally speaking my approach for attacking VOXATC errors is to first check the departure and destination airport ADE files and that includes hunting down duplicate 3rd party versions. Next would be to try a default aircraft. Then try a simple direct GPS IFR flight plan. Lastly, an uninstall reinstall is an option, but that is hardly ever warranted. If none of that works then bundle up the log files, ship them to the developer and pray.

11 hours ago, jabloomf1230 said:

If all else fails, uninstall VOXATC and reinstall it. Make sure that you also delete its hidden subfolder in your user roaming appdata folder. 

Generally speaking my approach for attacking VOXATC errors is to first check the departure and destination airport ADE files and that includes hunting down duplicate 3rd party versions. Next would be to try a default aircraft. Then try a simple direct GPS IFR flight plan. Lastly, an uninstall reinstall is an option, but that is hardly ever warranted. If none of that works then bundle up the log files, ship them to the developer and pray.

The emergency thing wasnt that big a deal to me although would have been cool to run through.  I shipped logs and an email to the dev for the fatal error you were helping with...well see how that goes.  So far no response.