Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Unknown Target on January 05, 2005, 12:12:16 pm

Title: Mission-critical bug.
Post by: Unknown Target on January 05, 2005, 12:12:16 pm
System:

Windows XP
512 MB of RAM
Geforce 4 Ti4600

FS2 Open version: 3.6.5
Features enabled: Everything except cell shading.


Hey all, I just installed two new campaigns (culled from the Vwatch archives, because I was bored). However, when I tried to run Freespace 2, it boots up normally (from the launcher), gets the loading screen, then gets to the pilot selection menu. However, afterwards when I click "accept", I get an error that says I am out of memory, so I restarted. Now I dfo the same thing, except I get no error, just a freeze, and I have to Alt-F4 out of the program.

Any help?


EDIT: Upon removing everything in my Missions folder, I now get the same error as before:


Error: Out of memory.  Try closing down other applications, increasing your
virtual memory size, or installing more physical RAM.

File:U:\src\cvs\fs2_open.testing\code\GlobalIncs\WinDebug.cpp
Line: 1495

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
Title: Mission-critical bug.
Post by: Black Wolf on January 05, 2005, 01:27:36 pm
Have you tried closing down other applications, increasing your virtual memory size, or installing more physical RAM?
Title: Mission-critical bug.
Post by: Unknown Target on January 05, 2005, 12:37:56 pm
Done, done, and done. It was working about 30 seconds before, and then it just stopped.

Now it's actually working....all I did was uncheck and recheck the graphics options. Maybe this warrants further investigation?
Title: Mission-critical bug.
Post by: DrunkenPirate on January 05, 2005, 05:24:51 pm
I had this once a while back before i reformatted my system, the only way I could effectively fix it was reinstall/patch to 1.2 and reinstall SCP.
Title: Mission-critical bug.
Post by: WMCoolmon on January 05, 2005, 05:41:55 pm
It might just be that memory isn't getting allocated fast enough. I'm not sure how Windows deals with memory fragmentation.

Windows also keeps old programs in memory until that memory is used, so maybe un-using that memory slowed down the allocation enough that it returned as false.
Title: Mission-critical bug.
Post by: Unknown Target on January 05, 2005, 06:05:53 pm
Is there any way that FSOpens memory usage can be reduced? It's an insane amount of memory for the program to use.
Title: Mission-critical bug.
Post by: Bobboau on January 06, 2005, 02:00:59 am
especaly if your foolish enough to enable everything except cell shading on a 512MB system
Title: Mission-critical bug.
Post by: Unknown Target on January 06, 2005, 01:07:56 pm
Worked fine when I had 256 MB.

Half Life 2 and Doom 3 runs fine on the same system, with most details turned up all the way (Doom 3 is turned up 90%, with 1024 by 768 resolution, Half Life 2 is pretty much at 100%, at 800 by 600 resolution). Freespace 2 shouldn't choke my system like it does.
Title: Mission-critical bug.
Post by: WMCoolmon on January 06, 2005, 05:40:03 pm
HL2 probably uses compressed textures...have you tried pcx2dds?