Temporary workaround to restore 3D Vision in World of Warcraft following v4.01 patch
  1 / 2    
A patch for the game World of Warcraft was released earlier this month. This patch introduced a bug in the World of Warcraft game user interface which prevents the 3D Vision support setting from working correctly. After a user patches World of Warcraft to version 4.01, the user will find that the in game 3D Vision setting will no longer work.

[url="http://forums.worldofwarcraft.com/thread.html?topicId=27303229042&postId=272794323937&sid=1#2"]http://forums.worldofwarcraft.com/thread.h...937&sid=1#2[/url]

Although 3D Vision support can no longer be enabled through the in game user interface, 3d Vision can still be toggled on or off through the in game console by running either of the two commands below:

To enable 3D stereo:
/script SetCvar("gxStereoEnabled", 1); RestartGx();

To disable 3D Stereo:
/script SetCVar("gxStereoEnabled", 0); RestartGx();

It is recommended that you create custom macros to make it easier to toggle the commands above. For a complete guide on using macros with Blizzard's World of Warcraft, please the URL below:

[url="http://www.worldofwarcraft.com/info/basics/macroguide-one.html"]http://www.worldofwarcraft.com/info/basics...oguide-one.html[/url]

An update is expected at a later date to address this issue.
A patch for the game World of Warcraft was released earlier this month. This patch introduced a bug in the World of Warcraft game user interface which prevents the 3D Vision support setting from working correctly. After a user patches World of Warcraft to version 4.01, the user will find that the in game 3D Vision setting will no longer work.



http://forums.worldofwarcraft.com/thread.h...937&sid=1#2



Although 3D Vision support can no longer be enabled through the in game user interface, 3d Vision can still be toggled on or off through the in game console by running either of the two commands below:



To enable 3D stereo:

/script SetCvar("gxStereoEnabled", 1); RestartGx();



To disable 3D Stereo:

/script SetCVar("gxStereoEnabled", 0); RestartGx();



It is recommended that you create custom macros to make it easier to toggle the commands above. For a complete guide on using macros with Blizzard's World of Warcraft, please the URL below:



http://www.worldofwarcraft.com/info/basics...oguide-one.html



An update is expected at a later date to address this issue.

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
Posted 10/28/2010 02:09 AM   
A patch for the game World of Warcraft was released earlier this month. This patch introduced a bug in the World of Warcraft game user interface which prevents the 3D Vision support setting from working correctly. After a user patches World of Warcraft to version 4.01, the user will find that the in game 3D Vision setting will no longer work.

[url="http://forums.worldofwarcraft.com/thread.html?topicId=27303229042&postId=272794323937&sid=1#2"]http://forums.worldofwarcraft.com/thread.h...937&sid=1#2[/url]

Although 3D Vision support can no longer be enabled through the in game user interface, 3d Vision can still be toggled on or off through the in game console by running either of the two commands below:

To enable 3D stereo:
/script SetCvar("gxStereoEnabled", 1); RestartGx();

To disable 3D Stereo:
/script SetCVar("gxStereoEnabled", 0); RestartGx();

It is recommended that you create custom macros to make it easier to toggle the commands above. For a complete guide on using macros with Blizzard's World of Warcraft, please the URL below:

[url="http://www.worldofwarcraft.com/info/basics/macroguide-one.html"]http://www.worldofwarcraft.com/info/basics...oguide-one.html[/url]

An update is expected at a later date to address this issue.
A patch for the game World of Warcraft was released earlier this month. This patch introduced a bug in the World of Warcraft game user interface which prevents the 3D Vision support setting from working correctly. After a user patches World of Warcraft to version 4.01, the user will find that the in game 3D Vision setting will no longer work.



http://forums.worldofwarcraft.com/thread.h...937&sid=1#2



Although 3D Vision support can no longer be enabled through the in game user interface, 3d Vision can still be toggled on or off through the in game console by running either of the two commands below:



To enable 3D stereo:

/script SetCvar("gxStereoEnabled", 1); RestartGx();



To disable 3D Stereo:

/script SetCVar("gxStereoEnabled", 0); RestartGx();



It is recommended that you create custom macros to make it easier to toggle the commands above. For a complete guide on using macros with Blizzard's World of Warcraft, please the URL below:



http://www.worldofwarcraft.com/info/basics...oguide-one.html



An update is expected at a later date to address this issue.

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

#2
Posted 10/28/2010 02:09 AM   
All

