I am using Ideal Flight to create the flight. I loaded the IdealFlight.PLN file into the Sid Star Wizard and set up Lam4M as a SID and also a star at my destinattion. Now, whenever I create a flight, VoxATC always asks me to fly that SID regardless of what airport I am starting from. I have tried deleting the Ideal Flight.pln file and creating a brand new one but it always remembers that SID.

Is there a manual config file anywhere to remove the entry?

I haven't tried to fly a SID or STAR yet only because the airports I'm flying out of are Class E,D or C, and I normally get a proceed direct after departure instructions.

 

The only thing I can recommend is to follow the directions, for example. Pick a Class B airport. In the documentation I believe they are using Kansas City Int. airport. Also, I would try it with FSX flight planner. However, you're not able to pick a SID,one is assigned to you based upon wind direction (I'm sure you know that)

 

VOX has to be enabled after a flight plan is loaded and whatever cache it creates is deleted. Because I tried to start a new flight after I landed. i.e. disable VOX; alt-space to get menu create a new flight plan, enable VOX....did not work, I had to do this.

 

Disable VOX; semi colon (save flight); alt-space to get menu - create new flight plan; enable VOX. That clear any memory VOX was holding and was able to take off again...without having to exit FSX first.

 

Hope this helps.

 

-Ray

I was having the same issue, and although the manual says you just have to go into the SID / STAR editor and delete the name field entries, this didn't seem to work for me.

 

However, I believe VoxATC creates a file corresponding to an FSX flight (not flight plan) file in the location below

 

%appdata%\Internal Workings\VoxATC X\userprocs\<flight_name>.VOX

 

Deleting this file, I believe, resolves the issue.

I was having the same issue, and although the manual says you just have to go into the SID / STAR editor and delete the name field entries, this didn't seem to work for me.

 

However, I believe VoxATC creates a file corresponding to an FSX flight (not flight plan) file in the location below

 

%appdata%\Internal Workings\VoxATC X\userprocs\<flight_name>.VOX

 

Deleting this file, I believe, resolves the issue.

 

Nice find, can be useful for some situations.

 

Thanks for sharing.

 

Dirk.