Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Triple Ace on November 30, 2004, 05:46:13 pm
-
I've tried all the newer builds and I get the same result. If I go to play with a mod or a user created campaign the game freezes when I click the hangar doors to start. It does not even get to the loading screen. Also, I did try the mod command in the launcher.
-
What build are you using?
Did you try creating a new pilot?
-
Newest build and I am using a new pilot.
-
May be you should select the new campaign in the campaign-screen first?
-
and then make a new pilot, again, after reselecting the new campaign
-
I've done that but it still freezes.
-
specs?
-
1.6 ghz athlon, 512 ram, 128 mb geforce 5700 le, 40 gb hard drive. Its a pretty beefy system.
-
beefy? :wtf:
-
Originally posted by Triple Ace
1.6 ghz athlon, 512 ram, 128 mb geforce 5700 le, 40 gb hard drive. Its a pretty beefy system.
Erk... Thats not exactly high end...
You're sure you installed it correctly to use the -mod?
-
Its high end for poor people and yes I did use -mod.
-
Would you be able to post your entire command line?
-
Sure I'll copy it now. C:\FreeSpace2\fs2_open_r.exe -spec -glow -pcx32 -jpgtga
-
pcx32... *shudders*
-
I meant the entire command line, including the -mod selection.
-
Get rid of pcx32 - AFAIK almost non of the optimized effects need it and it is a real drain on your RAM.
-
You think that might be the problem?
-
Ok the pcx32 command was not the problem so here is my command line again, C:\FreeSpace2\fs2_open_r.exe -spec -glow -jpgtga -mod (any mod).
-
I figured it out. It was the kpack vp that was causing the problem.
-
My concern about the -mod part of the command line was that spaces in the mod directory can cause issues with it. I needed to know if this was the issue you were having.
Later!
-
As soon as I removed the kpack vp it worked fine.
-
Odd. I wonder why it would do that with mods but not the main campaign.