|
|
#1 | |
|
Registered User
|
I have a laptop with a GeForce4 420 Go, and SuSE 8.2. I have installed the demo of Return to the Castle Wolfenstein (wolfspdemo-linux-1.1b.x86.run).
After installing, I run the wolfspdemo and I am able to see the first screen and browse through all the options. But when I try to play the game, right on the loading stage where the image of "Office of Secret Actions" and the message "Please wait..." appears, the program crashes and exits. Apparently, the console messages don't tell anything about what went wrong: LOADING... - game media done LOADING... flamechunks LOADING... clients LOADING... WolfPlayer trying fonts/bigFont.TGA... UI menu load time = 38 milli seconds Received signal 11, exiting... Shutdown tty console I have successfully played this game on other NVidia cards (TNT2, GeForce2 and GeForce4). And I am able to play Unreal Tournment 2003 on this same system. Does GeForce4 420 Go have any incompatibility with RTCW? Has anybody been able to play RTCW with this card? |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Oct 2003
Posts: 4
|
I have the exact same problem you describe. I was wondering if anyone else had experienced this problem. I am currently running an FX go5600.
|
|
|
|
|
|
|
#3 | |
|
Geforce 8800 GTS 512
Join Date: Nov 2002
Location: Australia
Posts: 396
|
Quote:
As they usually fix some problems relating to OpenGL. AS the windows based version uses Directx. Wolf |
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Sep 2002
Posts: 59
|
Quote:
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Oct 2003
Posts: 4
|
Damn! Damn! Damn!!!! I can't figure out what the hell is wrong!!! I have found others on the net that have the same problem as well. I have the latest updates to RTCW. I even recompiled it with the SDK. The game works fine all the way up to the skill level selection. After that I get a screen. It says loading at the bottom. The program exits with a signal 11. I don't think this is a driver problem though. It's probably something very simple. I can't even imagine what it is. I don't believe it is a problem with glibc. I don't think it's a hardware problem either. I also considered wrong permissions somewhere. I checked that's not it. I've wasted to much F***ing time on this
If anyone can give me a fix I would greatly appreciate it. |
|
|
|
![]() |
| Thread Tools | |
|
|