True Combat: Elite (OpenGL Issue)

Hey guys,

I’ve just moved from WIndows 7 to openSUSE and first of all I want to thank you for this great distro, I’ve tried some other distros but this one was the most user friendly I tested, specially for KDE users.

So, I’m having some trouble installing True Combat: Elite on my computer, I can run Enemy Territory just fine, but when it comes to True Combat: Elite I get the following terminal output:

xpl0ad3r@linux-n8hm:/usr/local/games/enemy-territory> sudo et +set fs_game tcetest
root’s password:
ET 2.60 linux-i386 Mar 10 2005
----- FS_Startup -----
Current search path:
/root/.etwolf/tcetest
/usr/local/games/enemy-territory/tcetest/pak4.pk3 (113 files)
/usr/local/games/enemy-territory/tcetest/pak3.pk3 (411 files)
/usr/local/games/enemy-territory/tcetest/pak2.pk3 (2066 files)
/usr/local/games/enemy-territory/tcetest/pak1.pk3 (1869 files)
/usr/local/games/enemy-territory/tcetest/pak0.pk3 (728 files)
/usr/local/games/enemy-territory/tcetest/mp_bin.pk3 (6 files)
/usr/local/games/enemy-territory/tcetest
/root/.etwolf/etmain
/usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files)
/usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files)
/usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files)
/usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files)
/usr/local/games/enemy-territory/etmain


8956 files in pk3 files
execing default.cfg
couldn’t exec language.cfg
execing autoexec.cfg
com_zoneMegs will be changed upon restarting.
Hunk_Clear: reset the hunk ok

------- Input Initialization -------
Joystick is not active.

Bypassing CD checks
----- Client Initialization -----
----- Initializing Renderer ----

----- Client Initialization Complete -----
----- R_Init -----
…loading libGL.so.1: Initializing OpenGL display
…setting mode 4: 800 600
Error couldn’t open the X display
…WARNING: could not set the given mode (4)
Initializing OpenGL display
…setting mode 3: 640 480
Error couldn’t open the X display
…WARNING: could not set the given mode (3)
----- CL_Shutdown -----
RE_Shutdown( 1 )

----- CL_Shutdown -----

Sys_Error: GLimp_Init() - could not load OpenGL subsystem

My Computer specs:
http://img845.imageshack.us/img845/8190/sysinfo.jpg

Drivers Installed
http://img825.imageshack.us/img825/9922/driverso.jpg

Any help?

So I am not a gamer, but wonder if you were to load a newer version of the nVIDIA driver and include the 32 openGL files from the proprietary driver, if that might help? The latest driver is 280.13 and you don’t get the 32 bit question unless you have installed the driver the hard way. You would need to remove all four nvidia files you have installed through YaST and the nVIDIA repository. It just depends on how bad you want to run that game. Here are links to my blogs on the subject. Good Luck…

http://forums.opensuse.org/blogs/jdmcdaniel3/installing-nvidia-video-driver-hard-way-29/

LNVHW - Load NVIDIA (driver the) Hard Way from runlevel 3 - Version 1.10 - Blogs - openSUSE Forums

Thank You,

Ok, now I can’t see the model at “sysinfo:”, but at least the 3D driver shows: “NVIDIA 280.13”.

Still, my graphic card model is detected by NVIDIA X Server Settings:
http://img7.imageshack.us/img7/8396/nvidiap.jpg

Just in case, here are the files I edited in order to install the drivers:

/boot/grub/menu.lst

title Desktop -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,7)
    kernel /boot/vmlinuz-2.6.37.6-0.7-desktop root=/dev/disk/by-id/ata-ST3320620AS_9QF6FLD5-part8 resume=/dev/disk/by-id/ata-ST3320620AS_9QF6FLD5-part7 splash=silent quiet showopts vga=0x31a nomodeset
    initrd /boot/initrd-2.6.37.6-0.7-desktop

/etc/sysconfig/kernel

NO_KMS_IN_INITRD="yes"

Xpl0ad3r Ok, now I can’t see the model at “sysinfo:”, but at least the 3D driver shows: “NVIDIA 280.13”.

