I’ve tried pretty much everything now; ingame, nVidia control panel, injected FXAA… My screenshots still look like jaggy crap. And while that can be fine when you crop+resize it, full-size it looks horrible. An unedited screen of Resistance spawn on Labs: http://img19.imageshack.us/img19/3466/shot01666.png
Drivers are the most recent, clean install and all. Game cache is verified.
do you have AA disabled in nvidia cpanel? do you use brinkit or brink configurator? do you use an autoexec.cfg file?
in nvidia cpanel make sure you dont override application
[QUOTE=Verticae;368038]See OP.
That’s all the same thing actually.[/QUOTE]
i know, but it might have gotten screwed in there. without an autoexec do you get the issues?
Without an autoexec I get the exact same settings. You do know how it works, don’t you? 
Try resetting all cvar settings. Run the game, open the console and run the command cvar_restart. Quit and restart the game. This should rule out any bad settings that may be set in your profile or elsewhere. I’d remove or rename your autoexec.cfg beforehand too, just to make sure it’s not something in there.
Could it be a conflict between graphic card forced settings, and game/steam settings ?
[QUOTE=Stormchild;368953]Could it be a conflict between graphic card forced settings, and game/steam settings ?[/QUOTE]It would be worth knowing how you are taking the screenshots (via Brink, via Steam or via some other method).
What is the AA level set by Brink? I can’t find that anywhere and it doesn’t seem sufficient.
/screenshot.
I tried cvar_restart, it didn’t do anything. So I went with a re-installation, and that seems to have fixed it. However, the anti-aliasing is still severely lacking. It seems that the Nvidia cPanel options don’t work with Brink in any way; is there any other way to bump up the anti-aliasing?
seta r_useAntiAliasing “1”
seta r_multiSamples 16
seta r_useAntiAliasing 16
Give those a try. I have mine set to 16x using a Brink config tool and it looks great.
No you don’t. r_multiSamples has been read-only for a while now, and changing it before didn’t do anything anyway. r_useAntiAliasing is a boolean (0 or 1 only), and that’s what toggling anti-aliasing in the in-game menu does. (http://www.splashdamage.com/forums/showthread.php?p=346697#post346697)
I don’t recommend either of the Brink config tools to anyone.
[QUOTE=HugePinball;369416]No you don’t. r_multiSamples has been read-only for a while now, and changing it before didn’t do anything anyway. r_useAntiAliasing is a boolean (0 or 1 only), and that’s what toggling anti-aliasing in the in-game menu does. (http://www.splashdamage.com/forums/showthread.php?p=346697#post346697)
I don’t recommend either of the Brink config tools to anyone.[/QUOTE]
After some testing, you’re absolutely right. They shouldn’t have this info in a sticky in the main forum in this case.
Brink uses FXAA, which is a post-process aa-effect. The settings in the driver does not affect this at all. This is not a problem we’ve seen anywhere else, so I suspect your CVARs are messed up. Toggling anti-aliasing in the display-menu should make a difference either way. What you are seeing in your screenshot is not the intended look.
“injected fxaa”… creative 
[QUOTE=sdGjoel;370425]Brink uses FXAA, which is a post-process aa-effect. The settings in the driver does not affect this at all. This is not a problem we’ve seen anywhere else, so I suspect your CVARs are messed up. Toggling anti-aliasing in the display-menu should make a difference either way. What you are seeing in your screenshot is not the intended look.
“injected fxaa”… creative ;)[/QUOTE]
As mentioned; the issue was finally resolved through a reinstall. I’d still like to find a way to up the amount of anti-aliasing passes, though.
