Banks

If that doesn't work, create a profile with nHancer that forces the level of aa you are looking for. I had the same problem with my AA going to crap everytime I would start SB. I started using nHancer, and now the AA stays at the level it was prior to starting SB.-Steve

Are you kidding me? From past observations, PMDG products spend MULTIPLE years in development, so I would say that their plate is somewhat full at this time to commit to producing a 777.Let's see here, they have provided me with a 73NG V1, 744, MD-11, and have in the pipeline a mystery A/C, a 73NG V2 and an A320.Not acting on the wishes of the customers, eh? Good one.

I think all developers should go to a non-disclosure approach on releasing information about current or future products, as Level-D has done. EACH project takes multiple years to complete, and you as a consumer, on the outside of development, either understand that or you are in a perpetual state of denial and can't stand the fact that the aircraft isn't going to be released a second sooner, than when the developers are ready to release it.You can either choose to accept this, or post repeatedly on these companies forums about how you are not satistisfied with the progress of a development to which you are not involved. Your posts are not constructive, are nothing but speculative, and show a lack of confidence in these developers. I'm sure they don't appreciate it.-Steve Me

With full cargo for me I can only add 209,000 lbs of fuel instead of 258,xxx so it works as designed for me.

This question is asked every other day if not every day in this forum. The word from them is that PMDG will release information on it as it becomes available.

I also get this. My virtual cockpit displays will freeze if I re-enter the VC during one of these times where the only two cycled views are spot/vc. I have to press 'A' in the virtual cockpit to cycle the views and my displays start updating again.

If you can't wait for the i7's, go quad core and then overclock it. Originally, there was very little gain to be had with a quad vs. dual core but that has changed with the coming of SP1/SP2.In the end, I am dissapointed with the combined performace that I am seeing with the MD-11 / FSX / VISTA and am now considering downgrading to FS9. Autogen absolutely murders my frames and as it is, I can barely have scenery complexity high enough to have terminals show up on airports I land at. Maybe the next gen Intel processors will show better results but only time will tell...honestly, I wouldn't purchase a new rig with the Core i7's launching this year. I thought my rig was good enough to get solid performance in all weather conditions with moderate scenery settings but I was wrong. I've tweaked with NvEnhancer but my frames still drop below 20 on final approach just about anywhere. It is what it is.

Hi guys, Not sure if what I'm trying to do would be possible or not....I would like to be able to have the PFD/ND/MCDU on the desktop while FSX is minimized....would this be possible and if so, how would I accomplish this?Thanks for your help!

Look to the left of the PFD on the auxiliary panel or read the manual (Systems section, AGEN.10.12 / AGEN.10.16). :)

Search the forum for why there is no WXr included with PMDG Products. In short, there is no accurate way to simulate a weather radar at this time because variable information is not provided by flight simulator.

I am having this issue as well. For me, switching views to an outside view (via the 'S' key) triggers the screens in the VC to freeze. If I press 'A' after re-entering the VC, (via the 'S' key) to switch view positions within the VC, the screens start working again. This happens every time I re-enter the Virtual Cockpit from an external view.The screens do not go black, they just freeze. Simply displaying the information that was current when I left the Virtual Cockpit.Out of all the display issues I've had with the MD-11, this is the only one of them that I can replicate everytime I start a flight.

I modded the FSX.cfg file with max texture size 768 and toned down some of the sliders in FSX and flew for about two hours without these issues occuring.With that said, now it appears that everytime I press 'S' to switch to outside view, when I cycle back into the VC, the display screens have stopped updating and are frozen displaying the information that was being presented before I pressed 's' to change views. Also, all switches fail to update after re-entering the VC, ex. I can press the numbers on the transponder, but the display doesn't update, it just displays whatever code was in the box before I changed views using 's'. I found that I can rectify this issue by pressing 'a' to switch camera views within the VC. After doing so, everything is working great again, the screens are updating, the switches show proper visual ques on actuation etc.Is anyone else experiencing anything like this upon switching views using the 'S' key?Thnaks for the help guys.

