I need someone truly gifted at the art of building approaches. I am willing to pay you for your time building them in the FSX environment. I will need samples of your work and contact info. Please PM me for further info.
I need someone truly gifted at the art of building approaches. I am willing to pay you for your time building them in the FSX environment. I will need samples of your work and contact info. Please PM me for further info.
Are you looking for a graphic artist to produce custom approach plates for you, or are you looking for a scenery designer to add actual ILSs and such into a specific airport in FSX?
If you're looking for the second, it shouldn't cost any money. Where and what kind of approach would you like? It only takes a minute or so.
FAA Certified Flight Instructor, Commercial Pilot and Airframe/Poweplant mechanic CFI/CFII/MEII/CMEL/A&P
American Corporate Pilot and instructor of new hires for Shanghai Airlines
AMD X6 1090T black edition CPU, liquid cooled
NVIDIA GTX 480 1.5Gb GPU
8G DDR3-1600 RAM
3TB storage, plain hard drives
Horning in on this thread ~~~
Can you point me in the direction for learning about this, please?
I have a situation where at a number of airports in FSX I just cannot fully capture the Localiser (it wants to stay permanently slightly to the right - OR - to the left depending on which airport) and landing using the ILS causes the wheels to touch down either to the left or right of the ashphalt
When this situation arises I am unable to fly by hand to "correct" the approach/landing despite turning OFF the AP and all of its components.
I suspect this is to do with AFCADs (?) and would like to be able to take the remedial action required for myself.
Never toooooo old to learn (???).
Ken![]()
Old enough to know better...
...young enough to do most of it again
Intel Q6600; 4Gb RAM; 9800GT-512Mb; XP-Home-SP3. FSX; REX; GEX; UTX; FSC; RC4; UT2
Ken, first of all many of these so-called problems you are concerned about are 100% correct. Many approaches use "offset localizers" because of terrain/obstacle restrictions.
Don't assume that they are "wrong."
Secondly, ADE9X is the easiest tool to use. See: http://www.fsdeveloper.com/forum/forumdisplay.php?f=95
Bill Leaming
Gauge Programming - 3d Modeling Eaglesoft & Military Visualizations
Flightsim.com Panels & Gauges Forum Moderator
Flightsim Rig: Intel Core i7-2600K - 8GB DDR3 1333 - GeForce GTX550Ti 1GB - Win7 64bit Home Premium
Development Rig1: Intel Core i7-3770k - 16GB DDR3 - Dual Radeon HD7770 SLI 1GB - Win7 64bit Professional
Development Rig2: Intel Core i7-860 - 8GB DDR3 Corsair - GeForce GTS240 1GB - Win7 64bit Home Premium
NOTE: Unless explicitly stated in the post, everything written by my hand is MY opinion. I do NOT speak for any company, real or imagined...
Please keep in mind that there are a couple of different, yet related things to consider:
1. The simulation of the ILS, VOR, and/or NDB (and beacons) that controls the simulated signal received by your navigation equipment. This simulation is used only by the user aircraft (the one you are flying).
2. The approach data, that is a computer database representation of the information found in Instrument Approach Procedures. A portion of this data is used by the ATC-AI aircraft system to provide guidance for the AI to approach the runway, and to handle missed approach/go-around situations. A bit more is made available for ATC-user aircraft interaction, primarily through menu selections in the ATC window for approach and transitions to runways. Finally, the data are also used to generate automatic flight plan waypoints and courses within the GPS, including visual display of flight segments which include curved segments and waypoint turn anticipation (within certain limitations). There also is limited vertical guidance provided (but not a true VNAV capability).
The first step in trying to analyze and fix potential problems is to try to obtain a current (or at least as of FSX-timeframe) procedure chart to compare to what is shown within the sim. If that comparison suggests a problem, the ADE9/X editing program can be used to compare specific data to charted data (there are certain rules about how to convert the routing data in the chart to the requried database format, but just like IRL not all procedures are really ideal for conversion. An added difficulty is that the procedure has to be able to support the limited AI data, which might conflict with what the chart shows. AI simply can't comply with every actual approach. They do best with a straight-in ILS where there isn't much terrain in front of the runway.)
scott s.
.
Bill, SCott,
thanks guys.
Ken![]()
Old enough to know better...
...young enough to do most of it again
Intel Q6600; 4Gb RAM; 9800GT-512Mb; XP-Home-SP3. FSX; REX; GEX; UTX; FSC; RC4; UT2
My experience is that far more often than not FS correctly locates and aligns localiser and glide slopes to reflect the real world situation. There are a significant number of offset localisers.
Most localisers are now zero-ranged to the threshold. That is, the associated DME reads zero at the threshold regardless of the position of the localiser aerial. This is often not modelled correctly.
Bookmarks