Jump to content

CaptainLars

Members
  • Content Count

    212
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

21 Neutral

1 Follower

About CaptainLars

  • Rank
    Member
  • Birthday 07/19/1981

Profile Information

  • Gender
    Male
  • Location
    East of EDDL, near BAR VOR
  • Interests
    Linguistics, History, and umm... yes, Aviation

Flight Sim Profile

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

Recent Profile Visitors

1,415 profile views
  1. VNAV follows the speeds that are indicated on the LEGS page on the CDU. The LEGS page typically indicates 170kts for the final approach. On RNAV approaches, "VNAV PATH" mode is used. Ensure this mode is indicated on the Primary Flight Display. Press / click the speed knob and set Vref + 5.
  2. We need the 777 update, and maybe the 777X in the future.
  3. It's helpful to read the corresponding section of the introductory manual and then enable the FBW indicator until you get the hang of it. Once I did that, my handflying skills significantly increased. That said, I also think that handflying the PMDG 777 isn't exactly easy, probably more difficult than in reality.
  4. I thought so, too. However, it wasn't mentioned in the starting post that PMDG would be currently working on that, yet I hoped they would.
  5. I am missing some other 777 updates. New ground friction model, EFB, rain effects.
  6. Right. And yet 5m is not a resolution low enough to avoid the crash at the threshold. Try 10m.
  7. I experienced this behaviour at SCIP freeware by Carlyle Sharpe. The solution is to set the mesh resolution to 10m (5m is not enough).
  8. I reset the key commands a second time and - so far - they are working again. Any idea about what could have been the cause of this issue? I'm open to any suggestion (even silly ones).
  9. Hi, all of a sudden, my assigned key command bindings for my defined views don't work anymore - but only those that involve one of the numbers on the number pad. That means, they are there, I can see them, but they don't work any more since yesterday. No changes were made, no addons installed. When I set the key commands anew, they work again, but only for a few seconds before they get inop again. This involves the number keys of the num pad. Yes, num lock is activated (though it doesn't make any difference in the sim I think). The "/" key and the "*" key are not involved and work as intended. I already respawned the "wxstationlist" file, but to no avail. Any help would be greatly appreciated. Regards Lars
  10. Thanks, I will try this. Why is it called Rainbow Trails, btw? I've never seen a rainbow appearing there... (or anywhere else in the sim).
  11. Hi, is it possible to get rid of the overwing condensation effect during cruise? I do like this effect, but not half of the time in the cruise segment of flight while being slightly above FL300. Whenever I take a plane (in real life), I look out of the window and at the wings, but I never ever noticed this effect during cruise. It seems to happen just a tad too often. Regards, Lars
  12. the updated 777 the 747-8/F as a standalone version the 777X one of the Bombardier Global series... a 1966 Pontiac GTO
  13. I think I already did that some time ago, but can't find it anywhere. The ticket itself is no longer visible amongst my more recent support tickets.
  14. Excactly this is the point where it's broke. Once you have your constant speed segment completed, you cannot use RTA correctly, which could be useful, of course, when you have a longer flight where the constant speed segment is only one part of the flight. There's a series of cifers appearing instead on Progress page 3, where the RTA normally can be inserted.
  15. A) a constant speed segment does not work together with RTA, and B) once you had a constant speed segment, the RTA function is broken on this flight. It's a bug it seems.
×
×
  • Create New...