Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: bigcheese on November 20, 2008, 02:47:46 am
-
Hi,
Just got FS2 from GOG but when I try and run using either the launcher or FS2.exe it crashes with the following error in the errorlog file
FS2 caused an Access Violation in module FS2.exe at 001b:005b1f90.
Exception handler called in Freespace 2 Main Thread.
Error occurred at 11/17/2008 12:33:14.
C:program filesgog.comfreespace 2FS2.exe, run by ....
1 processor(s), type 586.
1016 MBytes physical memory.
Read from location 000000ac caused an access violation.
I have DirectX 9.0c(4.09.0000.0904) drivers installed but I have a rather old system which uses S3 prosvage DDR integrated graphics chipset. The FS2 demo worked fine so I thought I may be in luck, my DxDiag system info is below. Any help would be great.
System Information
------------------
Time of this report: 11/17/2008, 16:11:08
Machine name: SUNRISE
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.080814-1236)
Language: English (Regional Setting: English)
System Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
System Model: KM266-8235
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Duron(tm) processor, MMX, 3DNow, ~1.6GHz
Memory: 1016MB RAM
Page File: 236MB used, 2208MB available
Windows Dir: C:WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
---------------
Display Devices
---------------
Card name: S3 Graphics ProSavageDDR
Manufacturer: S3 Graphics, Inc.
Chip type: S3 ProSavage DDR
DAC type: S3 SDAC
Device Key: EnumPCIVEN_5333&DEV_8D04&SUBSYS_73891462&REV_00
Display Memory: 8.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: s3gnb.dll
Driver Version: 6.14.0010.0033 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/13/2004 13:42:08, 401280 bytes
-
S3 prosvage DDR integrated graphics chipset
There's your culprit. No one here has ever had any luck with S3 graphics cards. Your best option is to invest into a new GPU/whole computer.
C:program filesgog.comfreespace 2FS2.exe
:wtf: I hope that one is actually C:\Program Files\gog.com\freespace2\ Even then I'm not sure about how the game engine reacts to periods in folder names.
You can, of course, attempt to find the latest drivers for your graphics card. Then, you might have luck using the 3.6.9 FSO build and selecting Direct3D from the Launcher's Video tab. But no guarantees. And even then it will sort of suck, since Direct3D isn't supported by the SCP group anymore.
-
OK I was afraid of that but knew I was stretching things, any thoughts on why the FS2 demo worked fine but the full retail does not?
-
any thoughts on why the FS2 demo worked fine but the full retail does not?
'fraid not. I'm still not completely aware of the things GOG has done to the FS2 they're selling. If they've fiddled with the game engine to make sure newer systems can run it, it could be that they've simultaneously pissed on backwards compatibility.
I'm concidering the solution that one of us (like me) sends you an old version of both the retail Launcher and FS2.exe, assuming that it would work that way without further hassle. Normally distributing retail files here would probably end up in beating the distributor with his own legs, but since you already bought the game from GOG and have problems getting it to run, I don't see anything wrong with it. But just to be sure, I'm going to wait for some time so that the powers that be have a chance to react and stop me if they do not approve.
-
i don't know if the FS2 engine likes the game data placed in a directory with a '.' in it. Try renaming to C:\program files\gog\freespace2\
-
i don't know if the FS2 engine likes the game data placed in a directory with a '.' in it. Try renaming to C:\program files\gog\freespace2\
I'd say reinstall into a folder such as the normal retail: C:\Games\Freespace2\
-
Yes, the default one.
-
Actually, there are many choices. One must only keep in mind that My Documents and the desktop are a no-no. As well as overly long paths, if I'm not mistaken. C:\Games\freespace2 works. So does C:\Program Files\freespace2.
-
Actually, there are many choices. One must only keep in mind that My Documents and the desktop are a no-no. As well as overly long paths, if I'm not mistaken. C:\Games\freespace2 works. So does C:\Program Files\freespace2.
The former definitely works, but if I remember correctly, file names with spaces cause problems. Again, I'd say just C:\Games\Freespace2\ is your best choice.
-
if I remember correctly, file names with spaces cause problems.
That particular issue was solved many builds ago.
-
if I remember correctly, file names with spaces cause problems.
That particular issue was solved many builds ago.
But that issue may not be solved with retail EXEs.
-
Hmm. Touché. Pardon me for failing to notice that particular detail.
-
OK thanks very much for those suggestions, I'm travelling on vacation for the next month and will try a few fixes when I get back home. I feel it has to be some kind of bad programming/bug because other older(1997-2002) graphics intensive games have worked really well e.g Half-Life 1,Deus Ex, Dungeon Siege, Baulder's Gate 2,Longest Journey etc.