Can anyone post if this works for them? I did it at BlizzCon 2010 and it worked on all of our machines.
All



Can anyone post if this works for them? I did it at BlizzCon 2010 and it worked on all of our machines.

#3
Posted 10/29/2010 04:00 PM   
All

Can anyone post if this works for them? I did it at BlizzCon 2010 and it worked on all of our machines.
All



Can anyone post if this works for them? I did it at BlizzCon 2010 and it worked on all of our machines.

#4
Posted 10/29/2010 04:00 PM   
As of Patch 4.0.1a (Most recent), the issue has been resolved. It was a server side bug
As of Patch 4.0.1a (Most recent), the issue has been resolved. It was a server side bug

#5
Posted 10/29/2010 04:54 PM   
As of Patch 4.0.1a (Most recent), the issue has been resolved. It was a server side bug
As of Patch 4.0.1a (Most recent), the issue has been resolved. It was a server side bug

#6
Posted 10/29/2010 04:54 PM   
Nope, it has not been resolved with 4.0.1a.

Seeing NVidia representative posted this, I'd also throw link that I posted on WoW forums, regarding other issues with WoW and S3D that yet need to be resolved:
[url="http://forums.wow-europe.com/thread.html?topicId=15111073669&sid=1"]http://forums.wow-europe.com/thread.html?t...73669&sid=1[/url]

c&p from my post there:
[i]With latest patch there are new issues with Stereo 3D for WoW.

One of main issues it is not possible anymore to enable/disable S3D by using ingame options under Video->Advanced.
Checking/unchecking tab does nothing.

However, having SET gxStereoEnabled "1" in Config.wtf will enable you to run it in S3D (again unchecking in options will not disable it).
Current workaround is to make 2 macros:
S3D ON:
/script SetCVar("gxStereoEnabled", 1); RestartGx();

S3D OFF:
/script SetCVar("gxStereoEnabled", 0); RestartGx();

Another issue new water effect - by using it, it displays severe graphical distortion which makes it completely unusable with S3D.

There are also some issues with some rendering too. Clouds and some other environmental details (like vortex while dead and similar) are rendered at about 1/2 maximum depth.
This makes an weird looking experience in some cases, when object should be infront of clouds, yet clouds are rendered at closer depth than objects itself (easily visible in example in Dalaran).
This is however better than in 3.x patch, where clouds were rendered at 2D depth, but still not good enough, especially with added extra clouds now.

Another (not as severe) issue could be that some menu screens are not rendered at same depth (more precise characters/mounts/pets) in: character screen, pet screen, mount screen and similar.

One more oddity I noticed was at Halion fight, in shadow realm - orbs would occasionally disappear.

Lastly, enabling DX11 even further breaks things - nameplates are rendered in 2D depth, and possibly even other bugs.

With list of current issues - especially inability to properly enable/disable S3D, WoW should be removed from 'Excellent' rating from NVidia's site.[/i]
Nope, it has not been resolved with 4.0.1a.



Seeing NVidia representative posted this, I'd also throw link that I posted on WoW forums, regarding other issues with WoW and S3D that yet need to be resolved:

http://forums.wow-europe.com/thread.html?t...73669&sid=1



c&p from my post there:

With latest patch there are new issues with Stereo 3D for WoW.



One of main issues it is not possible anymore to enable/disable S3D by using ingame options under Video->Advanced.

Checking/unchecking tab does nothing.



However, having SET gxStereoEnabled "1" in Config.wtf will enable you to run it in S3D (again unchecking in options will not disable it).

Current workaround is to make 2 macros:

S3D ON:

/script SetCVar("gxStereoEnabled", 1); RestartGx();



S3D OFF:

/script SetCVar("gxStereoEnabled", 0); RestartGx();



Another issue new water effect - by using it, it displays severe graphical distortion which makes it completely unusable with S3D.



There are also some issues with some rendering too. Clouds and some other environmental details (like vortex while dead and similar) are rendered at about 1/2 maximum depth.

This makes an weird looking experience in some cases, when object should be infront of clouds, yet clouds are rendered at closer depth than objects itself (easily visible in example in Dalaran).

This is however better than in 3.x patch, where clouds were rendered at 2D depth, but still not good enough, especially with added extra clouds now.



Another (not as severe) issue could be that some menu screens are not rendered at same depth (more precise characters/mounts/pets) in: character screen, pet screen, mount screen and similar.



