KCA9304

Stefan, During go-around this FMC defaults to a cruise altitude of 10.000/FL100.If you stay at the same airport, no diversion, changes are you never climb to that altitude. To get the speeds calculated again enter the actual altitude you climbed to during go-around in the INIT page - Cruise box, Hope it helps, Harry

My vote:MD11.Harry

Denis,Don't think so.Regards,Harry

He's talking about external views, not internal cabin lighting.Enjoy the MD11, she is different!! (as RSR stated years ago)Regards,Harry

Robert,Take as much time as your team needs.Regards,Harry

FBW has it's advantage,so you can tune the flight for the target at hand.Less easy to do that for a 'modernized' 737. Total different airplanes regarding their basic design.Regards,Harry

In both FSX and FS9, the L-key should switch on/off all the aircraft external lights.Make sure your L-key was not changed to something else as the default MSFS assignment.Tip: Logo light is switched as well by the L-key, also be sure to select a passenger aircraft to solve your problem.Regards,Harry

Hello Denis,No, you'r not the only one seeing this annoying VOR symbol drawing.I remember this ever since I have the MD11, also after reinstalling FSX/Acceleration and the aircraft on a new harddisk.I'm running the FSX version on a Q6600, Vista 32-bit and a GF9800GT in DX9 mode. Nothing special about that.I see this happening only on the 2D panels, VC is oke unless I pop-up the ND.For completeness sake: My FS9 installation on my notebook is working correct. (also Vista 32)Not of much help either, but awaiting any smart answer on this from other forum members who KNOW how to solve this.Regards,Harry

Julian,Simple answer is:Slope is not relevant in FSX.Wind: Enter the component, HD or TL component as relevant.Regards,Harry

May it be a stupid reaction as well, I add to this:The MD11 is one of the most silent cockpits I have flown. Be it wind noise or packs or whatever.Regards,Harry

Nothing to do with Candy.Used the MD11 to fly the STAR mentioned by Ryan into KLAX. SEAVU2 -ILS25L.For the purpose of VNAV, selected the RNAV (Z) approach to 25L.-Observations:The next waypoint on the STAR and following approach, is sequenced as soon as the nose of the aircraft symbol hits the magenta waypoint position.However: the next altitude restriction is sequenced some time later, when the aircraft center, which is the (MD11) present position, is passing that waypoint.As these two instances are not simultanious, this triggers a temporary level-off, de-stabilising the continuous descent profile.(for this reason I use FPA for the final stages of the approach.)As far as I can observe, the profile is calculated very excactly and synchronising the Waypoint sequencing with the next profile altitude at the same instance, would give a more smooth descent.May not be the problem that is investigated for the upcoming 737NGX. For the MD11 it would make it more like real life.Hope it is of help.Regards,Harry

Mark,You don't have to shout for beer on this one.It's free.Regards,Harry

Just for information.Landing Flaps 35 (or 50) have been indicated in this thread as a condition to obtain Dual or Single Land mode.Although Landing Flaps are a (certified) requirement for Autoland, the setting is NOT checked during the Autoland check, which is a system redundancy check only for the systems involved.So, Molly, there is something else you did correct to perform your first, non tutorial, autoland.Keep on going.Regards,Harry

Charles,On the NAVRAD page, select *LOC ONLY ?, untill cleared for approach?Regards,Harry

In my post #16 above, the links to some pictures are not working anymore.In the mean time Ryan - Pinned- an item in the General Forum that is strongly related to the problem that Nick (AoA) started.ie- Magnetic variation updates for FS9 and FSX -Updating the VOR's as well to the present values makes the ND look much more like real world, something that PMDG aircraft deserve.Here the missing pictures, so you can compare the differences.FIG1FIG2Regards,Harry

Hallo Vic,It's not to me to write a step by step help file for a GREAT program made by Herve Sors.Learned to use it myself, by reading all available documentation (also for FS9) on his site and having a look at the way the Basic Scenery Grid is set-up in FSX.So just some hints:Google -Basic Scenery Grid- to find a grid diagram telling how scenery is setup on this globe.This link is ESP, but you will find the same grid in your installed SDK for FSX.NDB's and VOR's are stored in the NVXxxxxx.BGL files for every grid-block.With EasyNavs you can update these BGL's to the current MagVar value.Time consuming, but worth the time if you want correct VOR indications.Once more, credit to Herve Sors.Hope it helps,Harry

As documented, it only corrects 4 of the possible 96 scenery areas.Still a great performance made possible by Herve.Regards,Harry

