In game anti-aliasing?

[Smoth]

The game is gorgous but cout really use AA. Feels like the most glaring thing left out.

[Smoth]

I ended up getting it to work with r_multiSamples somehow but damn the fps tanked at 16. Anything lower was unnoticable.

I dunno, I gave up, best I can figure it is bethseda doing another cash out port. I'll probably finish the game off and reclaim my 50GB. Damn shame really.

[EternallyHers]

I don't know what other numbers you were using. But I would stick to 2,4 and 8 if you want to make sure it's working and not use 16. Most engines run fine with those and I'm not sure if numbers like 10 would work.

One other thing to help make your screen more clear you can take the grain affect away by entering these two. Make sure to do them in this order though. On the first one there is a space inbetween the e and _ at the end.
cvaradd r_postprocessdofmode _1
cvaradd r_skippostprocess 1

[Smoth]

I only used numbers that are 2n. You don't use stuff like 10, too many issues with that. I tried 2,4,8 they all seemed to have entirely unnoticable effect. Which was odd but I figured hey, there may be a reason the options are gone

I'll try the cvars though, thanks!

[Sc0mBuNNeRRR]

I had the same issue and ended up downsampling it from 1440p to 1080p, still some jaggyness but acceptable performance

[Jig McGalliger]

Originally posted by Smoth:

Still nothing.

You have to add the line to your config file AND enable it in the console. It will almost always give the production code line.

[rippleeffect]

It works via the console command, but it doesn't make that big of an appearance when you do it. You'll still see jaggies on trasparencies and might not think its actually applying it. It does clean up the jaggies on the gun and vehicles. You are able to force SS via the NCP and it does work there, but multisampling will not work through there.

In sort, MSAA via the game console, and SSAA via the control panel.... be prepared for some performance hit. especially vram usage.

I ran 4xMSAA and 2xSSAA on my GTX 680 4GB and was pushing +3.8gb vram usage most of the game with some moments where the game froze to swap out caches textures.

[coc0nut]

aha, i get it! you need to turn off write protection on the game folder on program files!

[Nalydyenlo]

Originally posted by UnHoly Xander:

Alternately you can simply open the wolfconfig file and do it permanelty that way. Or force it via Nvidia CP/Catalyst.

Editing wolfConfig.cfg didn't work for me nor did forcing it through GPU software. Only got it working via the in-game console, but I did notice that when you do this, it writes 'r_multisamples "n"' to the wolfConfig.cfg file for you anyway. Not much use though as it still doesn't get applied when game starts up, so I've got to open the console and do it manually every time. I set it to 8 and crawlies & jaggies are somewhat reduced without too much of a performance hit.

[Pero Pljuca]

Maybe make the .cfg read only