Screen Tearing - in 3D Vision! Looks like smearing, smudging
I've noticed this has become more of an issue, I believe around the introduction of the 257 or 258 drivers, but the problem is there seems to be a frame rate synchronization problem where displayed frames are getting partial frames. This should not be happening with the 60 FPS cap while running in Stereo 3D. What the end result looks like is a "smearing" or "smudging" effect that makes parts of the screen blurry/muddy. But this is just traditional screen tearing, like what you would see with Vsync off and partial frames on a 60Hz monitor, but in Stereo 3D! :(
I know I'm not the only one who has commented on this and I did not have it for the longest time because I was using the R197 drivers. I have noticed it has improved somewhat with the R258.96 drivers but I can still reproduce the problem pretty easily in quite a few games and it also seems more noticeable when FPS drops below 60 per eye. I've also noticed it is typically worst below 60FPS per eye, and since I'm usually over that, I guess I haven't seen it as much. Here's some examples:
[list]
[*]1) Fallout 3 - smearing line near the bottom of the screen even at capped 60FPS. Can be mitigated by forcing Vsync on in the NVCP for Fallout3.exe and also setting iFPSclamp to 60 in the fallout3.ini.
[*]2) Transformers War For Cybertron - smearing line near the bottom of the screen even at capped 60FPS. Only occurs with the 60FPS unlocker, again, force Vsync on in the NVCP can help.
[*]3) Borderlands - smearing varies, only below 60FPS. Setting bframeratesmoothing to 60 can help, Vsync in NVCP also, but there's almost always some smearing below 60FPS (especially around T-Bone Junction roads).
[*]4) StarCraft 2 - Smearing/Warping all over the place, it is unplayable at default settings like this. In-game Vsync or NVCP Vsync don't really help, however, setting the mouse smoothing option does as it does whatever frame synching is required to remove the screen tearing.
[/list]
Just wanted to see if Nvidia is aware of this and if others are seeing this also. I've found workarounds for most of the games I've seen it in so maybe that can help some of you out also, but for me the best possible solution has been to keep 60FPS capped.
I've noticed this has become more of an issue, I believe around the introduction of the 257 or 258 drivers, but the problem is there seems to be a frame rate synchronization problem where displayed frames are getting partial frames. This should not be happening with the 60 FPS cap while running in Stereo 3D. What the end result looks like is a "smearing" or "smudging" effect that makes parts of the screen blurry/muddy. But this is just traditional screen tearing, like what you would see with Vsync off and partial frames on a 60Hz monitor, but in Stereo 3D! :(
I know I'm not the only one who has commented on this and I did not have it for the longest time because I was using the R197 drivers. I have noticed it has improved somewhat with the R258.96 drivers but I can still reproduce the problem pretty easily in quite a few games and it also seems more noticeable when FPS drops below 60 per eye. I've also noticed it is typically worst below 60FPS per eye, and since I'm usually over that, I guess I haven't seen it as much. Here's some examples:
1) Fallout 3 - smearing line near the bottom of the screen even at capped 60FPS. Can be mitigated by forcing Vsync on in the NVCP for Fallout3.exe and also setting iFPSclamp to 60 in the fallout3.ini.
2) Transformers War For Cybertron - smearing line near the bottom of the screen even at capped 60FPS. Only occurs with the 60FPS unlocker, again, force Vsync on in the NVCP can help.
3) Borderlands - smearing varies, only below 60FPS. Setting bframeratesmoothing to 60 can help, Vsync in NVCP also, but there's almost always some smearing below 60FPS (especially around T-Bone Junction roads).
4) StarCraft 2 - Smearing/Warping all over the place, it is unplayable at default settings like this. In-game Vsync or NVCP Vsync don't really help, however, setting the mouse smoothing option does as it does whatever frame synching is required to remove the screen tearing.
Just wanted to see if Nvidia is aware of this and if others are seeing this also. I've found workarounds for most of the games I've seen it in so maybe that can help some of you out also, but for me the best possible solution has been to keep 60FPS capped.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
I know I'm not the only one who has commented on this and I did not have it for the longest time because I was using the R197 drivers. I have noticed it has improved somewhat with the R258.96 drivers but I can still reproduce the problem pretty easily in quite a few games and it also seems more noticeable when FPS drops below 60 per eye. I've also noticed it is typically worst below 60FPS per eye, and since I'm usually over that, I guess I haven't seen it as much. Here's some examples:
[list]
[*]1) Fallout 3 - smearing line near the bottom of the screen even at capped 60FPS. Can be mitigated by forcing Vsync on in the NVCP for Fallout3.exe and also setting iFPSclamp to 60 in the fallout3.ini.
[*]2) Transformers War For Cybertron - smearing line near the bottom of the screen even at capped 60FPS. Only occurs with the 60FPS unlocker, again, force Vsync on in the NVCP can help.
[*]3) Borderlands - smearing varies, only below 60FPS. Setting bframeratesmoothing to 60 can help, Vsync in NVCP also, but there's almost always some smearing below 60FPS (especially around T-Bone Junction roads).
[*]4) StarCraft 2 - Smearing/Warping all over the place, it is unplayable at default settings like this. In-game Vsync or NVCP Vsync don't really help, however, setting the mouse smoothing option does as it does whatever frame synching is required to remove the screen tearing.
[/list]
Just wanted to see if Nvidia is aware of this and if others are seeing this also. I've found workarounds for most of the games I've seen it in so maybe that can help some of you out also, but for me the best possible solution has been to keep 60FPS capped.
I know I'm not the only one who has commented on this and I did not have it for the longest time because I was using the R197 drivers. I have noticed it has improved somewhat with the R258.96 drivers but I can still reproduce the problem pretty easily in quite a few games and it also seems more noticeable when FPS drops below 60 per eye. I've also noticed it is typically worst below 60FPS per eye, and since I'm usually over that, I guess I haven't seen it as much. Here's some examples:
Just wanted to see if Nvidia is aware of this and if others are seeing this also. I've found workarounds for most of the games I've seen it in so maybe that can help some of you out also, but for me the best possible solution has been to keep 60FPS capped.
-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings
Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST