cbrdriver

I tried several "bigger and better" AMDs with varying results on FSX, but with the NGX, it's such a complex simulation that i would always wind up with 18 stuttering frames per second at a big airport with all the sliders to the left. I finally broke down and spent about $400 to get a low end Intel mb and processor. I'm now getting smooth simulation with at least 49fps with sliders to the right at even Atlanta. AMD is great value, but to push the NGX, i found that the money was close to the same.

No. The ticket system is still in use. "PMDG Product Support" on the web site.

There are a few issues that can cause this. But with that kind of severity, and With two different aircraft, I would suggest a PMDG ticket.

http://ts.thrustmaster.com/eng/index.php?pg=view_files&gid=1&fid=3&pid=283&cid=1 I wouldn't use FSUIPC for calibration. With as wonderful as it is, it often does not play well with the NGX.

Unplug your yoke Count to ten Plug it back in Open the Saitek control panel and run through the stops. . . Fly

Mostly from experience. That was an issue for me with my Saitek yoke. That's not to say that they don't have a good product. I wouldn't trade my Saitek for anything, but a common issue is a common issue.

Same. I review what updates are available and, in most cases, I'll refuse them unless they're security related.

Obvious questions, but. . . Does your AP engage without an argument? What are the wind conditions. When i was having problems with my Saitek gear, the NGX saw it as control input, and would argue with me when i would try to engage the AP. The wind condition question is kind of obvious. Could you have a cross wind causing a push into a roll?

Very interesting, Dan. If i turn them on, they're not visible until I go to external view. They become visible then, and are visible again from the cockpit. Strange glitch and unknown cause, but you've inadvertently given me a work around. Thanks

No joy, Dan. Made several arbitrary changes but saw no changes to the lights. I closed fsx:se then re opened it with still no change. The only change i can remember was the addition of ASN. I had to delete, then reinstall because it had somehow been installed in the wrong place, and Steam couldn't find it. (yes, that confused me too, because it was installed through Steam) Could that have caused a corrupted file? Thanks.

That is correct. The manuals will be part of the package you purchase (in electronic format)

I've always wanted to see it come to fruition. Now if you can just work out the drop down fuselage.

I did recently learn the consequences of using an old panel state, so I've made sure to be loading with the trik as default, then choosing my NGX model from there. Is that what you mean? I fly out of my last arrival airport, so it seems to be global. I'll try, tonight, to make some changes to my NGX panel through the CDU. I'll let you know. Thanks

I've no idea what has changed. I used to be able to see my runway turnoff lights, but now I don't. The taxi lights are visible, just not those. Where can I start to diagnose this? Thank you.

I've spent a bit more time in my cockpit since the beginning of this post, just looking around, and as far as http://www.737ng.co.uk/mcp3.jpg this pic goes. . . there's some texture issues there. Boeing needs to get with PMDG so that they can fix their cockpit.

I've never thought about it until your post. Never even paid attention, honestly. Maybe a screen shot of above else's?

Actually, it looks normal. Just booted up mine to see.

Just looked at WYNDE7 and i see what you're saying. When I'm flying without ATC i will usually use the EXPECTs as hard altitudes. Most of the ones on WYNDE are pretty simple to plug, it was the Above 13000 and Below 17000 that i was having a problem with. Thanks

Thanks, Dan. As i spent time in the FCOM, i had no idea how to term a search, and became frustrated after reading then re reading for about two days.

RAVNN6 arrival into KBWI has me crossing WALKN intersection below 17000' and above 15000'. I know that this is an integral part of the arrival, and the obvious answer would be to just use the arrival but. . . Is there a way to input that altitude block through the CDU? Thanks

Gotcha. Thanks.

But something strange was happening. My Virtual CDU was apparently not getting good data. So, too get a "fresh state," i shouldn't save the flight at all? Or i should choose a different aircraft from the opening screen?

I've been guilty of saving my flight at the arrival gate, then having FSX skip the opening "choose your flight screen" The convenience was just too great. I've also found that doing that at the departure gate, after setting up the FMC then closing the sim will result in having that flight still set up in the FMC when reopening FSX. I understand that both scenarios will result in me using an old panel state. . . But what if i save the flight at arrival gate, setting it as default, then choosing that flight, without change, from the "choose your flight screen." Will that give me a fresh panel state? This just seems a bit cloudy to me. Thanks

I know I've seen this in another thread, but can't remember which. It leads me to believe that this is normal behavior for the NG. (But of course, i could be wrong) The auto flight system is not completely un coupling, until you hit the AP switch on the yoke, i.e. your Z button. Then shut down the FD as well. You don't need them on the ground.

I seemed to have spoken too soon. FSUIPC didn't run well with version 4.91, but updating to 4.98 fixed that. GeForce drivers also caused several unrecoverable freezes. . . again, fixed with an update. But now I'm back to a fuzzy VC and that same kind of scenery that you'd see in the very first Flight Sim. ( even after going back through my NGX intro and verifying all the settings) Gonna have to do some research on Nvidia settings. . . anyone try Nvidia Inspector with Windows 10?