Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

KCA9304

Members
  • Joined

  • Last visited

Everything posted by KCA9304

  1. 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
  2. Denis,Don't think so.Regards,Harry
  3. He's talking about external views, not internal cabin lighting.Enjoy the MD11, she is different!! (as RSR stated years ago)Regards,Harry
  4. Robert,Take as much time as your team needs.Regards,Harry
  5. 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
  6. 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
  7. 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
  8. Julian,Simple answer is:Slope is not relevant in FSX.Wind: Enter the component, HD or TL component as relevant.Regards,Harry
  9. 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
  10. 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
  11. Mark,You don't have to shout for beer on this one.It's free.Regards,Harry
  12. 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
  13. Charles,On the NAVRAD page, select *LOC ONLY ?, untill cleared for approach?Regards,Harry
  14. 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
  15. Paul,While I reinitiated this thread, yes I'm very familiary to this aircraft.Wind and track does not confuse me.Regards,Harry
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. Thanks for the link Jan-Paul.Harry
  22. Mikkel,Your problem is over when you read previous postsHarry
  23. FYI, independent of SOP,sReverser deployment on ALL 3 engines can be selected as soon as the mainwheels are on ground.Reverse thrust above idle can be selected on engine 1 and 3 as soon as the reverser is deployed.Reverse thrust above idle on engine 2, requires the nosewheel being on the ground.Hope it clears any questions.Regards,Harry
  24. Martin,Mentioned on pampier.FCOM - Alerts - Page A 10.21Regards,Harry

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.