After having CTDs and big freezes on my first few NGX flights, including on final into LGA, I thought I would apply some fixes and see how things went. Here is what I did... 1. Applied the hotfix2. Deleted ENB series3. Verified I had the latest UIAutomation file in FSX Main4. Downloaded and used game booster III5. Lowered cloud draw distance from 100-706. Lowered autogen from extremely dense to very dense I started out at FSDT's DFW with 12-13 FPS on the ground with Ultimate Traffic II running at 75%. Prior to departure from DFW, I turned off all traffic to ensure it wasn't eating my system on departure. The traffic looks good around the gates, but I really don't care if I see it while on the runway and enroute. On the takeoff and initial climb out of DFW, I was getting 18-21 FPS which quickly went up to my limt of 30 in cruise. Enroute, the only time I lost frames was when REX loaded. I am going to turn the REX load times down. I'm afraid if REX decides to load on final in a dense scenery area, it will crash. On descent in to FSDT's ORD, frames gradually dropped to around 12-15 on final. I think ORD is a little more detailed than DFW, thus even lower frames. After landing, I turned my traffic back on and got under 10 FPS during taxi. That is low, but should be expected with UT II at 75%, at FSDT's ORD in the NGX. Plus I'm running three monitors. Other than the taxi at ORD, I didn't notice any freezes or major chops. I'm really glad there were no CTDs this time, but this is just one flight. The next test will be going from FSDT's LAS with Mega Scenery X to FSDT's JFK. Going into NYC, I think I will have to lower my autogen even further. Dave

I'm not having these CTD's, (most of the time), but how can you get so low performance with a i7 2600K 4.3 GHz? I can run 15-18 fps at Aerosoft Schiphol, and FSDT airports without traffic, ultra high scenery, with an i7 860 2.8 GHz.Now I'm starting to doubt if it's worth overclocking...

I'm getting the same framerates with an E7600 running at about 3.4GHz. Of course, my graphics settings are a bit lower, but not by much.

I got a I7 860 o/c @3,4Ghz, 8 Gigas RAM, ATI HD5870 and win 7 64, normal autogen max REX resolution, but constant 30 fps even in complex environment.

I think it's the three monitors.

I think it's the three monitors.

That's a whole other ball game. I'll take my puny E7600 and 9800GT and I'll be on my way if you guys don't mind.

Out of the blue I started having CTD's when I flew in or out of LGA. Then I started having the same at MCI. Both Imaginesim airports. I uninstalled both for now. MCI flights are fine now with the default scenery. I am hoping that a reinstall fixes it. I haven't tried a LGA flight yet. They worked fine before and I made no changes to my pc. The only thing I can think of that changed is possibly the seasonal textures.

I have a shed-load of stuff installed around New York, including lots of Megascenery, Aerosoft's 'Manhattan' and the FSDT KJFK package. I also have almost all sliders maxed. I can fly continuously, at low altitude around the area in the NGX without a CTD. Even loitering around Manhattan, I'm getting 15-18fps. Away from there, I'm getting about double that. Overclocking made this possible. So far, I've only had ONE CTD, in Orbx PNW area. It is a truly STUNNING addon but, does need a fair amount of 'grunt' to run smoothely(?)

Strange...it almost seems like performance has no correlation with system specs. I tried to take a look at what was hitting the FPS the most by switching between my Coolsky MD-80 and the NGX. At a default airport with no traffic the Cool sky maxed out at 30. The NGX dropped to 22. AT FSDT's ORD without Traffic, Coolsky gets 17, NGX gets 13. If I add the traffic at ORD, Coolsky gets 13 and NGX gets 9. I really think the big culprit is the FSDT ORD scenery. My FSDT DFW scenery goet 17-18 FPS with traffic and the NGX. Going from full screen to window'd mode didn't make much difference. At least while I was changing aircraft, moving to different airports, going from full screen to windowed mode, and using the menu and such, I got no CTDs. That is something to be happy about.

I'm not having these CTD's, (most of the time), but how can you get so low performance with a i7 2600K 4.3 GHz? I can run 15-18 fps at Aerosoft Schiphol, and FSDT airports without traffic, ultra high scenery, with an i7 860 2.8 GHz. Now I'm starting to doubt if it's worth overclocking...

I also have Aerosoft Schiphol and i get (depending where i'm taxiing) 25-30 fps with Antilag limiting to 30fps and about the same on approach to 18R. Good luck to Dave at KJFK, its brutal in some spots on approach or departing + i never have my UT2 as high as 75%. To me thats overdone.

I finished flying most of the day. Started out at RKPK to WBGB, changed my mind mid-flight and landed at RPLB. Added some fuel and flew on to WADD. NO ISSUES WHATSOEVER. I flew Quantas (old colors). I fiddled a LOT with FMC and had not one issue. Today went well, no freezes and no crashes. I did back down some settings yesterday and it seems to have helped.