One more oddity I noticed was at Halion fight, in shadow realm - orbs would occasionally disappear.



Lastly, enabling DX11 even further breaks things - nameplates are rendered in 2D depth, and possibly even other bugs.



With list of current issues - especially inability to properly enable/disable S3D, WoW should be removed from 'Excellent' rating from NVidia's site.

#7
Posted 10/29/2010 08:24 PM   
Nope, it has not been resolved with 4.0.1a.

Seeing NVidia representative posted this, I'd also throw link that I posted on WoW forums, regarding other issues with WoW and S3D that yet need to be resolved:
[url="http://forums.wow-europe.com/thread.html?topicId=15111073669&sid=1"]http://forums.wow-europe.com/thread.html?t...73669&sid=1[/url]

c&p from my post there:
[i]With latest patch there are new issues with Stereo 3D for WoW.

One of main issues it is not possible anymore to enable/disable S3D by using ingame options under Video->Advanced.
Checking/unchecking tab does nothing.

However, having SET gxStereoEnabled "1" in Config.wtf will enable you to run it in S3D (again unchecking in options will not disable it).
Current workaround is to make 2 macros:
S3D ON:
/script SetCVar("gxStereoEnabled", 1); RestartGx();

S3D OFF:
/script SetCVar("gxStereoEnabled", 0); RestartGx();

Another issue new water effect - by using it, it displays severe graphical distortion which makes it completely unusable with S3D.

There are also some issues with some rendering too. Clouds and some other environmental details (like vortex while dead and similar) are rendered at about 1/2 maximum depth.
This makes an weird looking experience in some cases, when object should be infront of clouds, yet clouds are rendered at closer depth than objects itself (easily visible in example in Dalaran).
This is however better than in 3.x patch, where clouds were rendered at 2D depth, but still not good enough, especially with added extra clouds now.

Another (not as severe) issue could be that some menu screens are not rendered at same depth (more precise characters/mounts/pets) in: character screen, pet screen, mount screen and similar.

One more oddity I noticed was at Halion fight, in shadow realm - orbs would occasionally disappear.

Lastly, enabling DX11 even further breaks things - nameplates are rendered in 2D depth, and possibly even other bugs.

With list of current issues - especially inability to properly enable/disable S3D, WoW should be removed from 'Excellent' rating from NVidia's site.[/i]
Nope, it has not been resolved with 4.0.1a.



Seeing NVidia representative posted this, I'd also throw link that I posted on WoW forums, regarding other issues with WoW and S3D that yet need to be resolved:

http://forums.wow-europe.com/thread.html?t...73669&sid=1



c&p from my post there:

With latest patch there are new issues with Stereo 3D for WoW.



One of main issues it is not possible anymore to enable/disable S3D by using ingame options under Video->Advanced.

Checking/unchecking tab does nothing.



However, having SET gxStereoEnabled "1" in Config.wtf will enable you to run it in S3D (again unchecking in options will not disable it).

Current workaround is to make 2 macros:

S3D ON:

/script SetCVar("gxStereoEnabled", 1); RestartGx();



S3D OFF:

/script SetCVar("gxStereoEnabled", 0); RestartGx();



Another issue new water effect - by using it, it displays severe graphical distortion which makes it completely unusable with S3D.



There are also some issues with some rendering too. Clouds and some other environmental details (like vortex while dead and similar) are rendered at about 1/2 maximum depth.

This makes an weird looking experience in some cases, when object should be infront of clouds, yet clouds are rendered at closer depth than objects itself (easily visible in example in Dalaran).

This is however better than in 3.x patch, where clouds were rendered at 2D depth, but still not good enough, especially with added extra clouds now.



Another (not as severe) issue could be that some menu screens are not rendered at same depth (more precise characters/mounts/pets) in: character screen, pet screen, mount screen and similar.



One more oddity I noticed was at Halion fight, in shadow realm - orbs would occasionally disappear.



Lastly, enabling DX11 even further breaks things - nameplates are rendered in 2D depth, and possibly even other bugs.



With list of current issues - especially inability to properly enable/disable S3D, WoW should be removed from 'Excellent' rating from NVidia's site.

#8
Posted 10/29/2010 08:24 PM   
UPDATE: On test server selecting options from menu enables/disables S3D correctly. This is 4.0.3 test patch, so with 4.0.3 on live servers it should be fixed.

