nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   2 Questions, OpenGL and UT2003 (http://www.nvnews.net/vbulletin/showthread.php?t=7097)

njt1982 02-03-03 07:15 PM

2 Questions, OpenGL and UT2003
 
Firstly, I have installed the Nvidia drivers version 4191 sucseffully. I play Quake III and my FPS rarely drops below 90. Even the Tux game packaged with Red Hate 8 works nice! ;-)

Anyways, When i goto the display settings the Hardware Acceleration is greyed out. When I compiled up Wine, it tells me that OpenGL isn't available. This confuses me, because I could've SWORN the Quake 3 and TuxRacer use OpenGL. In fact, I KNOW they do because I tried to play TuxRacer with the standard Red Hat Drivers (nv ones, not nvidia) and it ran at less than 1fps. Has anyone had this problem and, more importantly, does anyone know a fix?!

Secondly, how do you play UT2003 in Linux? I have a windows version - but not one I bought specifically for Linux. Is it like Quake 3 where you install a patch and dump a pak file or do you have to have a special version?

Anyways, Thanx for ANY help!

Nick

Budious 02-04-03 02:53 PM

The linux installer for UT2003 in on the third cd of the US retail version, or so I've heard from friends. I haven't bought it yet.

bwkaz 02-04-03 03:33 PM

In Display Settings, HW Acceleration is grayed out because that program doesn't understand how the nVidia drivers work. So it won't let you enable acceleration with it.

This is actually a good thing, because if it did let you select it, it would actually disable hundreds of working desktops when people clicked it. :)

Anyway, since TuxRacer runs, you do indeed have OpenGL, but Wine needs a bit more than that. Wine requires some headers that binary installations of TuxRacer don't, that you may or may not have. Check the output of wine's configure script for some hints on which files you need to get to fix that one. Probably GL/gl<something>.h. Also, the config.log file that the configure script creates might have some clue as to what's going on -- whenever a test fails, the config.log gets a copy of the failed program, plus the command output.

There is only one UT2003 version, and it contains both Linux and Windows clients (though that isn't advertised; it's a shame, but the box art was already being printed when the Linux client made it onto the CDs). I've got it too; the way I would set it up is do an export SETUP_CDROM=/mnt/cdrom (but change this if your CD drive is mounted somewhere other than /mnt/cdrom), then from the same shell session, with CD 3 in the drive, do a mount /mnt/cdrom && /mnt/cdrom/linux_install.sh. This will first mount the disk, then run the installer.

The export SETUP_CDROM bit is so that the UT setup stops chugging at your floppy drive thinking that that's where it should get the setup info from. For some reason, it's not great at detecting which mount point is your CD drive. Other than that, though, it works pretty well.

Once you've installed it, then you're going to want to run loki_update as whoever you originally installed UT2k3 as, so you get the most recent patches for it. You have to run that as the same user because the original setup symlinks an XML file into the home directory of whoever runs the setup program, that describes what's installed.


All times are GMT -5. The time now is 01:28 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.