Modern computers just do not need them and they sometimes inhibit performance that worked well with older computer systems. Tweaks are really bad and should never be installed and used with computers after Sandy Bridge (IMHO). This procedures rids your config from any tweaks that may not be working properly. Most of the time an OOM will be fixed if you move the FSX.cfg or P3D.cfg to a temporary folder and restart the applicable program. The higher the settings the faster your system will run out of VAS. You stated you lowered your AI traffic but what about your other settings. If you use P3D, the same procedure applies except look in the P3Dv3 folder. You then go to the compatibility tab and look all the way down and select Run this program as an administrator for all users. You do this by going to the main FSX folder and right clicking fsx.exe and selecting Properties. You must also make sure FSX or P3D is started up with Admin Privileges for ALL USERS (not just you). You must also make sure FSX (or whatever program you installed this scenery) was installed in a non-default location such as C:\FSX or C:\P3Dv3 (as examples). These programs were made to protect you from evil-doers and many times an anti-virus program will see false-positives in a very safe application like this scenery and not allow files to be installed or a required system registry item to be entered. When you install addon scenery you must make sure that UAC and any anti-virus program has been disabled during the installation.
For instance, if the scenery is trying to call certain textures and they are corrupted or not there, then this could cause an OOM. Highly detailed scenery is just one cause.ĭid you download and run AppCrashView to see what the faulting module was that might have caused your OOM? Missing textures caused by a bad install can also cause this crash. It may or may not be the airport scenery causing your OOM's. V2 has been optimized for better FPS and eliminate most OOM's but it will not eliminate all OOM's.
0 kommentar(er)