Also, seems they fiddled with other things I mentioned too.
Clouds and some environment effects are now at bigger depth, but in some occasions can still seems a bit 'off' - like clouds that should be behind far away mountain or similar.
Character/pet/mount screen and 3D object inside now seem to be rendered at same depth, however when setting convergence for some reason it has more impact on character screen.

Overall, it's improvement.

As for water effect - what they messed up is it seems whole water is rendered at maximum depth (instead where it should be), so it really is messed up.
Hope they fix it soon (believe this one is also on Blizzard side).
UPDATE: On test server selecting options from menu enables/disables S3D correctly. This is 4.0.3 test patch, so with 4.0.3 on live servers it should be fixed.



Also, seems they fiddled with other things I mentioned too.

Clouds and some environment effects are now at bigger depth, but in some occasions can still seems a bit 'off' - like clouds that should be behind far away mountain or similar.

Character/pet/mount screen and 3D object inside now seem to be rendered at same depth, however when setting convergence for some reason it has more impact on character screen.



Overall, it's improvement.



As for water effect - what they messed up is it seems whole water is rendered at maximum depth (instead where it should be), so it really is messed up.

Hope they fix it soon (believe this one is also on Blizzard side).

#9
Posted 10/30/2010 08:30 AM   
UPDATE: On test server selecting options from menu enables/disables S3D correctly. This is 4.0.3 test patch, so with 4.0.3 on live servers it should be fixed.

Also, seems they fiddled with other things I mentioned too.
Clouds and some environment effects are now at bigger depth, but in some occasions can still seems a bit 'off' - like clouds that should be behind far away mountain or similar.
Character/pet/mount screen and 3D object inside now seem to be rendered at same depth, however when setting convergence for some reason it has more impact on character screen.

Overall, it's improvement.

As for water effect - what they messed up is it seems whole water is rendered at maximum depth (instead where it should be), so it really is messed up.
Hope they fix it soon (believe this one is also on Blizzard side).
UPDATE: On test server selecting options from menu enables/disables S3D correctly. This is 4.0.3 test patch, so with 4.0.3 on live servers it should be fixed.



Also, seems they fiddled with other things I mentioned too.

Clouds and some environment effects are now at bigger depth, but in some occasions can still seems a bit 'off' - like clouds that should be behind far away mountain or similar.

Character/pet/mount screen and 3D object inside now seem to be rendered at same depth, however when setting convergence for some reason it has more impact on character screen.



Overall, it's improvement.



As for water effect - what they messed up is it seems whole water is rendered at maximum depth (instead where it should be), so it really is messed up.

Hope they fix it soon (believe this one is also on Blizzard side).

#10
Posted 10/30/2010 08:30 AM   
I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?
I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?

#11
Posted 10/31/2010 12:52 AM   
I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?
I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?

#12
Posted 10/31/2010 12:52 AM   
[quote name='joedeejay' post='1139706' date='Oct 30 2010, 05:52 PM']I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?[/quote]
I think the issue is only if you don't already have the setting in your config.wtf.
[quote name='joedeejay' post='1139706' date='Oct 30 2010, 05:52 PM']I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?

I think the issue is only if you don't already have the setting in your config.wtf.
#13
Posted 10/31/2010 01:18 AM   
[quote name='joedeejay' post='1139706' date='Oct 30 2010, 05:52 PM']I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?[/quote]
I think the issue is only if you don't already have the setting in your config.wtf.
[quote name='joedeejay' post='1139706' date='Oct 30 2010, 05:52 PM']I have been able to enable and disable the option using the standard interface and it is correctly writing into the Config.wtf file?

I think the issue is only if you don't already have the setting in your config.wtf.
#14
Posted 10/31/2010 01:18 AM   
[quote name='ERP' post='1139712' date='Oct 31 2010, 03:18 AM']I think the issue is only if you don't already have the setting in your config.wtf.[/quote]
If you have it in Config.WTF file, it will start as S3D. You can disable it with CTRL+T (or button on dongle).
However, disabling it in Video->Advanced options in game will not disable it.
[quote name='ERP' post='1139712' date='Oct 31 2010, 03:18 AM']I think the issue is only if you don't already have the setting in your config.wtf.

If you have it in Config.WTF file, it will start as S3D. You can disable it with CTRL+T (or button on dongle).

However, disabling it in Video->Advanced options in game will not disable it.

#15
Posted 10/31/2010 06:51 AM   
  1 / 2    
Scroll To Top