davidinbasel

Hi again all. Thanks for the active discussion. Most interesting and educational. As Volker suggested, running the runway number update was what was required. Tonight I was assigned the Hochwald5N departure off Rwy 33 (previously had been 34). Clearly VoxATC could not associate any of the current SIDs for LFSB with a Rwy 34 that no longer exists. My other attempt from another airport must have confronted the same problem. [As an aside, the first time running the update failed ... it updated many runways up to and including all those with an ICAO code starting with K, but did not update those starting with L or later. Maybe there is a limit on how many the updater can process at once?] To clarify for other readers who have followed the discussion of flight planning and what waypoints to insert in order to obtain a desired SID, in my case the Hochwald (HOC) waypoint is the exit waypoint for SIDs for most of the south- and east-bound routes off both main runways at LSFB. So putting HOC as the first waypoint after departure ensures that a SID is assigned irrespective of wind direction and runway in use. (Not so clear going west and north. There the SID exit waypoints look like theyh differ as between different runways in use. Necessary to listen to ATIS before filing, I guess.) Andreas, the complicated procedure of loading and starting a flight (saving the intended IFR flight, then opening another, then returning to the saved flight) was partly due to seeing a comment somewher that FSX needed that in order to properly read in the new flight plan and attach a SID and/or STAR to it. As you are having no problems, maybe that is not an issue. And thanks for the tip about updated scenery. Will try the freeware one recommended. And as Joel noted, I just need VOR & DME to fly these procedures. I use the GPS procedures database only for additional situational awareness (a.) because I'm trying to fly it the hard way (b.) for many of these procedures a GPS is not valid as a primary navigation instrument and (c.) the Reality XP GNS530W database is a few cycles old and may not have all the current AIRAC procedures. Thanks again. David

Thanks everybody. Will try the suggestions in a few days (away on business) and report back. David

I have a problem getting VoxATC to use SIDs and STARs. I am using VoxATC v6.05 with FSX in a Windows 7 64bit environment, with 8GB ram. Only add-ons are VoxATC, FSUPIC, Reality XP’s GNS530W, and RealAir’sLancair Legacy (my IFR platform). Here’s what I have done so far, based on reading the manual and Forum postings. 1 Downloaded the latest NaviGraph navdata FMS file for Level-D 767 format, installed into the FSX directory (Flight Simulator X/Level-D Simulations/navdata), and pointed VoxATC to that subdirectory in Advanced Settings; run the Indexer; and checked that SIDs and STARs are now available to VoxATC by loading VoxATC’s procedure pronunciation editor and checking for the presence of SIDs and STARs. All looks good. 2 Created a flight plan in FSX’s flight planner, and edited to ensure that the first waypoint after departure airport is a valid SID waypoint for the possible runways in use, and likewise ensuring that the last waypoint before the destination airport is a valid STAR entry point for all likely runways (using RouteFinder to identify the appropriate SID exit and STAR entry waypoints for the route). In my example the route is LFSB HOC LSZH. (By “ensuring a valid waypoint” I mean ensuring that waypoint name in the FSX flight plan is the same as on the SID or STAR. I note this because the specific longs/lats differ between the current navdata file and the old FSX data, but I presume that only the name is relevant.) I set the IFR cruising altitude to be at least that stated on the relevant STAR as required or likely for possible transitions, although I don’t know if this is relevant. 3 With the flight plan saved, I save the flight with the aircraft parked at a suitable gate at the destination airport (either allowing FSX to move the aircraft there when closing the flight planner, or having parked there before creating and saving the flight plan and choosing not the have the aircraft moved; I have tried both ways). 4 I then open another saved flight, check that it is fully opened by clicking various switches on the panel and ensuring they move, then close that flight. I then reopen the saved IFR flight. I understand that this is necessary to have FSX connect the saved IFR flight with the new flight plan created for that saved flight. 5. I check that the flight plan is registered for the flight by looking at the NavLog in the Knneboard, then open VoxATC, contact clearance, and request clearance for my IFR flight. I receive “Cleared to [destination airport], cleared as filed, climb and maintain flight level 60 …” No mention of the SID. 6. I have retried with different departure and arrival airports, different SID exit and STAR entry waypoints, but the result remains the same Does anyone have any suggestions? David