So i recently got a new monitor which runs fantastically @ 120hz with my other games. But when i play ME2 with 120hz activated via DVI-D cable, i get very noticeable microstutter. If i go into the nvidia control panel and set my refresh rate down to 60hz, the game runs fine again - no stuttering at all.
My Specs:
3x GTX 580 (3GB versions) in 3-way SLI
Intel Core i7 980X @ stock
24GB Corsair Vengeance DDR3 RAM @ 1866mhz
1200w Coolermaster Silent Pro Gold PSU
EVGA classified 4-Way SLI mobo
Acer HN274H monitor connected via DVI-D cable
Yes i can workaround the 120hz bug by setting my monitor to run at 60hz, but when all my other games play better using 120hz why would i want to constantly reset my refresh rate just to play one game (ME2)?
Is this an Nvidia driver bug? Or something which never got QA tested at Bioware? Surely Bioware would have tested this game on an old Samsung 2233RZ moinitor (one of the first 3D vision 120hz monitors out there - 2 years old).
Microstutter Bug with 120hz monitors
Débuté par
OperativeX
, juil. 19 2011 11:42
Retour en haut
#2
Posté 20 juillet 2011 - 05:01
Bogsnot1
-
- Members
- 7 997 messages
You havent given Windows version, GPU driver version, game version and patch level.
It could be something that slipped by their QA because they didnt have access to such equipment, or it could be an Nvidia driver issue, as Nvidia are reknowned for tweaking their newer drivers to compliment newer games, while said tweaks often cause problems with older games such as ME2.
You're assuming Bioware had access to every possible hardware configuration available and tested it out with such. They would have tested it out with common hardware, and 2 years ago, 120hz monitors werent exactly common, or cheap.Surely Bioware would have tested this game on an old Samsung 2233RZ moinitor (one of the first 3D vision 120hz monitors out there - 2 years old).
It could be something that slipped by their QA because they didnt have access to such equipment, or it could be an Nvidia driver issue, as Nvidia are reknowned for tweaking their newer drivers to compliment newer games, while said tweaks often cause problems with older games such as ME2.
#3
Posté 20 juillet 2011 - 11:37
OperativeX
-
- Members
- 202 messages
Gpu driver is 275.50 latest beta. Windows 7 version 64-bit sp1. Game patched to latest version - it's digital on Steam and I've bought and installed all dlc available apart from the genesis comic
#4
Posté 20 juillet 2011 - 11:54
Bogsnot1
-
- Members
- 7 997 messages
Nvidia's beta drivers have never been that good with ME2. I'd give it a try with the WHQL version and see how its goes.
Also, are you playing the game in a different resolution to your desktop display? If so, set your Windows desktop to that resolution, and make sure the monitor is set for 120hz as well. It could be Windows glitch thats causing the problem, and not ME2 or Nvidia.
Another thing to try is go into the Nvidia Control Panel, and set up a custom profile specifically for Masseffect2.exe, individually selecting all the options instead of having "use global setting" selected.
Also, are you playing the game in a different resolution to your desktop display? If so, set your Windows desktop to that resolution, and make sure the monitor is set for 120hz as well. It could be Windows glitch thats causing the problem, and not ME2 or Nvidia.
Another thing to try is go into the Nvidia Control Panel, and set up a custom profile specifically for Masseffect2.exe, individually selecting all the options instead of having "use global setting" selected.
#5
Posté 20 juillet 2011 - 06:30
OperativeX
-
- Members
- 202 messages
Yes the desktop res is 1920x1080 @ 120hz also. Tried older WHQL driver 275.33... damn still problem persists. I hope the new WHQL which is due out soon will solve the problem 
#6
Posté 20 juillet 2011 - 06:31
OperativeX
-
- Members
- 202 messages
:edit post:
Modifié par OperativeX, 20 juillet 2011 - 06:31 .
#7
Posté 20 juillet 2011 - 08:11
Baramon
-
- Members
- 375 messages
Here's a helpful thread about tweaking ME2 (here: social.bioware.com/forum/1/topic/106/index/2060374 ). It said you had to use some 10.1 hotfix driver to do some tweaking.
I'm going to try fiddling around with the AA like it suggests. I thought it was just me, but I noticed it right off that the game didn't seem to have anti-aliasing in it. Now I know.
{EDIT: Fiddling caused too many additional problems, and most of the time the game wouldn't even load at all; so I gave that up.}
{Double-EDIT: Took out the suggestion about the hotfix; misread the instructions. Sorry.}
I'm going to try fiddling around with the AA like it suggests. I thought it was just me, but I noticed it right off that the game didn't seem to have anti-aliasing in it. Now I know.
{EDIT: Fiddling caused too many additional problems, and most of the time the game wouldn't even load at all; so I gave that up.}
{Double-EDIT: Took out the suggestion about the hotfix; misread the instructions. Sorry.}
Modifié par Baramon, 21 juillet 2011 - 11:36 .
#8
Posté 21 juillet 2011 - 08:21
Bogsnot1
-
- Members
- 7 997 messages
The thread that Baramon linked was going to be my next suggestion. THe 10.1 hotfix he mentioned aplpies to ATI cards, so that rules you out.
One thing that is mentioned in the thread is to try renaming the masseffect2.exe to UT3.exe for greater support via the Nvidia control panel. This will only work with the retail version though, so not sure how it will go with Steam version if you have that. If you do rename it, you will have to make sure to launch the game directly from the executable, rather than via the launch menu.
One thing that is mentioned in the thread is to try renaming the masseffect2.exe to UT3.exe for greater support via the Nvidia control panel. This will only work with the retail version though, so not sure how it will go with Steam version if you have that. If you do rename it, you will have to make sure to launch the game directly from the executable, rather than via the launch menu.
