Well, darn. Should click "preview" next time. Properly-formatted reply follows.
I installed the Loki version of Quake 3, which upon running froze up while it was initializing sound.
Were you running KDE or GNOME, or ? If you're running KDE, the aRts sound server should be disabled in the Control Center, as it grabs the DSP and doesn't let go.
Even though I did this, the sound STILL lags behind the action of the game unless I set the buffer to be shorter, which wastes my time because I had to restart the sound server to do it.
(replace "esound" with arts/yiff/whatever.)
"esound is junk. The only thing esd has is a good client API for going boing at approximately the right time. Anything else is beyond it." -- Alan Cox
Did I mention that I also had to use unofficial precompiled RPMs to install the nVidia drivers with ANY kind of convienience?
The unofficial ones that are on the driver section of nVidia's Web site?
Also, I had to mess around with an XFree86 configuration file.
The README should've spelled out the install process clearly enough.
Finally, when I was playing Quake, the same settings as before yielded a steady 80 fps. Whee.
This is a sign that either:
a) you're not using the same settings as before. or b) something's hogging CPU (probably aRts.)
Switch to a console (Alt+Ctrl+F2) and run ps auwx. Check to see if anything besides quake3 (or perhaps "quake3.x86") is taking a noticeable amount of CPU time.
I installed the Loki version of Quake 3, which upon running froze up while it was initializing sound.
Were you running KDE or GNOME, or ? If you're running KDE, the aRts sound server should be disabled in the Control Center, as it grabs the DSP and doesn't let go.
Even though I did this, the sound STILL lags behind the action of the game unless I set the buffer to be shorter, which wastes my time because I had to restart the sound server to do it.
"esound [replace with arts/yiff/what have you] is junk. The only thing esd has is a good client API for going boing at approximately the right time. Anything else is beyond it." -- Alan Cox
Did I mention that I also had to use unofficial precompiled RPMs to install the nVidia drivers with ANY kind of convienience?
The unofficial ones that are on the driver section of nVidia's Web site?
Also, I had to mess around with an XFree86 configuration file.
The README should've spelled out the install process clearly enough.
Finally, when I was playing Quake, the same settings as before yielded a steady 80 fps. Whee.
This is a sign that either:
a) you're not using the same settings as before.
or b) something's hogging CPU (probably aRts.)
Switch to a console (Alt+Ctrl+F2) and run ps auwx. Check to see if anything besides quake3 (or perhaps "quake3.x86") is taking a noticeable amount of CPU time.
Actually, LGP is an SDL house. So if you're using a windowing system that has both an SDL backend and a decent OpenGL implementation, you should be fine.
Slashdot Mirror
Well, darn. Should click "preview" next time. Properly-formatted reply follows.
I installed the Loki version of Quake 3, which upon running froze up while it was initializing sound.
Were you running KDE or GNOME, or ? If you're running KDE, the aRts sound server should be disabled in the Control Center, as it grabs the DSP and doesn't let go.
Even though I did this, the sound STILL lags behind the action of the game unless I set the buffer to be shorter, which wastes my time because I had to restart the sound server to do it.
(replace "esound" with arts/yiff/whatever.)
"esound is junk. The only thing esd has is a good client API for going boing at approximately the right time. Anything else is beyond it." -- Alan Cox
Did I mention that I also had to use unofficial precompiled RPMs to install the nVidia drivers with ANY kind of convienience?
The unofficial ones that are on the driver section of nVidia's Web site?
Also, I had to mess around with an XFree86 configuration file.
The README should've spelled out the install process clearly enough.
Finally, when I was playing Quake, the same settings as before yielded a steady 80 fps. Whee.
This is a sign that either:
a) you're not using the same settings as before.
or b) something's hogging CPU (probably aRts.)
Switch to a console (Alt+Ctrl+F2) and run ps auwx. Check to see if anything besides quake3 (or perhaps "quake3.x86") is taking a noticeable amount of CPU time.
(Sorry if I come off as condescending.)
I installed the Loki version of Quake 3, which upon running froze up while it was initializing sound. Were you running KDE or GNOME, or ? If you're running KDE, the aRts sound server should be disabled in the Control Center, as it grabs the DSP and doesn't let go. Even though I did this, the sound STILL lags behind the action of the game unless I set the buffer to be shorter, which wastes my time because I had to restart the sound server to do it. "esound [replace with arts/yiff/what have you] is junk. The only thing esd has is a good client API for going boing at approximately the right time. Anything else is beyond it." -- Alan Cox Did I mention that I also had to use unofficial precompiled RPMs to install the nVidia drivers with ANY kind of convienience? The unofficial ones that are on the driver section of nVidia's Web site? Also, I had to mess around with an XFree86 configuration file. The README should've spelled out the install process clearly enough. Finally, when I was playing Quake, the same settings as before yielded a steady 80 fps. Whee. This is a sign that either: a) you're not using the same settings as before. or b) something's hogging CPU (probably aRts.) Switch to a console (Alt+Ctrl+F2) and run ps auwx. Check to see if anything besides quake3 (or perhaps "quake3.x86") is taking a noticeable amount of CPU time.
Try Tux Games. They ship to the US, too.
Actually, LGP is an SDL house. So if you're using a windowing system that has both an SDL backend and a decent OpenGL implementation, you should be fine.
Wow. That's one hell of a trick, seeing as how the developers don't even have the code yet.