nV News Forums


nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Can't get FSAA to work (http://www.nvnews.net/vbulletin/showthread.php?t=1358)

krow 08-31-02 07:14 AM

Can't get FSAA to work
I've got the NVidia driver working, but FSAA won't work. I set the environment variable with "export __GL_FSAA_MODE=4", and check it by typing "env", but when I run a game there's no antialiasing.

Hardware: GeForce4 Ti4400
Software: Debian Woody
Linux 2.4.19
NVidia driver 1.0-2960
Tux Racer 0.61-6
Unreal Tournament 436
(no more 3D games in Linux yet)

Both the games work nicely with hardware acceleration, but they don't antialias.
Can anyone help? Thanks in advance.

Thunderbird 08-31-02 02:54 PM

I hope you understand how environment variables work. When you change an environment variable on linux the changed variable is only valid for the current shell you are using and all its clients.

So for example you set an environment variable in a gnome terminal. Then you launch an app from a different terminal or using a shortcut. In these two cases both apps don't know about those variables.

When you would start an app in the same terminal in which you set the variable it would work fine.

There are two good places to put nvidia environment variables like __GL_FSAA_MODE in. You can put it in your .bashrc. Then those variables will be set for each bash shell you launch.

Or another option would be to use a startup script to start a game. Then you can add those environment variables to the startup script. After you quit the app the variable is unset. Using this you can use different settings for different games.

krow 09-01-02 06:44 AM

I've already tried setting the environment variable in /etc/profile, and in a shell script which I use to launch the game:

export __GL_FSAA_MODE=4

Is there anything else that I might be doing wrong?

Thunderbird 09-01-02 08:25 AM

I would set the game at 640x480 and then compare with and without. At this resolution you should see the difference.

krow 09-01-02 02:53 PM

1 Attachment(s)
Here are cropped screenshots of Unreal Tournament to demonstrate the problem.
Top: Linux, setting 4x antialiasing with the environment variable (software described in my first post)
Bottom: Windows, setting 4x antialiasing with the NVidia system tray applet (WinME, NVidia driver 30.82, UT 436, OpenGL)

I'm probably just making some stupid mistake... I'm sure I'm setting the environment variable properly though.

Oh, btw, both those shots are from the same computer.


krow 09-15-02 02:31 PM

It works
1 Attachment(s)
I just recompiled the kernel to add some unrelated drivers. After recompliling the kernel I needed to reinstall the NVidia kernel driver. I had already tried reinstalling the kernel driver, but that didn't help.

Today I accidentally reinstalled the NVidia GLX kernel as well as the kernel driver, and now FSAA has started working!

Unfortunately I have no idea how to recreate the problem :-/

anyway, here's a screenshot of 4x antialiased tux racer to celebrate :D


krow 09-17-02 08:03 AM

Sorry about all this spam, but today I upgraded my xlibmesa3 package, and fsaa stopped again. Reinstalling the NVidia GLX driver fixed it. So, I must have broken the GLX driver by installing new distribution packages and failing to reinstall the NVidia driver.

All times are GMT -5. The time now is 11:28 PM.

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