Important Message

You are browsing the archived Lancers Reactor forums. You cannot register or login.
The content may be outdated and links may not be functional.


To get the latest in Freelancer news, mods, modding and downloads, go to
The-Starport

Possible crash fix for SL (not including miss 13/22/23)

This is a free discussion forum on Starlancer. This is the place to discuss general issues concerning StarLancer.

Post Sun Mar 06, 2005 6:49 am

Possible crash fix for SL (not including miss 13/22/23)

Well i finally got around to playing SL again after many years and immediately found out why i stopped. The random crashes with eax enabled and on the missions above (think it was those ones) random crashes no matter what i tried.

After much frustration i decided to try updating some of the dlls that the game uses as ive found that this has fixed things in games before. As it was mostly a sound related problem i decided to check around for sound related .dll files.

The mss32.dll file in the starlancer is something to do with the sound system and it reported a version of 6.0a and told me it was owned by miles sound or something like that. After looking on their site it seems there were some crash bugs with this version of the dll so i went and grabbed copies of the files from other games i had installed.

The results were that anything after v6.0m dosent work with starlancer but 6.0m does and is in HL1 (well the last non steam version anyway as thats all i have).

I havent tested this thoroughly because ive been on mission 13 for a while trying to get through it without it crashing on me (apparently that ones graphics related) but ive played a few of the earlier missions and it seems to have stopped crashing in those with eax enabled.

Could other people test this and see if this finally fixes the problem? better late than never

oh and if it makes any difference the sound card ive used it with is a SB audigy 2

EDIT: damn still get random crashes guess i was just lucky for a while back to the drawing board

Edited by - eaterofpies on 3/6/2005 3:15:27 PM

Post Mon Mar 07, 2005 3:32 pm

This one is actually pretty simple, but why it's the case, I don't know. Simply turn off any hardware acceleration and it should stop most CTD's. Never found a fix for this, and Warthog never patched it.

Post Mon Mar 07, 2005 4:43 pm

yeah i know you can turn it off but it just sounds better with it on . shame about the lack of patch. im suprised they havent open sourced it. if they cant be bothered to support it i would have thought they would have let someone else.

well no doubt they have their reasons.

Post Mon Mar 07, 2005 8:08 pm

Probably because they're still hoping Microsoft will make a Starlancer 2. All though, my opinion of Microsoft radically improved when they released the Source Code to Allegiance.

Post Tue Mar 08, 2005 9:41 am

i have to admit when i heard that i was shocked and stunned

Post Thu Mar 10, 2005 6:16 pm

Well, ancient history now. Believe me, we tried. The game simply didn't sell as well as thought, and Warthog never admitted that the 3D hardware was an issue, so it never got fixed. MS ownes the game, but Warthog ownes the code, and they kept saying it was driver issues. A shame it never got resolved, but the games still plays well and even sounds pretty good without the 3D effects. Love the music in the game.

Return to Starlancer Discussion