As per the title really, is the addition of SIDs/STARs automatic or do i still have to manually add them to the flight plan loaded in to FSX??Reason i ask is that i was doing a flight out of Bristol (EGGD), expecting runway 9 with SID EXMO1Z (programmed in to my FP), but by the time i got in to the game from flight planning i was taking off from rwy 27 but VOX automatically I believe assigned me the correct SID of EXMO1X. Is it really clever enough to do this or was i imagining it? Also if i dont add a SID will VOX assign me one?Same question with STARS. on same flight to Jersey i hadnt programmed a STAR, but it told me to follow the JERS1G (i think it was) STAR?So do i need to add SID/STAR to my FP if i want them, or will VOX do it automatically??Thanks in advance

On the text basis, the manual explains it the best.

Flight Planning and SIDs and STARsTo be assigned a SID or STAR, your flight plan must have some waypoints that correspond with waypoints in the SIDs at your departure airport and/or STARs at your destination. The assigned procedure may vary depending upon the runway in use.

So if we take your example Bristol (EGGD) and you are planning to depart to the West, you should chose the BCN VOR or the EXMOR intersection as waypoints in your flightplan. Those two waypoints are the ones which are covered by the westbound SIDs. So the plan would read EGGD as departure airport and then BCN for example. Thereafter your enroute waypoints will follow.If you would approach EGGD from the West to land there, the STU VOR would be the waypoint to look for. So the plan looks like enroute waypoints, STU and EGGD as arrival airport.So if you chose the waypoints which end SIDs or start STARs, VoxATC will most likely use the Navigraph data provided from the initial setup (Level D format) and assign a procedure for you. Waypoints between those initial ones aren't needed and avoiding them gives VoxATC the maximum flexibility for assigning procedures in my eyes.As for your Jersey (EGJJ) arrival, it seems like one of the waypoints from that STAR was in your flight plan. I expect the initial one, SAS VOR, to have been the trigger there.Those screenshots were taken from Aivlasoft's Electronic Flight Bag which is pretty neat for getting an overview and later on some details, but the normal charts should read those initial waypoints too. Just build your flight plans around them and you should always get some SID/STAR assignments.

CoolIPThanks very much for that. I apologise as i was being a bit lazt last night. I had just done a flight, it was time to go to bed, and rather than take the time to read the user guide for VOX, i posted a question.On having read your reply, and looked at the manual, as you say, VOX will generate a SID/STAR if one of the waypoints is on your FP. That explains why on my flight out of heathrow last night to Shannon, with an FP that when straight to CPT, CPT i presume isnt a waypoint on a SID, and that why i wasnt assigned one. Good to know that i can through a SSID into the FP, and regardless of the weather and runway, VOX will give me a SID to fly.Thanks

No problem with you asking questions in forums, parxuk. :( Those questions make forums a valuable source of information I hope. And even if the information one gets is "I should read the manual too", it has quite some value in my eyes.Here's one for you. I wonder what you mean with this sentence.

Good to know that i can through a SSID into the FP, and regardless of the weather and runway, VOX will give me a SID to fly.

I've marked the phrase which puzzles me. The SID or STAR will always depend on the active runway (which is defined by the current weather conditions). So the VoxATC assignment will most likely look for the active runway and then (after this first step) look for a SID or STAR which gets covered by you flight plan. If it doesn't find one there, it will vector you.Changing the runway from the user side (and therefore counteract the weather dependency of VoxATC) should happen via the zero "0" menu. Forcing a special SID or STAR can happen with the SidStarWizard (haven't tried since version 6) or if you include all waypoints of that special procedure in your plan (don't know if that works though).I must admit that the only time I used manual runway assignments (via the zero "0" menu) in VoxATC version 6 was at some airports where the real world people land or depart in one direction only, even with some more or less strong tailwinds. The FSX system doesn't allow this "one way data" to be included in the scenery files (that's why e. g. AI planes always go in both directions or none, there is no "this way only" operator), so VoxATC doesn't and can't know about those special places on earth.

What i meant was that i can do my flight plan on my 2nd PC using FSbuild, without knowing the weather conditions (and runway in use), add a SID and be vectored on the correct SID for the actual rwy in use even if i didnt get it right in my original FP

