Michael Carter
03-30-2009, 11:02 PM
I finally have two monitors hooked up to the client computer. The view out the forward quarters was fantastic. It adds quite a bit of immersion.
It took awhile to configure the second monitor, but before long, and on the second try it was working well.
Well, it was working. My frame rate dropped to under 6 at Mega-Frankfurt even with all sliders pulled back to about 50% or so, give or take. After getting away from the airport environment the frame rate went back up to 24 fps. All was going along well until crossing LAM for the 27 arrival at Mega-Heathrow.
The server (the good computer) crashed with an out of memory (address space) error.
I have just recently been able to comprehend this error and how it can occur. The two hours I spent on the ground at Mega-Frankfurt probably had at least a little to do with what happened. There were warning signs too.
After pushing out of A19, the server stumbled several times with frame rates going as low as 6-9 fps during the long taxi down to 07L at Frankfurt. After a few seconds it would quickly jump back up to 24 fps.
There is a configuration trick to try called the 3GB switch which allocates more address space for running applications than the 2GB that is normally allocated for processes and programs. This cuts into the available 2GB address space for the operating system, so it is a compromise.
This is only the second time I experienced this error, but on both occasions, a longer than normal time was spent in a high detail address draining scenery area before the flight.
I thought about changing to the Win XP Pro X64 version, but it's not worth the hassle.
I've learned that this error really does not have anything to do with the amount of physical or virtual memory available, but instead the amount of address space to place the data into memory. You can have 100 million meg, but if the address space to place the data into the 100 MMB of memory isn't there, the crash results.
It took awhile to configure the second monitor, but before long, and on the second try it was working well.
Well, it was working. My frame rate dropped to under 6 at Mega-Frankfurt even with all sliders pulled back to about 50% or so, give or take. After getting away from the airport environment the frame rate went back up to 24 fps. All was going along well until crossing LAM for the 27 arrival at Mega-Heathrow.
The server (the good computer) crashed with an out of memory (address space) error.
I have just recently been able to comprehend this error and how it can occur. The two hours I spent on the ground at Mega-Frankfurt probably had at least a little to do with what happened. There were warning signs too.
After pushing out of A19, the server stumbled several times with frame rates going as low as 6-9 fps during the long taxi down to 07L at Frankfurt. After a few seconds it would quickly jump back up to 24 fps.
There is a configuration trick to try called the 3GB switch which allocates more address space for running applications than the 2GB that is normally allocated for processes and programs. This cuts into the available 2GB address space for the operating system, so it is a compromise.
This is only the second time I experienced this error, but on both occasions, a longer than normal time was spent in a high detail address draining scenery area before the flight.
I thought about changing to the Win XP Pro X64 version, but it's not worth the hassle.
I've learned that this error really does not have anything to do with the amount of physical or virtual memory available, but instead the amount of address space to place the data into memory. You can have 100 million meg, but if the address space to place the data into the 100 MMB of memory isn't there, the crash results.