As the title states, when I upgraded to the new 296.10 drivers, the antialiasing in the game stopped working. I uninstalled the new driver and rolled back to my previous 275.33 driver. However, the antialiasing in the game is still broken.
Any idea on how to fix this? Mass Effect 3 is the only game that is exhibiting this problem.
Nvidia 296.10 Drivers broke anti-aliasing
Débuté par
TruSkill
, mars 15 2012 10:10
Retour en haut
#2
Posté 15 mars 2012 - 10:53
neilthecellist
-
- Members
- 450 messages
Same problem for me. ME3 runs on such an old build of Unreal Engine 3.... The latest build not only supports AA (true AA by the way) but also supports NVIDIA 3D Vision and DirectX 11... So tired of this BioWare crap...
#3
Posté 16 mars 2012 - 01:22
TruSkill
-
- Members
- 37 messages
neilthecellist wrote...
Same problem for me. ME3 runs on such an old build of Unreal Engine 3.... The latest build not only supports AA (true AA by the way) but also supports NVIDIA 3D Vision and DirectX 11... So tired of this BioWare crap...
Regardless of the lack of MS/SS AA, I just don't understand why the game isn't processing antialiasing anymore. I don't care if it's not as good as it could be, but right now multiplayer is putting significant eyestrain on me because of all the damn jaggies.
#4
Posté 16 mars 2012 - 01:35
Liam
-
- Members
- 41 messages
Did you check your NVIDIA console and see if your global or local preferences changed? They may have, especially if you chose a clean install, in which case you may have to set anti-aliasing parameters in the nvidia panel. Please check and let us know; for one, I'm loathe to install the new drivers if it kills AA. Thanks, and good luck!neilthecellist wrote...
Same problem for me. ME3 runs on such an old build of Unreal Engine 3.... The latest build not only supports AA (true AA by the way) but also supports NVIDIA 3D Vision and DirectX 11... So tired of this BioWare crap...
#5
Posté 16 mars 2012 - 02:45
TruSkill
-
- Members
- 37 messages
All of the ME3 application profile settings are exactly the same as they were before I tried upgrading to 296.10, so as far as I can tell, nothing changed there.
For the heck of it, I tried setting everything to application controlled, but there is still no change.
For the heck of it, I tried setting everything to application controlled, but there is still no change.
#6
Posté 17 mars 2012 - 04:40
neilthecellist
-
- Members
- 450 messages
Liam wrote...
Did you check your NVIDIA console and see if your global or local preferences changed? They may have, especially if you chose a clean install, in which case you may have to set anti-aliasing parameters in the nvidia panel. Please check and let us know; for one, I'm loathe to install the new drivers if it kills AA. Thanks, and good luck!neilthecellist wrote...
Same problem for me. ME3 runs on such an old build of Unreal Engine 3.... The latest build not only supports AA (true AA by the way) but also supports NVIDIA 3D Vision and DirectX 11... So tired of this BioWare crap...
Tried, no difference.
#7
Guest_magnetite_*
Posté 17 mars 2012 - 06:58
Guest_magnetite_*
Guest_magnetite_*
-
- Guests
Try reverting to an older driver and using Nvidia Inspector to force AA. Set it to override any application setting. Another thing that worked for me with ME2 & ME1 (which don't support AA natively) is rename the *.exe file to UT3.exe and use the renamed UT3.exe in the Mass Effect profile to force it. Seemed to work.
http://www.google.ca...aa &btnG=Search
It's the first link
http://www.google.ca...aa &btnG=Search
It's the first link
Modifié par magnetite, 17 mars 2012 - 07:02 .
#8
Posté 17 mars 2012 - 08:22
SubGumn
-
- Members
- 1 messages
If you use nVidia inspector, you can open up the ME3 profile and see the line for "Antialiasing - Behavior Flags" is set to "0x00000005 (Mass Effect III)" in 296.10 whereas it was set to "None" in previous versions of the driver.
Set it back to "None" and any hardware AA you override will work again.
Had to figure this out myself when I saw that AA wasn't working anymore in 296.10
Happy to say I'm back to playing with hardware AA in 296.10 now.
Set it back to "None" and any hardware AA you override will work again.
Had to figure this out myself when I saw that AA wasn't working anymore in 296.10
Happy to say I'm back to playing with hardware AA in 296.10 now.
