billflag

In Prepar3D, I set all of the graphics settings to max, but left the autogen vegetation to zero, and I'm good for about 2000nm before I get an OOM error...and that's with FTX Global, GSX ground crew, REX, and Active Sky Next. I do have a noticeable frame rate loss while on the ground. Once airborne...smooth as glass. Of course, on approach, the frame rates decline again...but to a workable level. Interestingly, I have FSX also installed and have NO problems with frame rates or OOM errors, even with the highest setting...same addons installed. However, the graphics quality just isn't as good as Prepar3D. For example, FSX shows trees and houses around KPHX, while Prepar3D shows a more accurate desert environment. Also, ground textures are quite a bit better in Prepar3D at altitude than they are in FSX. Bottom line for me: Since I fly commercial airliners exclusively, I'd rather have better overall performance than scenery quality. So, FSX remains my simulator of choice for most flights. After all, when flying a commercial jet, you're focused on the cockpit during takeoff and approach, so outside scenery is of a lesser value. Once at altitude, earth graphics is quite acceptable in FSX. Once Prepar3D solves the OOM issue, I'll probably transition over because it offers better overall graphics control with better scenery quality.

Unfortunately, I just attempted a long flight from KBOS to KSFO, and I got an OOM message halfway through the flight.....work in progress. Hope LM comes up with a solution.

This link hits the nail on the head concerning the OOM problem: ...#####.wordpress.com/fsx-oom-and-addon-vas-usage... I downloaded the link for a process manager from the link above and have had no more problems with OOM errors once I tweeked my Prepar3D graphics settings and kept the VAS below 3.9 GB. The 4 GB VAS limitation includes Prepar3D and all sub-processes listed in the process manager under Prepar3d. However, if I allow the VAS to get up to 3.9GB, I start losing screens and at around 4GB, I get the OOM error message and the program shuts down. This only happens between initial descent and final approach and doesn't occure during the rest of the flight. I'm using Prepar3D, FTX Global scenery, REX, Active Sky NEXT, and GSX, with the AS Airbus Extended X. The only to subprocesses running under Prepar3D are the sound files for Airbus Extended X and GSX. When my VAS usage approaches 3.9GB, I can shut the GSX process down immediately, giving me an extra 300-400MB, and the program doesn't give me an OOM error. Unfortunately, I can't use the higher scenery settings in Prepar3D without getting an OOM error. The scenery is still very reasonable and the frame rates are great: Graphics: 1024x1024; Anisotropic 4x Scenery: Terrain: Detail radius-High; Mesh Complexity: Medium; Mesh Resolution 38m; Texture Resolution 1m....Scenery Objects: Scenery Complexity-Extremely Dense; Autogen Vegetation Density-Normal; Autogen Buliding Density-Normal; Water and Bathymetry-Medium; Special Effects: Medium. Lighting Shadows-low; Traffic: Airline-27; General Aviation-0; Airport Vehicle Density-none; Road Vehicles-23; and Ships-54. Other settings might work OK too, but so far, I don't get any OOM errors with these settings even when using all of the programs I listed above, so I'm content. With these settings, I've successfully completed 11 flights from KPHX-KSFO, and 2 from KJFK-KFLL with NO OOM errors. I've also read on the forum that LM is working on a fix to the OOM problem. The problem will also be solved once LM converts the simulator from 32bit to 64bit.

737NGX and FS2 still DO NOT work. All of the responses I've received about it working OK are from persons that upgraded from Windows 7. I haven't heard from anyone that has done a clean install with windows 8. Upgrading may keep files that were resident in Windows 7, whereas, a clean install will not. Also, my video card, ATI Radeon HD 4850 does not have a Windows 8 video driver posted on their website...this could very well be the problem, as I'm also having a problem with the video driver for another application....

I actually like Windows 8 (especially the price) as compared to previous upgrade options. I find the interface very friendly and apps work quicker. HOWEVER....although FSX works great, PMDG 737NX AND FS2Crew DO NOT...at least on my computer. From previous posts, it seems that they might work OK of you upgrade to Windows 8. I couldn't do that because Vista required a "clean" install, despite what the Microsoft website stated. I guess it's just a matter of time before PMDG or FS2Crew come up with a solution....

Still haven't been able to resolve 737NX crash in Windows 8. Was unable to "upgrade" to Windows 8 because I had Vista Ultimate 64bit, so had to do a clean install. FSX works great until I load NGX. NGX by itself crashes every time I end a flight or exit FSX. However, when I load FS2 Crew version, the program never works. 2D screen does not load correctly and I never get the "countdown" you normally see when you load NGX. I can't back out of FS2Crew; I have to completely remove FS2Crew AND NGX before FSX stops crashing. As soon as I remove them, FSX works perfectly without having to reload FSX. I've tried numerous reinstalls and graphics settings with the same results.

I did a completely fresh install of FSX/Accelerator AND 737NGX. FSX works fine until I install NGX. Program crashes every time I end flight or close program. Also, the "countdown" doesn't work nor does the 2D panel. I've tried to reinstall several times with same results. I do have SP1c installed. When I removed NGX, FSX works fine. Never had problems before I moved to Windows 8.