Search the Community
Showing results for tags 'runways'.
Found 5 results
-
Today I created a flight to KLUK. However, LNM said there was an error in the runway assignments. Looking at the airport diagram, I see that runways 21R/3R are no longer on the diagram but still show up in LNM. After posting the above, I checked and found that the runway was closed on July 1, 2024. -
Hello, I'm locking for freeware taxi and-runway textures for every airport in FSX. Does anyone know where I can find them ?
-
Steve/Cheryl, Just in case you're not very busy at the moment, I thought I'd run a feature request past you (!) ... OPUS already produces excellent SID/STARS info, but I was wondering whether we could also query runways.xml to grab departure, enroute and destination runway information <?>. "Quick ILS" does all that - and then sends the info to FSX (via FSUIPC), allowing you to automatically tune your NAV radios on runway selection. However - it runs in a separate window and needs manual ICAO code input. As OPUS already knows where you are (along with any route info you've already given it), could that process be built into OPUS somehow? Adam.
-
So I have noticed a little quirk with VoxATC that is a bit annoying. Sometimes it is spot on and sometimes it is so off the mark that it has almost killed my virtual plane. One thing it seems to get consistently wrong is the altimeter settings while on the ground. You tune into the ATIS and the green ticker starts scrolling across the top and the ticker will say Altimeter 30.08 but VoxATC will say "Altimeter 29.96" (or any number of numbers that don't match the ATIS green strip). If you have FSX ATC turned on and listen to their ATIS read back at the same time as VoxATC, FSX ALWAYS gets the Altimeter right on the strip but VoxATC is hit and miss. As the METAR data is all coming in from the exact same place, why does VoxATC have problems getting this right? VoxATC is also bad at wind directions. Twice now, while my Avilasoft EFB has said "Winds favor a 22" departure" and I create my flight plan to depart on Runway 22 (El Paso International in this example), I've pushed back from the gate and asked for taxi to the active and VoxATC is like, "Taxi to runway 4 via blahblahblah" I am like @_@ But.. but... ALL the airport traffic is taxing to runway 22... why do you want me to taxi to the exact opposite end of the runway you daffy *(%&@*%& controller!? Are you trying to kill me!? It has done this at several other airports. I file a flight plan with departures based on the wind direction being fed in by NOAA data and it gives me the wrong damn runway. Don't get me started on a STAR approach in which it wants to take me 50 miles out of the pattern to sequence me. The last several airport approaches I've had to disable VoxATC on the approach because the controller is giving me crazy instructions that I refuse to follow and the AI controller won't shutup. I love VoxATC but the wrong altimeter and wrong runways are annoying. Anyone found a work around this or know why it is doing this in the first place? I use FS Passengers X with all procedures turned on and this incorrect Altimeter settings cost me points on my final score 50% of the time.
-
http://gizmodo.com/5983289/23-terrifying-runways-that-will-stoke-your-fear-of-flying I found some of them interesting and some very much a challenge but "fear of flying" - never!!! I have only "simmed" in/out of 4 of these.....