No, it does not break the ILS course.FSX is outdated regarding MagVar, that is if you use current approach charts and latest AIRAC files.In FS. the runways are aligned to true north, the local variation gives the correct runway heading on any ND.So what Tabs means is that the graphical runway alignment (and extended centerline) will be better aligned if using the Magdec.bgl he found on the site of Herve Sors. Unless offset, all ILS'es are fixed to the runway centerline. (be it real or FS).If realtime magnetic variation is applied to official charts (mostly once every 5 years), part of this operation is to change the ILS course as well if needed. (Do not see this at the NOAA charts however, read my thread above). Runway re-numbering is another possible item involved. Now, if your intention is to fly any airplane A to B by FMS and get you captured by the ILS, then you'r done, be happy with the resulting landing.Is there more we should know? Might be.Ever wondered why VOR needles on the ND did not indicate direct to a station?Ever wondered why VOR track mode on the MD11 was in between the MAP dotted line and the VOR CDI presentation?Same reason as the runway alignment being solved by a recent MagVar update.Still interested?VOR's (except a few oriented True North) have there reference to magnetic north.FS.'s VOR's are referenced to the default FS. magnetic variation.(declination if you want).Replacing the Magdec.bgl in FS. does not correct the VOR operation.What you could do, if you like:Read what is avail on the site of Herve. EasyNavs is a possible option to tweak your FSX installation so as to get it as real as it gets. Worked for me, MD11 freak.(real and FS that is)On to the little workhorse NGX, FSX will be the same default, or can be adapted to more real data by using info provided on the site of Herve Sors.Regards,Harry

Paul,While I reinitiated this thread, yes I'm very familiary to this aircraft.Wind and track does not confuse me.Regards,Harry

Ryan,Now that you have discovered the site of Herve, maybe this thread is of more interest now to you and the team.http://forum.avsim.net/topic/320849-md-11-vor-course-on-nd/page__p__1931485__hl__budee__fromsearch__1#entry1931485As stated, for me not only MagVar, but also other items on this site, permitted me to change FSX in a way so as to make the ND of your MD11 behave more like the real thing.It also resolved the VOR TRACK mode.As the runway alignment is taken from the NavData base (WPNavApt) , it would be even better for the presentation if these data (RwyHdg) were correct.Why this doubt?Reference: NACO Approach chart KMEM ILS/LOC RWY09 gives an ILS course 091. The same is derived from the Navigraph NavData file of course, as it is an official figure.Looking at the KMEM Airport Diagram we see that the Magnetic Variation is indicating Januari 2010.Based on this, the Magnetic Runway heading (092.6) is shown at rwy09.As the ILS is not offset, I would expect an ILS frontcourse of 093.Also the radial GQE to BUDEE (shown as R137) is different from what an FMS and other programmes on the mentioned site calculate. (R141)Likewise, using an FMS Fix page to draw published radials over a missed-approach holding point,are offset.Well, knowing this I read the official charts differently at least.For me, several programmes on this site, including the warnings given, worked to improve the ND presentation as seen on the real plane.Highly recommended, including warnings!Other good thing is:The MD11 does not need an update..... -for this one- ..., cause external data (FSX and NavData) are involved.Regards,Harry

Ryan,What is the Mesh resolution you are using in order NOT reproduce this.Default KFSO does not have this aircraft reaction.To exclude any add-ons, AFCAD etc, please have a look at the old links refering to JFK04L or BOS33L etc.Using only default scenery and able to project the aircraft trajectory from a stabilized approach, found both the Queen and also the more modern MD11 to crash land at certain places.Regards,Harry

William,It's an old problem, had it myself and in default scenery, on a couple of occasions.Have a look here:http://forum.avsim.net/topic/278851-strange-behavior-just-before-touching-down/Hope it helps.Regards,Harry

Pete,Thanks for your work in FS and stating facts here so clearly.Chicago is called 'the windy city' but simulating that the FS way, no, don't like that. :( Regards,Harry

Carlos,Where you say that pushing the Dump button, nothing happens, I bet you pushed it once, and only removed the protection cover.Pressing the button twice, should start the dump procedure and at least show some alerts, depending on your settings in the FMS, as others in this thread indicate.Regards,Harry

Nick,What I have done in the mean time regarding this thread.With the help of programmes and very well documented warnings on the site mentioned above:- Updated the default FSX MagVar.- Applied the updated MagVar to the scenery area's around KMEM and other areas on the globe.Not expecting an update on FSX, doing it this way, at least solved my question why the VOR needles are only indicating right to the station on the ND when coming in very close to that station.What it did not change is the dotted line GQE radial 137 ending over BUDEE.What does work correctly now is that VOR Tracking is consistent between the ND MAP dotted radial line and the ND VOR presentation.FIG1Dotted magenta line is Radial 137 from GQESolid magenta line is the Primary Fligtplan made with nativ FSX Flightplanner (is FSdatabase).Needs course 139 accoding FMS.Dotted blue line is the en-route selected arrival for KMEM 09 ILS in the Secondary Flightplan (Airac data).Needs course 141 according FMSHere a picture crossing the centerline RW09.FIG2As Ryan already indicated the differences between the FSdatabase and the real world data can not be solved.At least I'm happy that VOR needle indication is correct now and VOR Track mode works as in real life.Regards,Harry