Ah, now I got it. :(

Hello GuysI am getting slightly confused now.I am a Vox atc user since two years or so and I am very pleased to hear that the new version is adding SIDs and STARs to the ATC. But so far it never worked for me. I tried it in Amsterdam and in Zurich so far. I am using the Level D so I have the Navdata in the correct format and current. But when I m browsing to the folder it tells me that there is no Navdata in this folder. ut if I check the Pronouniciator afterwards all the SIDS and STARs are there and get spelled right. So I m setting up my FP and take the Last Waypoint of the SID as the first Waypoint in my FP, but VOXatc would not give me any SID.Am I doing something wrong?everything else works just fine as before. Altough I m getting some weird sentence to read back after listening to ATIS....Thanks for your help.Best regards Simon

I am a Vox atc user since two years or so and I am very pleased to hear that the new version is adding SIDs and STARs to the ATC. But so far it never worked for me. I tried it in Amsterdam and in Zurich so far. I am using the Level D so I have the Navdata in the correct format and current. But when I m browsing to the folder it tells me that there is no Navdata in this folder.

Hi Simon,Does the path you've input in the VA Advanced Settings dialog include the 'navdata' folder? e.g., F:\FSX\Level-D Simulations\navdata

So I m setting up my FP and take the Last Waypoint of the SID as the first Waypoint in my FP, but VOXatc would not give me any SID.Am I doing something wrong?

If you could post a sample .pln file, I'll load it and see what happens for me. Regards,

Hi FenricUnfortunately I m not able to post pictures. However it worked flying out of Salzburg LOWS into Zurich LSZH and VoxATC gave me a SID and cleared me via a STAR, but vectored me afterwards...So far it works.. I would like to know if you need to assign just one waypoint or do you have to set more than one waypoint in the FP in order to have a SID assigned. For example Zurich has a lot of Waypoints in the Navigraph database wich do not exist in FSX, so you can not assign them when planning your flight.The issue with the message when browsing for the navdata folder seem to be just a bug. Like the Fatal ERROR message in the VoxATC window every now and then. I just ignore it and continue and all works fine...So far so goodregards Simon

So far it works.. I would like to know if you need to assign just one waypoint or do you have to set more than one waypoint in the FP in order to have a SID assigned. For example Zurich has a lot of Waypoints in the Navigraph database wich do not exist in FSX, so you can not assign them when planning your flight.

Simon,I've tried it several ways and it's worked well most of the time.First, like CoolP I use AivlaSoft's Electronic Flight Bag for my general planning. It uses a Navigraph data set (the PMDG variant) so the fixes would be the same. (And now that the ISG avionics is supported with a Navigraph set, them too.)Last evening I flew to CYVR and in looking at the pre-flight weather I felt that I could expect 08R, which has a CAT II ILS approach. From looking at the STARs arriving soundbound, I wanted the GRIZZ3.08B STAR. But because I wasn't being picky about which runway I wanted, I thought to file my route just to the transition fix, PAE. From that point I had options for other STARs if the conditions changed (There was some low visibilities at the time - and I wasn't entirely sure if Canadians flew prowind or contrawind at night....).So the simple route I chose was KFAT J84 LIN J189 LMT J65 SEA PAE STAR CYVR. I set up and flew and after I passed SEA, I got a call from Seattle Center: cleared via grizz three runway zero eight right arrival paine transition acme niner two six . Spot on! I entered that (and the ILS approach) into my EFB and my ISG FMC, then had my call ready for when I was passed to Approach: vancouver approach acme niner two six with you on grizz three runway zero eight right request Full I L S runway zero eight right approach."Fly Full I L S runway zero eight right approach. When ready, report sekok." (A fix about 12nm from the runway.)So that worked - just specifying the intial STAR transition fix.I've also gone so far to file a full STAR and approach - using EFB to lay out the appropriate fixes. Each time I've done that, VoxATC knew what I wanted and let me take it. Even when other aircraft were landing and departing on cross runways. Wheeeee. So if you're using the FSX planner, get yourself some STAR/SID charts for the airports you're working with and try filing your flight plan from ORIGIN to SID-TRANSITION-FIX, through your enroute fixes, and then to your desired STAR-TRANSITION-FIX and finally your DESTINATION.