.jpg "fsx pmdg 777 free")
We recommend maximizing the window and then dragging the Virtual Size column over so that it’s right next to the CPU column so that you can easily see it. This is going to enable the column, but it will likely be at the far right of the Process Explorer display. Go to the “Process Memory” tab in the window that pops up and put a check mark next to the one called “Virtual Size” and press OK.
#FSX PMDG 777 FREE FULL#
You’re going to see a rather bewildering looking list of all the processes running on your computer with various columns full of parameter values that are constantly updating. The first thing you’re going to want to do is enable the VAS display – to do this, right click in the area where the column names are and choose “Select Columns”. Once you have it downloaded, unzip the files to a folder of your choosing and run the procexp.exe file.
#FSX PMDG 777 FREE WINDOWS 7#
There is literally no reason not to run the 64-bit version of Windows 7 on an FSX simming PC. 64-bit Windows does not have this limit and with a lot of RAM you can essentially run as many other applications outside of FSX (browser, weather apps, flight planners etc) as you want with no effect on the system. 32-bit versions of Windows can also only ever access 4GB of total physical memory, so if FSX is using 3GB itself, there’s not much there for the OS and other applications. This can be increased to 3GB for FSX through an edit to the boot environment configuration (“the 3GB switch”), but this is still 1GB lower than you’ll get with the 64-bit version of Windows and it makes both OOMs more likely and OS crashes more likely because it reduces the amount of VAS the OS itself has to work with.
In 32-bit Windows the default is a maximum of 2GB of VAS for FSX and 2GB reserved for the operating system. The reason we recommend using a 64-bit operating system like Windows 7 64-bit is due to the fact that it can give FSX.exe that entire 4GB block of VAS.
When you do the rest of the conversion math this value comes out to exactly 4 gigabytes of potentially addressable memory for a 32-bit process. The amount of VAS a 32-bit process can access can be calculated by raising the number of possible values for each bit (2) to the power of the number of bits available (32). This is why at the core a computer executes “binary” code. The mathematical limit itself comes from the definition of “32-bit” – a bit is the most basic data structure in computer science and it can have two values, a 0 or 1, which can mean all sorts of things like true or false, on or off etc. Note that VAS is *NOT* the same thing as the “virtual memory” swapfile that you can set the size of in the Windows system options – they are two very different things and having a large virtual memory swapfile does not protect you from the 4GB VAS limit.
#FSX PMDG 777 FREE SIMULATOR#
VAS is effectively a preallocation of everything the simulator can potentially access during a flight and will fluctuate over the course of using the simulator as you fly between different areas.
0 kommentar(er)