So did you upgrade the driver through YaST or load it the hard way as explained in my blogs? Did the driver upgrade you did change anything with the game in question?

Thank You,

Well, your blog lead me to this way:
SDB:NVIDIA the hard way - openSUSE

So, I’ve followed all the steps and still nothing, same problem with OpenGL.

There was something about “LNVHW” but since it wasn’t on that guide I thought it wouldn’t be necessary at all…

Well, your blog lead me to this way:
SDB:NVIDIA the hard way - openSUSE

So, I’ve followed all the steps and still nothing, same problem with OpenGL.

There was something about “LNVHW” but since it wasn’t on that guide I thought it wouldn’t be necessary at all…

So when you installed the nVIDIA driver the hard way, did you answer the question about including the 32 bit openGL Library in the affirmative?

Thank You,

Yes I did.

Perhaps it’s something to do with 3d Acceleration? (which shouldn’t be enabled by default when installing the proprietary drivers?)

Yes I did.

Perhaps it’s something to do with 3d Acceleration? (which shouldn’t be enabled by default when installing the proprietary drivers?)

So as far as I know, Hardware Acceleration is turned on by default. Don’t confuse what the nVIDIA driver provides with your desktop graphic setup. Have you looked at the options in the nvidia-settings application to see if it can help? Besides me, have you spoke with any gamers to see if they have used this program before under openSUSE?

Thank You,

Yeah I looked in the options but I couldn’t find anything that relevant about this…

No, I’ll try to ask on their forums too…

Anyway, there’s anything else I could do to check if my driver is properly installed? I mean, isn’t it weird that it doesn’t show the driver model at “sysinfo:/” ?

Unless a modification is made to show the video card model, the info is blank and I think unimportant since nvidia-settings knows the card chipset. Here is mine without telling it the model.

                 Display Info
    Vendor:  nVidia Corporation
     Model:
  2D driver:  nvidia
  3D driver:  NVIDIA 280.13

I happen to have a GTX 560, but I don’t think the name shown in sysinfo is needed.

Thank You,

Oh I thought it was just me.

Ok, thank you for the support. :slight_smile:

Perhaps I am being simplistic but why do you think that something wrong with the video driver is the problem when Enemy Territory itself runs?

In any case I noticed these lines in your output:

…loading libGL.so.1: Initializing OpenGL display
…setting mode 4: 800 600
Error couldn’t open the X display
…WARNING: could not set the given mode (4)
Initializing OpenGL display
…setting mode 3: 640 480
Error couldn’t open the X display
…WARNING: could not set the given mode (3)
----- CL_Shutdown -----

Is it possible that your desktop resolution and the resolution the game is set to run at aren’t playing nice with each other? I’ve had that keep certain games from running for me in
my systems especially if the desktop resolution was less than the games, while other games didn’t seem to care.

Because as it says, it’s OpenGL related and since and I tried to reinstall it already with no success.

Yeah, I tried that already, I have my desktop resolution always at the max value… =/

I just noticed that after trying the “hard way” of nvidia installation I can’t execute commands like:

sudo kwrite test.txt

Because:

kwrite: cannot connect to X server

Maybe that’s the cause of my problem…
I’m not sure why it’s giving me that error since I did it just like as described in the wiki:

rcxdm start

So, I don’t know the problem, but in the case of starting kwrite as root with a terminal session open, you would use the following command:

/usr/bin/dbus-launch kdesu kwrite

If you are starting kwrite from a bash script as root, but the terminal window is not displayed then use:

kdesu kwrite

Not all programs that run as a desktop window like to be started from a terminal session. If you get this kind of error from a program started from terminal:

kwrite: cannot connect to X server

And the program is written to run in a desktop window, like kwrite, consider adding in the command in front:

/usr/bin/dbus-launch

Programs that run in a window, again like kwrite need to use kdesu to be run as root since they are desktop based and not terminal based. Its possible sometime to use sudo to run a second batch file, where sudo works OK which then launches kwrite as root, but you must play around with such a combination to get the correct sequence that works.

Thank you,