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.

Pekanuss

Members
  • Joined

  • Last visited

Everything posted by Pekanuss

  1. Hi everyone, Made two flights yesterday, one with 777F and the other with A319. Same weather before yesterday (03-Nov-2014) where I encountered these abnormal turbulences, groundeffect in 140' and non-responsive AT. In short: Same scenario as in every landing since Saturday ^_^ (if I remember correctly at this time I applied the newest hotfix to the SP). This time I used FSGRW latest version and with both aircraft I made picture-book approaches and landings. The PMDG AT reacted so smooth and good to the turbulences (medium turbulences forecasted and finally happened), it was a real pleasure to fly in this weather ^_^. I'll drop a ticket to ASN this afternoon and see what happens and will provide them a link to this topic. Best regards, Ben
  2. Hi everyone, I have the exact same issues (at around 140' it feels like an allmighty ground effect kills the sinkrate all at once). AT is not able to catch the trimmed speed (trimmed for 145, actual speed dropped to 136 and N1 stays at around 56% without being influenced by AT). I too use Active Sky Next with the latest service pack and hotfix installed. I did also notice that since Saturday on every single airport I fly (Dubai, Frankfurt, Munich, Tromso, Bergen ...), the landing is almost impossible due to medium to heavy turbulences and an instant kill of sinkrate at around 140 - 100 ft. It's really a fight to land the plane, but not only the 777. I also suffer the same problem with the A319; yesterday an invisible hand pressed me down to the threshold and the METAR said: 17006 9999 -RA. It was almost impossible to hold the flightpath. I use the 777 SP1b installer (which means SP1b is already included), everything on a new setup, deleted the FSUIPC countless times and setup everything new. It seems that it's an ASN problem (only a best guess by myself). I'll try today same flight as yesterday with same weather conditions. But this time using FSGRW to see if these sinkrate killer appear here as well. Best regards, Ben
  3. That was a nice video, learnt a lot from it and my only thought was: It's that easy? O.O @Rob: I slowly get the feel for it, but trimming to flight level not achieved by now. I struggle a bit like you. When I enable cheat mode I'm always surprised how far away I'm from the 300 knots ref speed. Maybe doing still something wrong who knows. Tried 9 landings today, all a fail. I don't know why and how, but the last 500 ft. to the runway the approach gets more and more unstable. I have to correct the flightpath very often with my Yoke during that time. Then when I think everything is ok, right before crossing the threshold the sinkrate gets broken (gets up from around 750 ft/min. to almost 400 to 300). It looks like the plane flares itself and then it floats above the runway. Irrespective what I do (push the Yoke down and hold it), the sinkrate goes up. Is the ground effect that strong on a 777? I don't know, either witchcraft in my Yoke, or I'm just doing some unexpected things I don't realize at this time . Just out of curiosity. Is anyone having the exact same problems I am fighting against during landing? If not, then my hardware is definately messed up. Best regards, Ben
  4. Hey people, @777simmer: Thank you very much for your explanation and advice. I'll do this practices as you said to get the hang of it. Don't worry the FBW Reference Speed I had only activated in the very beginning to get a basic understanding of the FBW mechanism. Regarding the landing, I'm not a professional but I can say that I don't have the problems with landing. My problem was, that as soon as my controls where centered, the airplane tries to catch the Ref. Speed wich is - as you all explained - perfectly normal. And these corrections cause my V/S to go rapidly down or too much up causing an unstable approach. And this is the point (I think) where I do the mistakes and mess up the landings. But practise makes perfect. @emvaos: Thanks for your explanation and the comparison with FLCH mode. I understand. Watched some videos again, these showed that every pilot controls the thrust as well, not relying on the A/T. They sometimes pull and push the yoke, but they control the thrust all the time. Maybe I should set the Autothrust Override mode to always and also work more with thrust. Because when I simply go with the FDs and pitch too my V/S needed for the 3° slope; as soon as the Yoke gets centered, the FBW catches the trim speed 'ruining' my flightpath ^_^. So I'll will try thrust as well. @Mike: It's really hard to judge. The elevators and ailerons look 'normal' to me, no overreacting or such. In FSUIPC I set the Slope for both to 0 and the Nullzones as well. In the FMC options I set both FBW nullzones to 2%. For the buttons I use LINDA. The drim buttons are set as follows: On Press: Elevator Trim dnfast / upfast On Repeat: Elevator Trim dnfast /upfast I'm curious what you guys have set there, maybe I did something wrong with this settings and didn't know it!? Lets see. Now I'll go learn a bit trimming . See you later
  5. Hi Werner, My first 'official' participation here in a topic . From my part, I have some difficulties getting warm with the FBW system. I think I've read the manual where the FBW is explained 15 times, did research on the Internet how this system works... but don't get it right. I recalibrated my Yoke (Saitek), deleted FSUIPC.ini, played with Slope, Deadzones and the new FBW column settings in the FMC. Either I smash my beloved 777 on the runway with 600 - 800 ft/min. or I float above the runway, but a good landing wasn't archieved within 30 tries today :(. On my approach it happens that when I established my path and the yoke gets in neutral position, the 777 pitches up to catch the trimmed ref speed (if I'm too fast), causing a loss in V/S. When I'm a bit too slow and Yoke gets neutral it pitches down increasing the V/S. I'm constantly fighting the airplane with the Yoke . If I watch my Bluerays of Justplanes or Pilotseye where a 777 is on approach, they make small inputs, not even looking at the trim button. I think I do something really wrong or misunderstood the FBW completely, that's for sure. Even when I takeoff I don't understand the logic behind the FBW. I activated the Trim Reference Speed bug to understand how this works. As my 777 climbed and the new commanded speed shifted from 210 to 250 knots. I tried to trim the aircraft conventionally. But somehow I never get the Trim Speed matched with the speed I want (250 knots for example). Maybe I'm too muched focused on the FD. I know that I need to trim down to set the new ref speed but the FD commands pitch up (so I pull the Yoke back) and then all of the sudden (when I trimmed down) jumps from 10° nose up to 5°. It's really confusing for me. Maybe here's someone who have mastered this or does this for a living and can give me some tips and advice, I'm always willing to learn (and will read some parts of the FCOM later on). I want to get this system mastered ....... some day . Nevertheless, the other stuff PMDG implemented is awesome. The weather radar works like a breeze and I was searching for the thunderstorms to test it . It was really really immersive to avoid the thunderstorm cells with HDG SEL mode and not with guesswork as happened in the past. Great addition! Have a nice evening. Ben
  6. Hi Bryan, Want to thank you for sharing this tip. I saw this in the AeroLogic Blueray and since 30 min. I try to figure out how it works in my 777. Searched 2 min. here and found your tip. Works like a charm. Kudos for you . Best regards, Ben
  7. @machine2035: Very interesting, thank you for the explain! :good: Best regards, Ben
  8. Hi Luke, thank you very much for the explaining. Much appreciated and I understand . For the enroute alternate. When you've reached your TOC, do you then set the Fix from the first enroute alternate to the new one? Or do you draw the next arcs _f r o m_ the next enroute alternate. Example: Your initial setup: LSZH to enroute alternate LEMH (just for example): 420 nm Next enroute alternate WXYZ is 315 nm from LEMH, so you set the fix WXYZ /315? Just curious, never used that, but want to . Best regards, Ben
  9. Hi Luke, saw this on YouTube earlier this day, wanted to comment on that but YouTube bugged me with creating a channel account, Google+ crap and whatnot , so I'm glad I found your thread. May I kindly ask you if you could explain to me, whatfore are these 3 distance rings on the fix page (4 nm, then 25 nm and 420 nm). Saw something similar in the 777F video of Pilotseye.tv. I started searching around but couldn't find any clue why this is done or the intention behind it (special altitudes or autopilot engagement - really have no clue). Very interested in it. Looking forward to your answer and best regards, Ben
  10. Good evening, first post, same problem . Mark may I ask if you had success in the meantime? My tickets regarding this problem are not answered since 08-May and I still can't activate my NGX. Get the same message and after hitting ok, my entire FSX is crashing. Sent a friendly reminder today but no reply after all. I don't want to sound offense in the tickets, but I'm getting a bit impatient, because in two days my holidays are over and I spend the last two and a half days watching the message box that I don't have a valid license. That is really really annoying. This online activation stuff always punishes the loyal customers :(. I hope they get it to work soon. Normally the support answered me within three or four hours and was really great. Kind regards, Ben

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.