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

**FIX** Crashing/Reboots

The place to ask for technical help with running the demo or the full game...

Post Mon Apr 16, 2007 6:00 am

From what I'm gathering on this problem, I'm begining to think it is more of
a problem with the Radeon Express 200M graphics card installed on this laptop.
On my other "working" desktop pc (a Hewlett Packard with a P4 & Updated 82845G->82845G/GL/GE/PE/GV Intel Graphics chipset) everything is working fine.
It is my understanding the a lot of people who had the 82845G chipset were
experiencing problems with Freelancer. The Video Chipset update addressed
this issue. (Video BIOS Version 2897)

Post Mon Apr 16, 2007 8:37 am

Intel users will be happy to know that the latest Hardware Update released on the =EOA= website has all working Intel IGP chipsets added to it and it includes the texture corruption fix for the i810 and i815 series chipsets.

Post Mon Apr 16, 2007 2:54 pm

Rankor I never had a problem with my 845's, and I played FL for a good 6 months before I even got internet access, but there again I am using the laptop version.

**shuffles off with a new headache**

Post Mon Apr 16, 2007 5:00 pm

This card I have on the particular laptop is a Radeon Express 200 M.
Although two of the problem models are working fine on the Intel Chipset based pc (the "working" desktop) ...
certain texture combinations seem to cause problems with the Express.
Such as the nomad_fx.txm used as the sails you see on the HIspanola.
That screenshot was taken off the "working" pc.
(Help requests thread: ... c_id=33096 )
The exact same model seems to be causing a CTD on this laptop.

Something else I am also wondering about it the difference between the SDK 1.3 and SDK 1.5 ... The Working Pc has the 1.3 in use on it where the Laptop has the 1.5 in use. You don't suppose that has anything to do with you?

Edited by - Rankor on 4/16/2007 6:05:49 PM

Post Mon Apr 16, 2007 6:16 pm

Fixing that Radeon Express 200M problem would require a lot of experimenting with the flconfigdatabase.txt file. Try the options like TextureOffset one by one to see if there is any improvement and post your results here.

The difference between 1.3 and 1.5 is that they are not compatible. You aren't supposed to be using any version of the SDK as a patch anyway. Grab the QuickFix Patch.

Post Wed Apr 18, 2007 2:54 am

Moved the question to the EOA forums

Edited by - Bejaymac on 4/18/2007 4:10:33 AM

Post Thu Apr 19, 2007 5:15 pm

I've annotated the card in the FL config database, but as far as working on the texture offsets is still yet just a little beyond me at present.

The only reason I haven't used the QuickFix Patch is to keep my stereo settings for the audio. I would use it IF it didn't disable 3d sound. When I'm using a headset, the 3d sound becomes apparent in many cases and I like that added depth.
Also, I'm quite far into this particular mod I've been working on and would hate like hell to dump it all to install the patch.

Post Thu Apr 19, 2007 8:46 pm

You can re-enable 3d sound right in the game's options menu.

Post Fri Apr 20, 2007 2:08 pm

Oh, that's cool. So its not greyed out then?

Post Sat Apr 21, 2007 3:28 pm

All the patch does is set 3D Audio to be off by default. You can turn it back on at any time.

Post Sun Apr 22, 2007 6:20 pm

I don't know if it's just me, but... Last time I tried running Freelancer (about six months ago), it ran perfectly. Recently I installed a new AMD64 X2 4200+, installed the proper patches and registry entries, and got the dual-core optimizer. After I got all that done, I had a feeling like I wanted to try Freelancer again. So, I reinstalled it, got the patches installed... and the game crashes right after the main 'Freelancer' image comes up after the intro movies.

Just checked my error log, this is the last line with no other errors.

E:\FL\Scratch\Source\Common\Archetype.cpp(60) : *** ERROR: ArchDB::Get(2401461066) failed

Nevermind... ..weird fix. I needed to install the game on my system drive for it to run properly.

Edited by - Interim on 4/23/2007 4:06:22 AM

Post Tue Jun 12, 2007 7:07 pm

didn't work for me

Post Tue Jul 10, 2007 9:01 am

Freelancer isn't working for me either. It was screwed up, so I reinstalled, a clean install, although some files had got tangled up in shortcuts and wouldn't delete properly. Now it crashes after movies. I deleted my saved games and I think thats my real problem, but do I need to reninstall again?

Post Wed Oct 31, 2007 9:45 am

Wow.. Over two years since this thread was open and this problem still doesn't have a solution..

The random crashes/reboots are very frustrating and will ultimately be the reason that I stop playing the game, which is very unfortunate because I really love this game! However, I don't love when I've made a lot of progress, the game crashes, and I lose everything.

I (as well as many others seemingly) have tried the "Disable 3D Sound" fix, but have found very quickly that it does NOT fix things at all. I have also installed the QuickFix patch but that has also not fixed the problem.

I consider this to be a fairly serious issue with the game and I am quite surprised over the course of all these years, this problem has not been fixed. Also, I am more inclined to believe that this is a bug in the game and not directly related to specific hardware since there have been a huge variety of users with different hardware that get this same problem.

If anybody can offer any insight as to how to stop these random crashes/reboots, it would be greatly appreciated. This is truly an amazing game, and many of us would like to actually play it!!

Post Wed Oct 31, 2007 11:32 am

Long shot:

Did you try setting the exe to run in Windows 2000 compatibility mode? Technically the game should run in Windows XP but I know it ran quite well under my Win2K install back when I still used that OS.

Return to Freelancer Technical Issues