Verify software started via EXE.XML are NOT still running Verify software started via EXE.XML are NOT still running
If you have CTD during a flight, the software loaded from entries in theEXE.XMLEXE.XMLfile(s) will still be running. These programs need to be terminated using Task Manager or Process Explorer.
An example of programs/add-ons that could still be running after P3D terminates are:
GFDev.exe GFDev.exe
SimObjectDisplayEngine.exe SimObjectDisplayEngine.exe
If you attempt to run P3D again while these programs are already running, it could cause problems and/or prevent P3D from running correctly.
After exiting P3D, it can take anywhere from 30 seconds to 3 minutes for programs (add-ons) that were launched via the EXE.XML to properly terminate. It’s
important that P3D is NOT restarted before these programs/add-ons are terminated.
Out-of-Memory (OOM) Out-of-Memory (OOM)
This is a commonly reported error that is a result of many add-ons and/or very high graphics settings resulting in P3D attempting to use more than 4GB of memory (VAS). P3D is currently a 32bit program and is limited to using no more than 4GB of memory (regardless of how much physical RAM you might have installed in your computer).
The solutions to resolving this error are many, but almost always require the user to compromise graphics details and/or reduce the number of concurrent add-ons being used.
Here are some tips to reduce frequency of OOMs:
P3D graphics settings – reduce texture resolution to 1024 x 1024.
Disable airports not being used in your scenery library.
Reduce the number of add-ons being used at the same time.
Minimize view usage during flight (stick to just VC view and/or spot view only).
Avoid manually changing Time/Season before flight (especially switching from dawn to day to dusk).
Hardware, Overclocking, Performance Hardware, Overclocking, Performance
Flight simulation will always require as much computer hardware as you can afford. Many people try to compare 3D shooters to a flight simulator and say why can’t a flight simulator look like a 3D shooter. The answer is always “view distance”. 3D shooters operate at much smaller view distances between few 100 feet to at most 3 miles before the back drop is just a single static image. Flight simulators work at a visual distance of 100-200 miles or more and it’s a continuously loading globe … no waiting for the next level to load as with 3D Shooters.
The global size the planet along with extreme view distances puts a huge strain on memory, memory subsystems, and of course both the CPU and GPU.
With that said, flight simulators can still look pretty stunning, especially when optimized to make the best of one’s computing hardware.
Hardware Hardware
It doesn’t make much sense to list hardware choices in this document because hardware evolves and changes every few months, new video cards, new CPUs, new monitors, etc.
However, when selecting hardware for a new build or upgrade to existing computer, it’s good to balance the system as best as possible. Pairing up a high end GPU with a low end CPU will not provide a good overall system balance and will not realize the performance potential of the GPU because it’s being held back by a low end CPU.
It’s good to shop smart, top tier hardware rarely has a good price to performance ratio.
With that said, P3D does seem to respond well to the following:
Large L3 CPU Cache (shared cache across all cores)
Higher CPU clock frequency
Higher memory bandwidth with fast SSDs Large L3 CPU Cache
Large L3 CPU Cache
The L3 cache is a shared cache so it’s used by all CPU cores. For some CPUs (usually those with 8 or more real cores) disabling Hyper-threading frees up the L3 cache which improves the probability of access “hits” for data and/or instructions … this can help keep up the flow of processing and improve overall performance (specifically FPS).
Examples of L3 Cache sizes: frequency at which you operate those cores at. For example, if a 5960X with Hyper-threading enabled can only reach 4.3Ghz overclocking, but when Hyper-threading is disabled the same
Overclocking Overclocking
P3D does benefit from overclock both CPU and GPU. The most cost effective and low maintenance overclocking is obtained with dual loop water cooled system. Water cooling for computers has evolved considerably over the last decade with many options available with fully self-contained kits aimed at novice users/builders.
CPUs, chipset (PCH), power regulators (VRM), and GPUs all can get very hot when overclocked. Fortunately, there are many water cooling solutions that will cover these 4 key components.
This section will NOT go into details of the 200+ BIOS/EFI settings that can be modified in order to achieve a stable overclocked profile. Every motherboard/CPU/RAM will operate differently and it would be impractical to attempt to cover every possible overclocking setting/combination.
At it’s very basic, overclocking is:
Higher frequency
More voltage
More cooling
Tuned RAM timings
Current memory modules (DDR3/DDR4) don’t heat up enough to justify water cooling , if the case is well ventilated with sufficient fans for well controlled Intake and Exhaust air flow, then memory modules should not require any special cooling.
There is some danger with overclocking such as damaging components, but in most cases a CPU will have thermal protection (assuming it’s not turned off via BIOS/EFI) which should prevent permanent damage/failure, however, proceed at your own risk with no guarantee. When overclocking always proceed with caution, if you can’t afford to write-off your CPU of choice, then don’ t risk overclocking. With that said, some users have been overclocking computers for well over 16 years and have not had a single CPU failure.
Figure 113
To monitor with a visual overlay of the selected items (i.e. FPS, Temps, etc.) make sure OSD ON (white … if gray, click on OSD OFF).
Setup monitoring of GPU/CPU frame rates, temperatures, bus loads, GPU loads, CPU loads, and more:
Figure 114
SLI dual GPU monitoring (above) – to monitored values in P3D the “Show in On-screen Display” must be enabled.
Overclocking the CPU can be approached in many ways, booting to BIOS/EFI and making the changes there, or via Manufacturer utilities that allow for adjustments directly from within the Windows OS environment with options to save overclocking profiles.
One approach is to setup a safe “boot” clock in the BIOS/EFI and then define an overclocking profile that you can manually load AFTER booting into the OS.
Below is an example of ASUS overclocking/monitoring tools (AI Suite) that can be used to setup and save overclocking profiles from within Windows OS:
Figure 117
Once a profile is saved, it’s time to start testing the profile in P3D.
Monitoring CPU, VRM (voltage regulators), and PCH (chipset) temperatures using motherboard monitor/overclocking tools should provide the most accurate readings as they tie indirectly to the motherboard manufacturers components. Most motherboard manufacturers provide these tools/utilities with motherboard purchase (also watch for updates via motherboard manufacturers website):
testing at KSEA.
Performance Performance
How to get “smooth” motion in P3D is actually not that difficult, but it does require some willingness to compromise on graphics settings and/or add-ons.
The easiest approach (but certainly NOT the only approach) to get smooth motion in P3D is to find a monitor that can operate at 30Hz and still look as good as it does at 60Hz or higher with NO mouse lag. Below is a table of the relationship between monitor frequency, limited vs.
unlimited, and FPS:
Figure 119
60 FPS would be a more desirable goal.
Figure 120