You're taking this the wrong way. This is just so people who don't know what they're doing and want their graphics to work, having followed umpteen internet tutorials and installed both drivers, get the better working ones of the bunch instead of having nouveau interfere. It's also an option that's not on by default, so something suggests to me that someone else will be turning it on.
oh come on, it's common knowlege why the drivers need that, stop trolling for the wrong reasons
Oh, geez, you missunderstood me, I know all about FXAA/SRAA/MLAA/TXAA/*AA, as a user, I ONLY said that it's not needed to APPLY FXAA OVER MSAA, use MSAA or FXAA, but not both... that's all :P
BTW, in my test, Unigine Heaven 3.1, 1920x1080/16x AF, all HIGH, Tess Extreme, with in-engine 4xAA is (surprise) faster than with driver applied FXAA, I'll post the numbers once I get home later.
Last edited by Licaon; 08-14-2012 at 05:21 AM.
but thats my point... I went into nv-settings and it has an option "override application" but it turned out it didn't actually override the application.
ingame I had AA at x8
in the nv control panel I can "force application" to x4 but it doesn't actually override it just adds aa, so app does x8 then nv does x4.
So when I did FXAA it didn't override the program doing AA (as the nvidia-settings is implying) it does it on top of what the application is doing HENCE the x8 MSAA and then FXAA being applied by nv thus resulting in the fps drop.
once ingame was disable reasonable fps was recieved (lower than MSAA to be fair but I am playing)
you seem to be misunderstanding me, the issue here is with nvidia-settings not actually doing what it say. in windows force override does exactly that, in linux is does it in addition to
I did understand, I repeat, given the nature of the FXAA (and of the other shader based AA things) I found it rather ugly when combined (blurred text and al).
Also, since this sounds like a bug somehow, do report it too via http://nvidia.custhelp.com/app/utils...m/redirect/ask (not via nvnews since no nVidia dev posted there afaik since the June/July incidents)
I just removed mplayer2 and libav and replaced them with mplayer and ffpeg.
The slowdown isn't there. But it's just as useless, because when I minimize the video or make it fullscreen, the whole desktop freezes and mplayer crashes after 6 seconds or so (at which point the desktop becomes responsive again.)
Interesting to see the improved EDID support. Had to export the EDID.bin and fix it with some script on my monitor because otherwise the
screen would be cropped. Maybe I can remove my Option "CustomEDID" from xorg.conf now.
This is mplayer (not mplayer2) http://youtu.be/7VtHz4RNfac
It's not "5 fps cursor" but video shuttering is unacceptable, same as desktop experience at framerate < ~60 FPS
This is wonderful news!- A --disable-nouveau switch for the NVIDIA binary blob installer that will attempt to automatically kill the open-source Nouveau DRM driver to prevent it from being loaded and conflicting with NVIDIA's official driver.
Now I'm hoping for a "--delete-Mesa" switch, followed by "--kill-GCC", and finally "--replace-everything-with-Win8", so people have no problems anymore and nothing conflicts with the official driver.
That's exactly what we want a hardware vendor to do -- not opening specification so we can use their shit, but deleting open source software from your computer if it doesn't fit in with their secretive master plan.
Kudos!