Thank you much, Michael, I appreciate the feedback. I tried lowering the sliders, LOD, mesh complexity, etc. and I'm still encountering difficulty with getting Prepar3Dv2.4 to load successfully, particularly in full-screen mode. Wish I could hit 4.7GHz with my Haswell-E CPU. Water cooling beckons.... Also, received my very first official OOM from Prepar3D on a planned 737-700 flight from Buffalo, NY (USA) to Green Bay, Wisconsin in the terrible cold-snap today (18-Nov-2014) with current weather downloaded by PILOT's FS Global Weather. The OOM occurred while flying by Lansing, Michigan while I was in external view waiting for the stock Lansing airport scenery to load. At that time all my sliders were set all the way to the right with a 2K texture setting. REX4 was configured with compression, i.e. not the 32-bit textures, btw. For those of you who have not followed this thread recently, my system is based on a hex-core Haswell-E CPU (15MB of L3 Cache RAM) with 16GB of system RAM and 4GB of video RAM (more details are contained in my post from earlier today). Obviously this rig has more than enough resources to handle whatever I throw at it (short of real-world weather modeling, real-time ray tracing, data mining, or terraforming - ha!) and I was indeed getting at least 15 fps in most situations (perfectly flyable in Prepar3Dv2). This, however, was the first time I had flown in snowy conditions.... It is a sad state of affairs that LM is still releasing a simulator based on a 32-bit engine, which limits addressable RAM to 2GB. Computer hardware is now capable of driving LOD "Max" and terrain mesh "Ultra/Max", but the 32-bit engine is apparently not up to the task. Hmmmm.... perhaps my NVidia GTX 970 needs to be replaced with the 8GB model when it arrives next month... Does anyone know of a utility I can use to monitor memory utilization of a 970/980? Here's hoping this 32-bit limitation gets "addressed" in Prepar3Dv3... or v4... or v5... (or before I'm too old and feeble to build/enjoy fs rigs)! -=Tim=-
My experience with the GTX 970 has been mostly excellent.... My rig is built with an X99 mobo (ASRock X99M Extreme4) with a "base model" hex-core "Haswell" Core i7-5820K CPU (15MB L3 Cache / 16GB of quad-channel RAM - nothing crazy about the RAM clocking) with a factory-clocked 1.329 GHz NVidia GTX 970 (Gigabyte G1 "Gaming" card) w/4GB VRAM. The CPU is OC'd to 4.0 GHz on air cooling. My OS is 64-bit Windows 8.1 Pro (Windows "10" Tech Preview isn't stable yet). I'm "blessed" with a Samsung EVO 840 500GB SSD - don't fly home without one. The one and only monitor is a Samsung 1080p HDTV connected via a good quality HDMI cable. I've got the following add-ons (and only the following add-ons so far) installed on top of Prepar3D v2.4: -PILOT's - FS Global 2010 for FTX (25GB download for 9m resolution - hey, I'd happily download 2TB for 1m !!) -Orbx - FTX: Global BASE (desperately waiting for Orbx OpenLC for North America) -Orbx - FTX: Global VECTOR (has anyone else noticed the roads running through autogen buildings?) -REX 4 (sprite clouds, c'mon man, give me a break!) -PILOT's - FS Global Weather (I really like their implementation of flight sim weather) -Freeware 737-700 (still waiting for a modern payware 737 for Prepar3D) With the above configuration and sliders mostly maxed out with 4K textures (on an otherwise clean cfg) I'm seeing roughly 30 fps (max configured frame rate) flying at FL300 and above (just about anywhere, including mountainous terrain). I'm seeing about 23 fps with default startup (F-35 at Nellis with default weather) during daytime. I'm seeing roughly 15 fps departing from / landing at stock complex airports (day and night) - perfectly flyable in Prepar3Dv2. Liberty Int'l in Newark starts at about 12 fps and can dip to below 7 (not really flyable) as I head for Manhattan, which has always been a good torture test for all the systems I've built since the early days of Microsoft FlightSim. Windows System Monitor shows me that one of the CPU cores is always maxed at 100%. Depending on what I'm doing the hyper-threaded CPU hits over 60% total utilization so there's got to be some threading capabilities in Prepar3Dv2 (me thinks). NVidia's included monitoring software indicates the GPU reaches a maximum of about 60% "utilization" (whatever that means) no matter where I fly in Prepar3D. (Note that I can max out the video card with certain first person shooter games.) Unfortunately lately occasionally/frequently I have problems getting Prepar3Dv2 to launch. Could just be my rig (which is still new and requires more t-shooting) but Prepar3Dv2.4 will startup, load terrain data, then (before the cockpit is displayed) get stuck on a black screen and then just close (without an error message) after a few seconds. Occasionally when loading weather, switching airports, etc, Prepar3D will crash with a "Prepar3d stopped working, checking for a solution" error (or just close with no message)... This happened once while I pulled up a map to get ILS frequencies.... doesn't happen all the time though. Not sure what this is at the moment... perhaps the CPU is overheating (it is rated for 66.8 C) or maybe OOM (being that Prepar3D is still 32-bit and all)? Could be the NVidia drivers (still no "official" support for FSX/Prepar3D). I'm almost starting to think I've got an issue with my Saitek controllers.... THAT is my experience. If someone tells you they are hitting 60 fps with a 4GB GTX 970 with a stock cfg and the above configuration, I'd like to know what type of nitrogen-cooled system they have fabricated. Otherwise, I'd really like someone to tell me what I'm doing wrong.