Jump to content

KingCat

Members
  • Content Count

    153
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

3 Neutral

About KingCat

  • Rank
    Member
  • Birthday 04/09/1978

Profile Information

  • Gender
    Male
  • Location
    Netherlands

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

2,065 profile views
  1. Yes, I did mention direction of takeoff in my post (rwy 26R). I did "self-vector" towards VR, but it wasn't possible to line select that or any other waypoint in the route on top (selected waypoints appeared in the scratchpad, but dropping them on top did not do anything).
  2. Yesterday, I had a similar issue where the FMC would not let me line select waypoints on top of each other. Route: CYVR-YVR9 (SID)-VR-HUH-SEA-J65 LMT-TUDOR2 (STAR)-KSMF Departing from CYVR runway 26R. The first waypoint on the YVR9 are VECTORS. Departure was flown with HDG SEL and VNAV. When I tried to line select VR on top a few miles west of the airport, VR appeared in the scratchpad, but would not go on top. Same with the other waypoints (e.g. line selecting HUH on top of VR same problem). I solved this by creating a RTE2. Never had this problem in the NGX. Route was entered manually.
  3. I agree with this topic. Right now the keypress for the beacon lights toggles between lwr beacon and off, while it should toggle between off and both to make this keypress useful.
  4. If I recall correctly, your mesh resolution has to be at least at 10M or higher. I think this only happens when doing an Autoland and approaching an airport over water.
  5. If you are flying towards INN on heading 230, AB should be behind you. Also make sure that the range (scale) of your ND is large enough.
  6. I've attached 4 pictures of the real NDB's at LOWI. They are AB, INN, KTI and RTT. I took the pictures myself a few years ago. This year I'm going to visit the NDB's again to record their morse-ID. Enjoy the pics and happy Easter.
  7. I hope the new 737NG will be released for FS9 as well. That would be the biggest news for me personally. Let's hope it makes it into FS9.Jon
  8. >For the 737, the gate position is not implemented. I'm not>sure about the 747.>I think it's the other way around. For the 737 the gate postion is implemented, but not for the 747.It's best to use the GPS postion when using the 747.Jon
  9. >Jon,>>There is repaint for the 747-400 BCF of Martinair.>It is found on AVSIM on this link,>http://library.avsim.net/download.php?DLID=94143>And the filename is mp744phmpp.zip.>>Greetz, RonaldRonald,That's absolutely fantastic! I just have one question though.I own the passenger version of the PMDG B744. Since this is a livery for the cargo version, my question is if I can use these texture files for the passenger version too?Jon
  10. Hi,I would be interested in a Martinair livery for the B744.Or if anyone else knows where to download this livery, please let me know.Jon
  11. >John and Michael:>>John: I'll will check your points if autotune fails, but so>far it didn't. What do you mean with pt3: I doubt if the>runway must be on top of the legs page because at that point>you are already approaching the runway. I think most of the>ILS legs will start at a fix where you can capture the ILS.>Did you mean that the first ILS fix must be on top?>>Michael: I upgraded yesterday the AIRAC and SID/STARS to the>latest versions, after that I had 2 flights without any>problem BUT still NOT SURE if the problem is solved because I>have the problem irregularly.>>Thks,>Herman It's not about that you're already approaching the runway. It's about that your next active leg is on top in the LEGS page. In this case that's the ILS runway. And yes I meant the ILS runway not the first ILS fix. But I must say that I use this procedure without any problems when using FS ATC vectors. If you're using a STAR, then eventually the ILS runway will come up on top of the LEGS page also, so it's basically the same procedure.The problem with FS ATC is that you have to deviate from your flight plan when you start receiving vectors to final. At that point it's best to up-select the ILS runway on top of the LEGS page. It has always worked for me this way.You don't have to have VNAV enabled for autotune to work. I fly without VNAV all the time.You mentioned "within 200 miles of top of descent". This has to do with the ILS frequency and approach course being displayed on the NAV RAD page (e.g. if you're within 250 miles of top of descent, the NAV RAD page will show PARK instead of the frequency and course).Jon
  12. You could try the program Real ATIS by SkyTalk Team.Additional info can be found at www.simmarket.comI haven't tried the program myself, but it seems to do what you're looking for.Jon
  13. You have to do the following things in order for the FMC to autotune.1. Select an ILS approach on the ARR page.2. Close up the discontinuety on the LEGS page with the ILS runway you're landing on (up-select the ILS runway). This only applies if you're not using a STAR, and are following FS-ATC vectors.3. Make sure (this is probably the reason that your FMC will not autotune) that the ILS runway you're going to land on, is on top in the LEGS page.Best regards,Jon
  14. Merry Christmas to you too!KingCat
  15. The load manager is located in the PMDG folder (e.g. C:Program FilesMicrosoft GamesFlight Simulator 9PMDG747400_LoadManager.exeYou can always create a shortcut and place it on your desktop for easy access.
×
×
  • Create New...