No issues here. I just competed a flight from PANC to PHNL (~2800nm!) in the ETOPS Alaska -800. Various other pattern work before hand with one CTD at FSX close (no surprise). Not a hitch!!! Most of the issues I've seen on the forum so far have been the following: 1. PC specs at or below minimum. A lot of this going around. A 4-6 year old PC isn't enough, guys. Not with the setting's you're running, and not without understanding how to make it work.2. Complete disregard of the manual, lack of system knowledge, or laziness.3. FSX short comings. UIAutomationcore.dll CTDs. OOMs. Etc.4. A hand full of plain old unreasonable people.

mostly all good here as well. I do have a repeatable FSX close/exit crash on occasion (I will post some screenies about this later after a bit more testing). Overall, it is absolutely killer. Beautiful, both aesthetically and technically. See attached pic.

No issues here. I just competed a flight from PANC to PHNL (~2800nm!) in the ETOPS Alaska -800. Various other pattern work before hand with one CTD at FSX close (no surprise). Not a hitch!!! Most of the issues I've seen on the forum so far have been the following: 1. PC specs at or below minimum. A lot of this going around. A 4-6 year old PC isn't enough, guys. Not with the setting's you're running, and not without understanding how to make it work.2. Complete disregard of the manual, lack of system knowledge, or laziness.3. FSX short comings. UIAutomationcore.dll CTDs. OOMs. Etc.4. A hand full of plain old unreasonable people.

Pretty much sums it up. Point 4, seems like more than a handful.... pushed me over the edge on one guy... Pushing the boundaries with such a antiquated platform is bound to spawn problems. I feel for PMDG with this ddos thing. Wish I could help. Actually we all can help by being more understanding wrt what they have to contend with. It is all going to turn out on the plus side.

For once I'm actually NOT having any CTD's that weren't caused by me. I changed views when the panel was initializing that was my fault. But so far so good. Specs in my siggy. I expect your proposed system to do well! (I'm actually running at 4.4GHz at the moment).

- shes flawless. No problems here at all. Most of whats happeneing here is user error or conflicts in OTHER software programs. None the less mates, they will get it all fixed "soon" :)

Well, she's not flawless, but she is completely flyable and a joy to use. I've already gotten several hours under my belt and I've had a blast. I just did my first V1 cut in it and now I'm gonna go back in for some more. Awesome purchase.

I have to say again for the third time now that this aircraft is just freaking awesome. I'm actually not having any problems and I'm running a duo core processor 2.3Ghz 3Gb Ram with built in video card Windows 7 64-bit Toshiba Satellite laptop. I have most of my settings on medium a couple are on low. The only thing I had problems with was actually the -900 and -900WL liveries but I got that sorted out now. Again I love this aircraft.

I have absolutely no issues. FPS are great at FSDT KJFK and even better at KSFO X (Check My Sig For My Specs). This is definitely worth the money bro. Can't wait till my day off on Monday so I can play around some more with this aircraft.

I am running the same as what you ordered, cept I have a 560 TI as well. The plane, she runs great, I just did a flight from CYYC - KLAS and then back to CYYC, with no problems with the plane itself whatsoever. I am having an issue with my my FPS dropping, but doing some investigating on my last flight, I BELIEVE it is temp throttling the chip (hit 96 degrees C on Core 0). So I have reconfigured one of my fans to blow right on the cpu fan, and gonna take it for another spin, and see if that cools things down a bit. But basically what it is doing is, I can run up to 60 FPS, then it drops to 30, then to 17, sometimes down to 7, then shoots right back up to 60 again, all without doing a thing, not moving my view nothing. So I am thinking that's what it is. If the fan move doesn't work, then I am going to order liquid cooling for it. It's running way to hot for my liking, and it's not even overclocked!

I am running a basic Asus Laptop, no upgrades, its loaded with crap and FSX Addons and is 2 years old with Windows 7 64 Bit. I run the NGX perfectly with 35+ Framerates (Outstanding considering I usually run addons with 15ish) and I have not had one problem other than a livery issue which they are fixing. The plane works great and I have found 0 bugs and have completed 2 flights VMC and IMC, one at night, and conducted autolands and other manuevers. THIS PLANE ROCKS! Thank you PMDG for the time and effort and for those having problems all I can say is something went wrong on your end cause this thing is working perfect and is everything I hoped for. Kudos PMDG! Zach Hutcherson

All I can say is that it has met and exceeded my expectations... I couldn't be happier with it! So far the only issue I've had is some funny business installing -900 liveries, which is apparently solved, I've just been too lazy to fix it yet. Other than that the only issues I've been having are due to me winging it without really reading much about the systems yet. This is a support forum so most of the posts are going to be problems people are having... and most everybody else is probably a little too busy flying it to be here posting about how everything is doing what it should be doing.

1. PC specs at or below minimum. A lot of this going around. A 4-6 year old PC isn't enough, guys. Not with the setting's you're running, and not without understanding how to make it work.2. Complete disregard of the manual, lack of system knowledge, or laziness.3. FSX short comings. UIAutomationcore.dll CTDs. OOMs. Etc.4. A hand full of plain old unreasonable people.

1 and 2 especially... reading the intro solves most of the low FPS threads, and the rest are running on old systems. Even with the old systems I'd bet you could at least make it flyable from the 2D panel if you're realistic with the sliders and have a clean enough system. And 4 ... welcome to the internet, I guess... Not everybody wants to be happy.

I'm reading through the forums and starting to get discouraged with the NGX and FSX (more the latter: OOM's CTD's etc) the more I read. I am waiting on parts for my new i7 2600K Sandy Bridge, gtx570, 2X4gb DDR3 ram build however all the issues everyone is having is making me nervous I just wasted alot of money... Is there people NOT have issues? If you have any of the specs I just mentioned, please feel free to reply with how things are going for you so far. I'm not saying there isn't people that aren't happy, they just seem to be keeping to themselves if that is the case.

My NGX is running great at a constant 20 FPS on the ground and air (this is what I run limiter at with my configuration). It is super smooth for me.

Absolutely no problems....from going to PMDG website to load the acft, about 15-20 mts...and I rebooted my system just to be sure with all that support installs. FPS compared to my PMDG 74X which is the biggest FPS user I got...departed FSDT KJFK, on take off roll with HGS on VC and Track IR, FPS dropped to 5 but picked up once in the air. Wow...what sounds and lighting...PMDG, did you guys deliver, or did you deliver... Hats off to the DEV team. 2D panel has better FPS, so that probably should be used. Now I am off to read the manual.

No issues here. I just competed a flight from PANC to PHNL (~2800nm!) in the ETOPS Alaska -800. Various other pattern work before hand with one CTD at FSX close (no surprise). Not a hitch!!! Most of the issues I've seen on the forum so far have been the following: 1. PC specs at or below minimum. A lot of this going around. A 4-6 year old PC isn't enough, guys. Not with the setting's you're running, and not without understanding how to make it work.2. Complete disregard of the manual, lack of system knowledge, or laziness.3. FSX short comings. UIAutomationcore.dll CTDs. OOMs. Etc.4. A hand full of plain old unreasonable people.

Can someone explain the UIAutomationcore.dll issue? First time I have seen it. Does the intro doc have a fix for this?

Bump. I'm on my cell phone now so can't post for for the last gentleman.