HiI would like to see VoxATC merge with flightplans developed in FSBuild2 without errors in vectoring to waypoints not on the flightplan.Great Job Team! This is a "Must Have" add-on!Chip B.

Hi Chip,Take a look at response #10 in topic #281 (Controller Suddenly Stops Talking) for a zipped file with two flightplans, one stock from FSBuild2 and one modified to fit FS2004 constructs. VoxATC is reading flightplans properly, it is FSBuild2 that needs to add an option for constructing its flightplans to conform to FS2004 standards.Zane

Hi ZaneI've posted on the FSBuild forum with an example of each entry. Hopefully they will be able to do something.Thanks!Chip

Hi Chip,As stated in another thread I stand corrected. VoxATC will work with a FSBuild2 generated flightplan... I just verified this on my system. I think the problem comes in with the user enabling VoxATC after they have loaded the flightplan (even after saving the situation with this flightplan). There is still a step that needs to be taken to ensure the program works without a hitch. Load up the newly saved situation that has the attached flightplan, then enable VoxATC. Let us know if after using this procedure you are still having difficulty.Zane

Hi Zane,I'll get to that tonight and let you know.I did hear from the developer of FSBuild, and he states:The former format used is accepted by both FS2002, and FS2004, that is the reason it is used in Fsbuild. The latter format is only accepted by FS2004. The latter format was the one you had modified. This explains why it formats the way it does.I'll get back to you on the extra step.Chip