• Content count

  • Joined

  • Last visited

About Mike777

  • Rank
    Member - 2,000+

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Contact Methods

  • ICQ

Profile Information

  • Gender
  • Location
  • Interests
    Flight simulation, European history, classical piano, sailing

Recent Profile Visitors

3,438 profile views
  1. Hi Romain, This sounds right to me. I was going to say that the FMC could compare the radio altitude info with the baro altitude info, but that would just reintroduce the baro altitude temperature uncertainty. I suppose the radio altimeter method could work if the FMC data contained a very accurate topological map of the approach terrain, but that is probably very impractical, and the terrain itself might be subject to frequent change anyway. Mike
  2. Thank you for the explanation. Why on earth doesn't the aircraft in VNAV on approaches use radio altimeter once it becomes available (I know this is not your problem -- you didn't design the 777!)? This is a non-precision, visual approach at last stage. If I can't see the runway from that altitude soon after passing FAF I must go around. This would be true even with good VNAV guidance (although maybe the minimums are different?). Mike
  3. So if you only have horizontal GPS guidance you simply rely on your altimeter at each waypoint? Mike
  4. Richard, this is a very interesting thread you started! I've flown such approaches, and there has been some discussion about them elsewhere on this forum. One thing I learned is don't tune, or at least don't follow, the ILS, as the horizontal and vertical paths can be different -- for example at KSFO 28R. Wing Lai (or someone else), I wonder if you would explain in greater detail why temperature affects the vertical path? Also, is this simulated (or simulatable, if there is such a word) in FSX or P3D? Finally, couldn't one compensate for an incorrect vertical descent path by using the radio altimeter and checking at each waypoint? Thanks, Mike
  5. I couldn't agree more! Mike
  6. Hi Bruce, You have no need to start messing with "the bowels of the PC" to fix either the FSUIPC problem or the GPWS problem! You are scaring me! Just remove the 777 profile and see if that fixes the climb/speed problem. If not, remove FSUIPC.ini and let it rebuild. If you are not familiar with how to find and delete a file, ask your friend, but this is not a complex operation. For the GPWS problem just delete the file ARPT_RNWY.dat in FSX/PMDG/NavData. Mike
  7. Hi Bruce, If you have a lot of profiles for different aircraft and it would be a hassle to redo all of them, first try deleting just the profile for the PMDG 777. If it would be easy to redo your existing profiles, just follow the advice of Romain and Dan: remove FSUIPC.ini from the modules folder to somewhere outside of FSX and let it rebuild. I am just trying to help him avoid the hassle of redoing a lot of work if he has multiple profiles. Bruce, BTW, the file that Kyle suggested you delete to eliminate false GPWS warnings is in FSX/PMDG/NavData and is named ARPT_RWY.dat It is not part of the Airac data and will rebuild the next time you load the 777 (or 747 QOT II). Mike
  8. I believe it's just the flaps. The flaps look like they are up but the sim sees them as down. That's why the aircraft won't climb or accelerate well. Try deleting any assignment of the flaps through FSUIPC before you completely eliminate FSUIPC, and see if that fixes the problem. Mike
  9. Regarding Asiana, as I recall, they were too high and decided to use FLCH to go down more quickly. However they had already set the go-around altitude, which they were below. So the throttles increased and the aircraft tried to climb (VNAV doesn't do this if the aircraft is more than 300 ft below go-around altitude -- VNAV will continue to follow the descent path). So they manually forced the throttles to idle, which put the autothrottles in HOLD (I have been unable to get a PMDG 777 to simulate this, but it is a weird situation not normally encountered). I believe they switched off the autopilot at this point, but the throttles remained in HOLD. They did not realize this, and failed to pay attention to the airspeed, presumably because they assumed the autothrottles would maintain approach speed. Regarding the problem of no autobrakes or reverse thrust until the nose wheel comes down, I have never experienced it, but I am using FSX (Steam). I wonder if this is only a P3D issue? Mike
  10. Thanks. I would have guessed that galleys & lavatories would be included in the base empty weight. But not the elaborate furnishings in first class or satphone equipment. Mike
  11. Just look in the FSX/PMDG/Navdata folder which you already found. Find cycle_info.txt and click on it. it will open in Notepad. Just read what it says at or near the text. Mike
  12. I believe you can get this message if you load a saved flight that is not within the date range of the Airac - not sure though. But be sure and check the two folders Jim suggested, in FSX/PMDG: Navdata and SidStars. if you click on any file in the folders it will open in Notepad -- it should have the date and Airac cycle at the beginning. Be sure not to save the file you open! Mike
  13. I'm surprised, with all the emphasis on reducing weight and recent use of composite materials, that an extra 24,000 lbs would be acceptable to any airline. I am curious to know, what adds so much extra weight? Thanks
  14. There's always the Pause button. I realize it disrupts the immersion -- my daughter was half-grown when I got into flight simulation, but I did have a dog that often accompanied me on the "flight deck" but sometimes needed immediate attention. Mike
  15. Just enter "VHHX" as your departure or destination. Should come up with options for both ends of the runway and a number of SIDs or STARs. Mike