adamant365

I agree, but what I would really like to see would be the option to still set fuel manually in the FUEL screen even with ground ops running. That way, we could still simulate the ground turn (or modified such as mine) and start with a much higher pre-loaded fuel amount.

I actually had the same question yesterday so as I am a tinkerer, I tried something. I loaded the default "747 Long" panel state and started the "Short" ground operations. After about 30 minutes (timer down to 30 minutes in ground ops), I saved the panel state as "Adam Long." I reloaded the sim and selected my new "Adam Long" panel state and voila...the trucks were all in place and the countdown was at about 30 minutes just as I had left it. Now, the tricky part is fuel. If your tanks are near empty, it will take a long time to fuel up. I recommend before starting the ground ops (when initially creating your custom panel state) manually setting your fuel to like 80000 or something (it won't let you manually set fuel once the ops have begun). That way, you can get a reasonably high fuel load within your 30 minute window.

Ah gotcha...for future reference the minimum allowed is 60 and it will accept the value if it is 60 or greater. Thanks Kyle!

Hello, I'm trying to use the "Custom" turn type in the MCDU menu. The "short" turn time of 55 minutes is too long for my taste. I'm unable to put in a 30 minute turn time. I've tried "30", "30.0", and "30.00" in the TURN TIME field with "CUSTOM" set as the type and always get "Invalid Entry." Is there a minimum to the turn time length? If not, what's the format? I didn't see anything in the Intro manual the specifically states a format or minimum time. Thanks!

A beautifully done 747-400, two pogo sticks, a pair of Segways, and several crates of woodpigeons all for the price of the 747 alone. Brilliant!

Rolls Royce. Notice the engines. I would assume the PW version is N744PW and GE N744GE.

I promised myself I wouldn't comment on release speculation, but I'm going to echo those that say it will happen during the week, barring any unforeseen circumstances. For PMDG, it matters not internally because regardless, they are going to be flat out for the next few weeks regardless. The hard work has ended in some regards, but it just beginning in others with all of us in the community reporting "bugs" that they have to filter through. The real reason I think it will be this week is due to hardware support. Although I'm pretty sure PMDG uses Amazon AWS for hosting, it's still easier to get support from a hardware perspective on a weekday. I don't care if it is Amazon...I work for one of the largest IT firms on the planet with a huge cloud presence, and it's still harder to get support from us on weekends :-). Finally, just for fun I think it will be Thursday because the T7 "welcome to release week" was on Aug 26 of 2013 and it released on the 30th...four days. So Thursday of this week as well?

    Yes, and doesn't anyone remember the dozens of new threads from end users asking about the NGX release...then they just dropped it on us and the servers crashed?? I'm not a moron. I was one of those hitting F5 every five minutes when it was NGX time. Same with the T7. Sure, there was that cryptic post from RSR about CEP and all that. But we were never given "it will be released between x and x." That was my point is all... We didn't get really any advance notice about the NGX and only a "Welcome to Release Week" for the T7. No criticism at all for PMDG here. They do what they want because they can. Not picking on you...really I'm not...with the 777 we were given a "week" and it released in that time frame. The NGX was largely silent. The August 2, 3, 4, 2011 frenzy was quite interesting then they released it without announcement and crashed both AVSIM and their own servers. I remember that evening as the NGX was probably the most anticipated addon to that point in the history of flight simmming. Remember the supposed DDOS attack?? Anyway. Fun times. Great learning for PMDG certainly.

Also pretty sure they told us we would get some advanced notice before both the NGX and 777 came out, but they ended up releasing silently.

Was your fuel freezing? PMDG accurately simulated the affects of very cold temperatures on the fuel system of the MD11. Were you able to relight the engines after descending to a lower altitude? A Google search of "PMDG MD11 fuel freezing" will bring up loads of threads on the topic and how to resolve it pre-flight. Hint, you can change the "freezing point" of the fuel on the "FUEL INIT" page 3/3 while on the ground by using Jet A1 or by directly changing the fuel freeze temp by entering a ower number.

