Originally posted by Goober5000
PLEASE NOTE: The "engine failure" bug is known and has been fixed in this build:
http://fs2source.warpcore.org/exes/latest/fs2_open_C06222004.zip
We now return you to your regularly scheduled thread.
------------------------------------------------------------------------
Sorry to report a bug in the forum, but I just couldn't get the bug report page to work.
Now, using the above mentioned build, I get the following error after a maximum of 3 missions played in a row, along with a "Virtual Memory Too Low" notification from Windows.
Error: Out of memory. Try closing down other applications, increasing your
virtual memory size, or installing more physical RAM.
File:.\globalincs\windebug.cpp
Line: 1474
Call stack:
------------------------------------------------------------------
fs2_open_ex.exe 00465aa0()
fs2_open_ex.exe 00465f0d()
fs2_open_ex.exe 00466491()
fs2_open_ex.exe 004690c8()
fs2_open_ex.exe 00466746()
fs2_open_ex.exe 004696f8()
fs2_open_ex.exe 004c5979()
fs2_open_ex.exe 005fd4cb()
fs2_open_ex.exe 00602de9()
fs2_open_ex.exe 0060464c()
fs2_open_ex.exe 0060489d()
fs2_open_ex.exe 005b751f()
fs2_open_ex.exe 005d2ff5()
fs2_open_ex.exe 00659a03()
fs2_open_ex.exe 0064884b()
------------------------------------------------------------------ I guess this ought to happen when running FreeSpace with 16 MB of RAM, but I currently have 256 DDR, and 128 VRAM. Moreover, there are major slowdowns in-mission, when ships explode (yes, I am using the hi-res explosions, so that's understandable), and when any ships exit subspace.
My command line for running FreeSpace is:
D:\Games\FreeSpace2\fs2_open_ex.exe -spec -glow -pcx32 -jpgtga -d3dmipmap -phreak -ship_choice_3d -2d_poof -snd_preload I'm running Windows XP SP1, Detonator v61.77, on a Duron 850 MHz, 256 DDR, MSI nForce 1, GeForce FX 5200. Pretty low-end, I know, but considering I just finished Splinter Cell 2 on it on best graphics settings without slowdowns, I guess FSSCP ought to run just fine...