|
Post by aerofoto - HJG Admin on Oct 12, 2016 20:02:27 GMT
We did "quite a bit of work" on these DC-9 panels, so, some of the features represented in what we offer are/may be "different" from those of the original panel versions (I can't recall whether or not we worked on the AP functions though .... this was all to many simulations/developments ago) .... and yet other features represented wthin our versions of these panels were not included within the original.
Mark C AKL/NZ
|
|
|
Post by M.I.B. on Nov 10, 2016 17:07:48 GMT
Hello ! I was the one programming the Autopilot related to Stellan 's DC-9. When A/P is active and the Nav selector is moved to "RNAV" position, the A/C should be able to follow/track the flight plan providing a plan has been loaded. And yes, I know this is cheating ! Best regards, Geir Indeed that's what it is, I've just taken one of the 9s for a test flight, and it sure does follow the flight plan route, don't know why I didn't think of that. Mystery completely solved Thanks Geir!
|
|
|
Post by walterleo on Nov 11, 2016 9:41:54 GMT
Hi friends: What Geir calls "cheating" is the way the default "GPS-following" in FS9 works. One can live with that as long as you dont try to "fly" transatlantic or following real instrument navigation charts, as the flight plan creation in FS9 is "less than real". But there exist programes which create a fpl outside FS9 and one can load it into FS9 taking into account all the latest real navigation information, AIRAC Cycles and Notams. A dream for some Virtual ATCs. rfinder.asalink.net/free/It looks like this: NAT: Eastbound track message identification is 316 NAT: Westbound track message identification is 316 NATs: NATU: can't identify fix 4630 (-1) Computed route from MEXICO AEROPUERTO INTERNACION (MMMX, MM) to CANCUN AEROPUERTO INTERNACION (MMUN, MM): 11 fixes, 694.5 nautical miles Cruise altitude between FL330 and FL330 MMMX (0.0nm) -SID-> APN (40.0nm) -UT19-> AVIVI (234.7nm) -UT19-> VODAG (266.9nm) -UT19-> VIDMU (316.6nm) -UT19-> ELOPA (398.5nm) -UT19-> AXUKU (468.3nm) -UT19-> MID (538.4nm) -UJ18-> TULUM (570.7nm) -UJ18-> AVATA (595.5nm) -STAR-> MMUN (694.5nm) Details:
ID FREQ TRK DIST Coords Name/Remarks MMMX 0 0 N19°26'11.02" W099°04'19.09" MEXICO AEROPUERTO INTERNACION APN 114.8 71 40 N19°38'14.25" W098°23'54.73" APAN AVIVI 79 195 N20°11'50.00" W095°00'00.00" AVIVI VODAG 80 32 N20°17'01.00" W094°26'10.00" VODAG VIDMU 80 50 N20°24'47.00" W093°33'52.00" VIDMU ELOPA 80 82 N20°37'01.00" W092°07'30.00" ELOPA AXUKU 81 70 N20°46'54.00" W090°53'37.00" AXUKU MID 117.7 81 70 N20°56'16.97" W089°39'22.40" MERIDA TULUM 87 32 N20°57'35.00" W089°04'49.00" TULUM AVATA 87 25 N20°58'30.00" W088°38'21.00" AVATA MMUN 87 99 N21°02'33.87" W086°52'23.52" CANCUN AEROPUERTO INTERNACION
Tracks are magnetic, distances are in nautical miles. MMMX SID APN UT19 MID UJ18 AVATA STAR MMUN The bad news:IF YOU WANT TO USE THE fpl EXPORT FUNCTION: PLEASE REGISTER AND PAY!Kind regards Walter
|
|