If I had followed my own suggestion I would have saved myself some time during the reinstall a few weeks back. It was kind of a derp moment on my part and I deleted the PMDG folder before considering the key command .ini. Luckily, I only have TOGA, flaps, A/P discon, and A/T discon mapped.

Can't you just copy the .ini key map files out to your desktop, run the uninstall/reinstall process, and then overwrite the newly created .ini with your version from your desktop?

What do you have your setting for throttle override set to? In the PMDG options in the FMC you have the option to have your throttle lever override the A/T: Always, Never, or Only in Hold Mode. Look at the Introduction Manual starting on page 93. If it's set to "Never" then that's not the problem. "Always" can definitely be an issue if your throttle is creating "noise" and overriding the A/T. If it is set to "Only in Hold Mode" that could also be the issue, especially if you see the issue only at times the A/T is in "HOLD" mode. As for your near stall on approach, that sounds eerily like what happened to OZ214. What A/P / A/T modes were active at the time of your near-stall??

EK (Emirates) fly to many destinations in their network that are <6 hours. There are other European and Asian carriers that fly <6 hour flights as well. I've been flying the 300ER more than the 200LR since the 300ER came out and I was worried I wouldn't get the opportunity to fly it much.

In addition to what Dan said, I completely unmapped the "Engine" E key from FSX. I used to have the same issue constantly. On the fly, one way to make sure you have both engines selected is to press the "E" key followed quickly by the "1" (top row number) key followed quickly again by the "2" (top row number) key. You DON'T press the keys at the same time... just do it in sequence E then 1 then 2. That will select engines 1 and 2 so that both are being affected by your throttle.

I'm glad my limited knowledge/experience could help someone else. There's something in the FCOM about the A/C not allowing trim inputs that oppose the elevator commands. I can't remember if it applies only on the ground or not though. Glad you got it sorted!

Also make sure your yoke is centered. I had the same issue with the 200LR back in February and I found my yoke was commanding slight nose up so it wouldn't allow my nose down trim input on the ground.

I definitely had the trim issue prior to SP1b and I can report that it is much better with the latest update. Prior to the patch, I was all over the place, particularly in turns. Although I do have to apply yoke back pressure in turns, otherwise, trimming seems to work much better. I have my main flight controls (rudder, elevator, aileron) mapped in FSX. The only flight controls I have mapped in FSUIPC are the trim switch, throttle, and reversers. I have a 10% "null zone" set in the PMDG menu. Regarding the back pressure in turns...I thought the 777 FBW was supposed to apply the elevator correction automatically in turns. I didn't think pilot elevator input was required in turns to maintain level flight. Am I incorrect?? Because if the FBW is supposed to handle the elevators in turns, that piece definitely isn't working.

Good job guys. Much much smoother on approach. I just did a few circuits around KTUL (AA maintenance) and it was as smooth as could be. Great work!

Speedbrake doesn't need to be armed for T/O. Some things that will cause T/O Config warning are improper flaps, improper trim, or speedbrakes deployed. I'm sure there are others but whether or not speedbrakes are armed makes no difference. Didn't realize the comment about armed speedbrakes wasn't aimed at the OP. Armed speedbrakes shouldn't cause a config warning on descent either. If flaps are 20 or higher, you will get the gear horn though.

Apparently I can't quote or multi-quote posts.... Thanks admin for the friendly reminder, I have removed system specs from my sig line. Thanks Ryan for the FBW/Trim confirmation. That's the only issue I've experienced so far.

Very excellent. I can't wait. Thanks for the update! Oh wait...meant to ask. Will the update correct the odd FBW/trim behavior?

It does happen with the 77L, but since the 77L is much shorter in length, it is less pronounced.

In the CDU, there are options defined per livery "Airline Options." You have to look there, not the Addons menu. The option is also in the PMDG Operations Center. This is all in the introduction manual. Give it a read...lots of good info there and the "solution" to about 85% of the "issues" reported here.

There are several topics on this subject. If you are familiar with using EditVoicePack X, here's a link that will help you: http://forum.avsim.net/topic/422862-ground-control-not-recognizing-boeing-777/#entry2818722 Otherwise you can also do what Kyle says.