I have the same issue with the flood lights. Once you turn them on, they corrupt the panel surfaces and leave "dots" all over as pictured in the screenshot above. This happens on any panel surface the respective flood light is illuminating.

I am having the exact same problems with the MD-11 on the flight I am conducting right now. I am using the latest Nvidia WHQL 178.13 drivers. The screens in the VC have stopped updating, only the engine nacelles, outline of the wings and cargo containers inside the aircraft are visible. Sometimes when I switch views the virtual cockpit won't appear and sometimes the screen is just black. Please see attached screenshots. Sorry for the size but I want to make it clear what is happening.

After my first flight last night of MEM-LAX, all I am sure of at this point is that this is the only plane I will be flying for a long, long time.I remember back in 2003 when I first saw that there was a high fidelity MD-11 in the works, I was beside myself in thinking that a product of such, would someday be a reality.To Bill and team, simply, thank you.

Maybe a little better...I'm probably breaking all kinds of avsim rules on the size though...I'm working at 3840x1024. The problem appears to be related to the display of the flood lights over the panel surfaces. This is the overhead with overhead flood lights full, no dome light and full panel back lighting. If I shut the flood lights off, all of the dots on the panel surfaces go away. The problem is very pronounced when I have the dome light on and start cranking on the flood lights for the associated panel that I am looking at. Dots start appearing all over the panel surfaces that I assume are to represent the flood lights. http://www.1337inc.com/ohprob2.jpg

Noticing these "dots" on the overhead and on the intstrument panel when adjusting the flood lighting....also heavily concentrated around the dome switch area when the dome light is on. Is this normal?http://www.1337inc.com/ohprob1.jpg

Downloaded @ 1.2MB/sec.Installing Now. :) KMEM-KLAX on VATSIM right now, cya in the skys!

GAME TIME!!!!!!!!!!!!!!!

I'm only several days into my Vista x64 install in prep for the MD-11, but I already see conclusive opportunity to advance those sliders based on improved memory management. I never thought I'd see the day where my system would be screaming for MORE than 4 gigs but here I am. GPU memory utilisation is still minimal and remember, there is a direct relationship between frame rates and CPU clock speed. Spend all you can on CPU.

>I have to disagree with this. Look at this scenario...>>You have a problem with your PMDG 747-400 (FS9) and come onto>the AVSIM PMDG forum as it exists today. You've seen that>someone has posted a fix to this ages ago but as other posts>have been made since then, it's been pushed down the list and>back 5, 6, 8 or more pages. You now have to use the search>engine to find it and it spits out any match with the string>of words you used.>>Instead of the above, you open the tiered forum and go>straight to the "PMDG 747-400 (FS9)" thread and look in the>"Support" section of that thread. There's the sticky put there>by the forum moderators right at the top. No confusion either>over whether it's the FS9 or FSX version. Ahhh, wasn't that>easy!I agree.

>Ok my CPU is overclocked and is running at 3,5 Ghz >>Can i change some settings?LoL, Did you read the post above yours? Start with those settings and adjust ever so slightly accordingly.

Thanks for taking the time to post the screenshots!

It appears as though they have had the green light for a day or two. Just look a few posts down for starters.

Congrats on your new build! Overclocking is free and is one of the only things that you can do hardware wise that translates directly into more FPS within Flight Sim. With the manufacturing of C2D's today, you may not even have to increase voltages to obtain the speed you are looking for. As an example, I can run my e8400 @ 3.6ghz on stock voltages. If properly cooled, you are not going to fry your chip or shorten it's life so that you would notice it by increasing the voltage the small amount needed to reach a reasonable clock speed. Just watch the temps and read the many overclocking forums for ideas on values to plug into your bios and enjoy the increased FPS in FS! :)