World of Warcraft used to work flawlessly, now unplayable in 3D
8 / 26
What I don't understand, from my possibly naive standpoint is this:
[b][u]How can nVidia need to ask us that question?[/u][/b]
If this problem was unknown and obscure, that would make some sense. But this issue has:
a.) been known for months
b.) been acknowledge by nVidia
c). indicated, by an nVidia rep, as a top priority fix in this very thread almost two months ago now
d). affected a ridiculously popular product that they intend to use to show of their new hardware fairly soon
Doesn't nVidia have... you know... test machines to test things on? At the very least, all drivers subsequent to October 2009's 191.07 / CD 1.13 need to have their profile for WoW show a "poor" or "not recommended" rating, lest anyone give it a shot and think it's nVidia's concept of "excellent" 3D support.
I'm sorry for the tone of this post, I've never whined on a forum before and only registered here to bump this ancient thread in the hopes that it will actually get some attention. If I'm way out in left field here, someone please talk some sense into but this whole situation seems pretty sad.
What I don't understand, from my possibly naive standpoint is this:
How can nVidia need to ask us that question?
If this problem was unknown and obscure, that would make some sense. But this issue has:
a.) been known for months
b.) been acknowledge by nVidia
c). indicated, by an nVidia rep, as a top priority fix in this very thread almost two months ago now
d). affected a ridiculously popular product that they intend to use to show of their new hardware fairly soon
Doesn't nVidia have... you know... test machines to test things on? At the very least, all drivers subsequent to October 2009's 191.07 / CD 1.13 need to have their profile for WoW show a "poor" or "not recommended" rating, lest anyone give it a shot and think it's nVidia's concept of "excellent" 3D support.
I'm sorry for the tone of this post, I've never whined on a forum before and only registered here to bump this ancient thread in the hopes that it will actually get some attention. If I'm way out in left field here, someone please talk some sense into but this whole situation seems pretty sad.
For those experiencing this problem, can you please post your system specifications?
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below: GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
[quote name='ManuelG' post='1031543' date='Mar 31 2010, 10:59 PM']For those experiencing this problem, can you please post your system specifications?
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
I have this problem for the following configurations for all the latest driver releases (the initial CD release that came with the glasses works great, but crashes in Windows 7 often).
[quote name='ManuelG' post='1031543' date='Mar 31 2010, 10:59 PM']For those experiencing this problem, can you please post your system specifications?
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
I have this problem for the following configurations for all the latest driver releases (the initial CD release that came with the glasses works great, but crashes in Windows 7 often).
Just got done playing WOW tonight and all I can tell you after tweaking forever is.
1) CTRL-t to look at the map (use a macro ex. ctrl-t pause m)
2) if something is out of depth get to the WOW menu and adjust the top 3D setting bar by just moving it a verrry little left or right. If I do this multiple times, it seems to fix things (still sucks cause of how many times I have to do it.). It helps.
This is the last prob i have with 3D vision. Thanks again for finally fixing the Samsung detection issue.
Just got done playing WOW tonight and all I can tell you after tweaking forever is.
1) CTRL-t to look at the map (use a macro ex. ctrl-t pause m)
2) if something is out of depth get to the WOW menu and adjust the top 3D setting bar by just moving it a verrry little left or right. If I do this multiple times, it seems to fix things (still sucks cause of how many times I have to do it.). It helps.
This is the last prob i have with 3D vision. Thanks again for finally fixing the Samsung detection issue.
Just to reiterate ... this is 100% to do with the convergence setting in WoW in relation to the 3D Stereo Driver. It's like there is an incongruity between the two.
I tried tonight to run at zero "screen depth" setting in WoW (zero convergence adjustment I think) and it was almost tolerable. All the usual things were way off, but not by as much. I used to run with that setting at about 20% or so and had great success in 1.13 (191.07), but if I try that with any later drivers, 80% of the UI diverges to the point that it's incomprehensible. I did notice that with the screen depth slider at zero, I could see the map screen but it appeared about 1" behind my physical screen at that point... Also, context frames (mousing over a player's name and right clicking for example) would appear 1" OUT of the screen... so it seems that different parts of the UI are being perceived by the 3D vision driver as at TOTALLY different depths, when the UI should ALL be a zero depth period. Even at a zero setting, the chat text redraws were still almost impossible to read because my eyes just wouldn't pop them out. It should be rendered flat anyway.
Pissing around with the convergence (CTRL F5 and F6) is retarded because it simply moves EVERYTHING, including the action bars and map and whatnot either into or out of the screen which really messes with your brain... so any solution involving that crap is off the table - the UI NEEDS to be at screen depth, period. The rest of the world can revolve around it just fine, as in older drivers - again - 1.13 or earlier for WoW.
Not rocket science - you have working drivers, and failing ones... shouldn't be a 6 month fix to make it the way it USED to be.
Just to reiterate ... this is 100% to do with the convergence setting in WoW in relation to the 3D Stereo Driver. It's like there is an incongruity between the two.
I tried tonight to run at zero "screen depth" setting in WoW (zero convergence adjustment I think) and it was almost tolerable. All the usual things were way off, but not by as much. I used to run with that setting at about 20% or so and had great success in 1.13 (191.07), but if I try that with any later drivers, 80% of the UI diverges to the point that it's incomprehensible. I did notice that with the screen depth slider at zero, I could see the map screen but it appeared about 1" behind my physical screen at that point... Also, context frames (mousing over a player's name and right clicking for example) would appear 1" OUT of the screen... so it seems that different parts of the UI are being perceived by the 3D vision driver as at TOTALLY different depths, when the UI should ALL be a zero depth period. Even at a zero setting, the chat text redraws were still almost impossible to read because my eyes just wouldn't pop them out. It should be rendered flat anyway.
Pissing around with the convergence (CTRL F5 and F6) is retarded because it simply moves EVERYTHING, including the action bars and map and whatnot either into or out of the screen which really messes with your brain... so any solution involving that crap is off the table - the UI NEEDS to be at screen depth, period. The rest of the world can revolve around it just fine, as in older drivers - again - 1.13 or earlier for WoW.
Not rocket science - you have working drivers, and failing ones... shouldn't be a 6 month fix to make it the way it USED to be.
I can apply the work around similar to whodamanxbox to get all the overlays aligned but with just one tap of CTRL F6 - its unplayable...
edit - whoops 260 not[i][/i] 240
Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.
-------------------
Vitals: Windows 7 64bit, i5 2500 @ 4.4ghz, SLI GTX670, 8GB, Viewsonic VX2268WM
1) Acer GD235HZ
2) GTX 285
3) Vista Ultimate 32-bit
Overlays, maps, minimaps, buffs, debuffs, character preview, login screens, and exp all show up bugged/double/blurry/seperated using almost all convergence settings (unusable).
While your at it, the mouse on the loading screen also doubles (with both hardware and software mouse).
Also, since it seems like no one at NVIDIA has lifted a finger to actually test this out (as it would be grossly apparent what is wrong with any new driver) convergence settings are in wow listed under stereo options as : "screen depth"
You really don't need to be gathering that much data, as all setups have an issue with this game, and it is very clear what the problem is. If you want to recreate it, load up a machine with any monitor, install wow, install latest 3d driver (or any driver released by you guys in since 2009) and just look at the screen through your 3d glasses.
This is not a small issue affecting a small percentage of players, it affects all players using 3d in WoW, and all hardware setups. The only people that can actually get it to work use an ancient driver from when WoW actually worked in 3d.
Overlays, maps, minimaps, buffs, debuffs, character preview, login screens, and exp all show up bugged/double/blurry/seperated using almost all convergence settings (unusable).
While your at it, the mouse on the loading screen also doubles (with both hardware and software mouse).
Also, since it seems like no one at NVIDIA has lifted a finger to actually test this out (as it would be grossly apparent what is wrong with any new driver) convergence settings are in wow listed under stereo options as : "screen depth"
You really don't need to be gathering that much data, as all setups have an issue with this game, and it is very clear what the problem is. If you want to recreate it, load up a machine with any monitor, install wow, install latest 3d driver (or any driver released by you guys in since 2009) and just look at the screen through your 3d glasses.
This is not a small issue affecting a small percentage of players, it affects all players using 3d in WoW, and all hardware setups. The only people that can actually get it to work use an ancient driver from when WoW actually worked in 3d.
1) Samsung 2233RZ
2) EVGA GTS250 SLI
3) Windows 7 x64 Professional
Works with 191.07 drivers. UI is totally bugged out with newer drivers. You can fix the text and maps by moving the depth slider, but as soon as anything changes on the UI the new item will screw up and you have touch/move the slider again. The cool down boxes are never correct no matter what I have done. pwnshoppe's post above hit the nail on the head. This is a problem with everyone, no system specs are really needed.
Works with 191.07 drivers. UI is totally bugged out with newer drivers. You can fix the text and maps by moving the depth slider, but as soon as anything changes on the UI the new item will screw up and you have touch/move the slider again. The cool down boxes are never correct no matter what I have done. pwnshoppe's post above hit the nail on the head. This is a problem with everyone, no system specs are really needed.
Thanks all. I have passed this information to our QA team to investigate.
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below: GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
[b][u]How can nVidia need to ask us that question?[/u][/b]
If this problem was unknown and obscure, that would make some sense. But this issue has:
a.) been known for months
b.) been acknowledge by nVidia
c). indicated, by an nVidia rep, as a top priority fix in this very thread almost two months ago now
d). affected a ridiculously popular product that they intend to use to show of their new hardware fairly soon
Doesn't nVidia have... you know... test machines to test things on? At the very least, all drivers subsequent to October 2009's 191.07 / CD 1.13 need to have their profile for WoW show a "poor" or "not recommended" rating, lest anyone give it a shot and think it's nVidia's concept of "excellent" 3D support.
I'm sorry for the tone of this post, I've never whined on a forum before and only registered here to bump this ancient thread in the hopes that it will actually get some attention. If I'm way out in left field here, someone please talk some sense into but this whole situation seems pretty sad.
How can nVidia need to ask us that question?
If this problem was unknown and obscure, that would make some sense. But this issue has:
a.) been known for months
b.) been acknowledge by nVidia
c). indicated, by an nVidia rep, as a top priority fix in this very thread almost two months ago now
d). affected a ridiculously popular product that they intend to use to show of their new hardware fairly soon
Doesn't nVidia have... you know... test machines to test things on? At the very least, all drivers subsequent to October 2009's 191.07 / CD 1.13 need to have their profile for WoW show a "poor" or "not recommended" rating, lest anyone give it a shot and think it's nVidia's concept of "excellent" 3D support.
I'm sorry for the tone of this post, I've never whined on a forum before and only registered here to bump this ancient thread in the hopes that it will actually get some attention. If I'm way out in left field here, someone please talk some sense into but this whole situation seems pretty sad.
Core i7 920 @ 3.6Ghz, 6GB 3 Channel, SLi GTX670 2GB, SSD
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below:
GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
I am also available on Twitter:
www.twitter.com/manuelguzman
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
1) Samsung 2233RZ
2) Zotac GTX260 (216 core)
3) Windows 7 x64 Professional
Seems like this problem isn't dependant on either of the things you are asking for though :(
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
1) Samsung 2233RZ
2) Zotac GTX260 (216 core)
3) Windows 7 x64 Professional
Seems like this problem isn't dependant on either of the things you are asking for though :(
2) eVGA GTX260 (core 216)
3) Windows 7 x64 Home Premium.
2) eVGA GTX260 (core 216)
3) Windows 7 x64 Home Premium.
Core i7 920 @ 3.6Ghz, 6GB 3 Channel, SLi GTX670 2GB, SSD
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
1) Samsung 2233rz
2) EVGA 9800GTX+
3) Windows 7 Enterprise x64
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
1) Samsung 2233rz
2) EVGA 9800GTX+
3) Windows 7 Enterprise x64
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
I have this problem for the following configurations for all the latest driver releases (the initial CD release that came with the glasses works great, but crashes in Windows 7 often).
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) NVIDIA GeForce GTX 275
3) Windows 7
AND
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) GeForce GTS 250
3) Windows Vista
AND
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) GeForce 8800 GTX
3) Windows Vista
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
I have this problem for the following configurations for all the latest driver releases (the initial CD release that came with the glasses works great, but crashes in Windows 7 often).
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) NVIDIA GeForce GTX 275
3) Windows 7
AND
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) GeForce GTS 250
3) Windows Vista
AND
1) Samsung® SyncMaster 2233RZ 120 Hz LCD display
2) GeForce 8800 GTX
3) Windows Vista
1) CTRL-t to look at the map (use a macro ex. ctrl-t pause m)
2) if something is out of depth get to the WOW menu and adjust the top 3D setting bar by just moving it a verrry little left or right. If I do this multiple times, it seems to fix things (still sucks cause of how many times I have to do it.). It helps.
This is the last prob i have with 3D vision. Thanks again for finally fixing the Samsung detection issue.
1) CTRL-t to look at the map (use a macro ex. ctrl-t pause m)
2) if something is out of depth get to the WOW menu and adjust the top 3D setting bar by just moving it a verrry little left or right. If I do this multiple times, it seems to fix things (still sucks cause of how many times I have to do it.). It helps.
This is the last prob i have with 3D vision. Thanks again for finally fixing the Samsung detection issue.
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
1. Alienware AW2310 and/or Samsung 223RZ
2. GTX 295
3. Windows 7 32bit.
and
1. Asus G51J3D Latop w/120hz screen
2. GTX 260M
3. Windows 7 64bit.
Like everyone says it's bugged on every driver version after cd 1.13.
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
1. Alienware AW2310 and/or Samsung 223RZ
2. GTX 295
3. Windows 7 32bit.
and
1. Asus G51J3D Latop w/120hz screen
2. GTX 260M
3. Windows 7 64bit.
Like everyone says it's bugged on every driver version after cd 1.13.
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?[/quote]
1. Acer GD245HQ
2. GTX 285
3. Windows 7 64 Ultimate
I registered just to post this. WoW is the game i play every day and the bug is very annoying.
@whodamanxbox: this is not a fix, if you want to play with high convergence settings the ui is definitely bugged and not fixable with settings.
1) Which monitor/HDTV used?
2) Graphics card?
3) Windows version?
1. Acer GD245HQ
2. GTX 285
3. Windows 7 64 Ultimate
I registered just to post this. WoW is the game i play every day and the bug is very annoying.
@whodamanxbox: this is not a fix, if you want to play with high convergence settings the ui is definitely bugged and not fixable with settings.
I tried tonight to run at zero "screen depth" setting in WoW (zero convergence adjustment I think) and it was almost tolerable. All the usual things were way off, but not by as much. I used to run with that setting at about 20% or so and had great success in 1.13 (191.07), but if I try that with any later drivers, 80% of the UI diverges to the point that it's incomprehensible. I did notice that with the screen depth slider at zero, I could see the map screen but it appeared about 1" behind my physical screen at that point... Also, context frames (mousing over a player's name and right clicking for example) would appear 1" OUT of the screen... so it seems that different parts of the UI are being perceived by the 3D vision driver as at TOTALLY different depths, when the UI should ALL be a zero depth period. Even at a zero setting, the chat text redraws were still almost impossible to read because my eyes just wouldn't pop them out. It should be rendered flat anyway.
Pissing around with the convergence (CTRL F5 and F6) is retarded because it simply moves EVERYTHING, including the action bars and map and whatnot either into or out of the screen which really messes with your brain... so any solution involving that crap is off the table - the UI NEEDS to be at screen depth, period. The rest of the world can revolve around it just fine, as in older drivers - again - 1.13 or earlier for WoW.
Not rocket science - you have working drivers, and failing ones... shouldn't be a 6 month fix to make it the way it USED to be.
I tried tonight to run at zero "screen depth" setting in WoW (zero convergence adjustment I think) and it was almost tolerable. All the usual things were way off, but not by as much. I used to run with that setting at about 20% or so and had great success in 1.13 (191.07), but if I try that with any later drivers, 80% of the UI diverges to the point that it's incomprehensible. I did notice that with the screen depth slider at zero, I could see the map screen but it appeared about 1" behind my physical screen at that point... Also, context frames (mousing over a player's name and right clicking for example) would appear 1" OUT of the screen... so it seems that different parts of the UI are being perceived by the 3D vision driver as at TOTALLY different depths, when the UI should ALL be a zero depth period. Even at a zero setting, the chat text redraws were still almost impossible to read because my eyes just wouldn't pop them out. It should be rendered flat anyway.
Pissing around with the convergence (CTRL F5 and F6) is retarded because it simply moves EVERYTHING, including the action bars and map and whatnot either into or out of the screen which really messes with your brain... so any solution involving that crap is off the table - the UI NEEDS to be at screen depth, period. The rest of the world can revolve around it just fine, as in older drivers - again - 1.13 or earlier for WoW.
Not rocket science - you have working drivers, and failing ones... shouldn't be a 6 month fix to make it the way it USED to be.
Core i7 920 @ 3.6Ghz, 6GB 3 Channel, SLi GTX670 2GB, SSD
2) Graphics card?
3) Windows version?[/quote]
1) Viewsonic VX2268WM
2) GTX 260
3) W7 Home Premium 64bit
I can apply the work around similar to whodamanxbox to get all the overlays aligned but with just one tap of CTRL F6 - its unplayable...
edit - whoops 260 [b]not[/b][i][/i] 240
2) Graphics card?
3) Windows version?
1) Viewsonic VX2268WM
2) GTX 260
3) W7 Home Premium 64bit
I can apply the work around similar to whodamanxbox to get all the overlays aligned but with just one tap of CTRL F6 - its unplayable...
edit - whoops 260 not[i][/i] 240
Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.
-------------------
Vitals: Windows 7 64bit, i5 2500 @ 4.4ghz, SLI GTX670, 8GB, Viewsonic VX2268WM
Handy Driver Discussion
Helix Mod - community fixes
Bo3b's Shaderhacker School - How to fix 3D in games
3dsolutionsgaming.com - videos, reviews and 3D fixes
2) GTX 285
3) Vista Ultimate 32-bit
Overlays, maps, minimaps, buffs, debuffs, character preview, login screens, and exp all show up bugged/double/blurry/seperated using almost all convergence settings (unusable).
While your at it, the mouse on the loading screen also doubles (with both hardware and software mouse).
Also, since it seems like no one at NVIDIA has lifted a finger to actually test this out (as it would be grossly apparent what is wrong with any new driver) convergence settings are in wow listed under stereo options as : "screen depth"
You really don't need to be gathering that much data, as all setups have an issue with this game, and it is very clear what the problem is. If you want to recreate it, load up a machine with any monitor, install wow, install latest 3d driver (or any driver released by you guys in since 2009) and just look at the screen through your 3d glasses.
This is not a small issue affecting a small percentage of players, it affects all players using 3d in WoW, and all hardware setups. The only people that can actually get it to work use an ancient driver from when WoW actually worked in 3d.
2) GTX 285
3) Vista Ultimate 32-bit
Overlays, maps, minimaps, buffs, debuffs, character preview, login screens, and exp all show up bugged/double/blurry/seperated using almost all convergence settings (unusable).
While your at it, the mouse on the loading screen also doubles (with both hardware and software mouse).
Also, since it seems like no one at NVIDIA has lifted a finger to actually test this out (as it would be grossly apparent what is wrong with any new driver) convergence settings are in wow listed under stereo options as : "screen depth"
You really don't need to be gathering that much data, as all setups have an issue with this game, and it is very clear what the problem is. If you want to recreate it, load up a machine with any monitor, install wow, install latest 3d driver (or any driver released by you guys in since 2009) and just look at the screen through your 3d glasses.
This is not a small issue affecting a small percentage of players, it affects all players using 3d in WoW, and all hardware setups. The only people that can actually get it to work use an ancient driver from when WoW actually worked in 3d.
2) EVGA GTS250 SLI
3) Windows 7 x64 Professional
Works with 191.07 drivers. UI is totally bugged out with newer drivers. You can fix the text and maps by moving the depth slider, but as soon as anything changes on the UI the new item will screw up and you have touch/move the slider again. The cool down boxes are never correct no matter what I have done. pwnshoppe's post above hit the nail on the head. This is a problem with everyone, no system specs are really needed.
2) EVGA GTS250 SLI
3) Windows 7 x64 Professional
Works with 191.07 drivers. UI is totally bugged out with newer drivers. You can fix the text and maps by moving the depth slider, but as soon as anything changes on the UI the new item will screw up and you have touch/move the slider again. The cool down boxes are never correct no matter what I have done. pwnshoppe's post above hit the nail on the head. This is a problem with everyone, no system specs are really needed.
2) EVGA GTX260 SLI
3) Windows 7 home premium 64Bit
2) EVGA GTX260 SLI
3) Windows 7 home premium 64Bit
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below:
GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
I am also available on Twitter:
www.twitter.com/manuelguzman