Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: SpardaSon21 on August 09, 2010, 12:49:55 pm

Title: Unable to Run FS2
Post by: SpardaSon21 on August 09, 2010, 12:49:55 pm
I've freshly installed FS2 from GoG, and then used Turey's installer to install everything except the 3.6.12 MediaVPs and 3.6.12 since those weren't available options, but I installed those manually, including Launcher 5.5f, and of course OpenAL.  Other than that I haven't done anything.  If I try to start retail FS2, it won't load at all.  If I use a 3.6.12r build, Windows gives me an error message about FreeSpace 2 shutting down and the send/don't send choices.  If I use a debug build a window pops up giving me this error and asks to click OK to break into debugger or cancel to exit, and no, no fs2_open.log is produced:
Code: [Select]
ERANGE: String error. Please Report.
Trying to put into 32 byte buffer:
ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ.
<no module>! KiFastSystemCallRet
<no module>! WaitForSingleObject + 18 bytes
<no module>! SCP_DumpStack + 354 bytes
<no module>! Error + 229 bytes
<no module>! scp_strcpy_s + 297 bytes
<no module>! scp_strcpy_s<32> + 53 bytes
<no module>! cf_search_root_pack + 892 bytes
<no module>! cf_build_file_list + 131 bytes
<no module>! cf_build_secondary_filelist + 166 bytes
<no module>! cfile_init + 398 bytes
<no module>! game_init + 341 bytes
<no module>! game_main + 519 bytes
<no module>! WinMain + 330 bytes
<no module>! __tmainCRTStartup + 358 bytes
<no module>! WinMainCRTStartup + 15 bytes
<no module>! RegisterWaitForInputIdle + 73 bytes
Title: Re: Unable to Run FS2
Post by: General Battuta on August 09, 2010, 12:52:23 pm
Move your FS2 install to C:/Games/FreeSpace2
Title: Re: Unable to Run FS2
Post by: SpardaSon21 on August 09, 2010, 02:25:05 pm
My FS2 installation was in C:\Games\FreeSpace 2, so I just re-named the folder to FreeSpace2 and got the same error.
Title: Re: Unable to Run FS2
Post by: FUBAR-BDHR on August 09, 2010, 02:32:53 pm
Do you have any files in any of the directories in or under your FS2 directory that have a file length > 31 characters including the . and extension?  If so that can cause this. 
Title: Re: Unable to Run FS2
Post by: SpardaSon21 on August 09, 2010, 02:45:12 pm
What do you mean by file length, the file path that goes "C:\Games\FreeSpace2\<folder>\<filename.xxx>"?
Title: Re: Unable to Run FS2
Post by: Jeff Vader on August 09, 2010, 02:59:04 pm
What do you mean by file length, the file path that goes "C:\Games\FreeSpace2\<folder>\<filename.xxx>"?
Yes.
Title: Re: Unable to Run FS2
Post by: SpardaSon21 on August 09, 2010, 03:12:02 pm
Yeah, I've got a lot of files with a file path longer than 31 characters.
Spoiler:
C:\Games\FreeSpace2\DEM - Interlude\DEM - Interlude.vp
That file path right there is around 50 characters, so extend that to all the mods I have, and well, it doesn't look good, unless the length only starts counting once I hit the FreeSpace2 folder.
Title: Re: Unable to Run FS2
Post by: Jeff Vader on August 09, 2010, 03:16:04 pm
Waitwaitwait. Beer occasionally causes errors in thinking.

If your FS2 is in C:\Games\FreeSpace2\ , there shouldn't be any problems, unless, for example, your pilot files have insanely long names.
Title: Re: Unable to Run FS2
Post by: SpardaSon21 on August 09, 2010, 03:24:33 pm
Okay, I fixed the issue.  I thought my fs2_open.log file was going to be in the root folder, but it was actually in the data folder, so I didn't know I had one.  I opened it up, and found that FS2 crapped out after trying to load one of the multi-mission .vp files which Turey's installer placed in my root folder, and it may have been corrupted, and those files probably shouldn't have been there in any case.  I moved the two of them to their own mod folder, and now FS2 loads.  Thanks for your responses guys.
Title: Re: Unable to Run FS2
Post by: Jeff Vader on August 09, 2010, 03:27:56 pm
The multi files actually can be in \freespace2\ , but you only need them if you want to play multiplayer. But yes, if a file is broken, it will freeze up the entire game (or according to some people, just take a ****load of time to start the game up), so it is best to either remove them or move them somewhere where they aren't used by the game.