Help for users with the Red Warning Message on 3D Vision Monitors Please read this thread!
1 / 2
Hi All
We've been reviewing the red warning messages internally at NVIDIA and are trying to find solutions to users that are seeing this message on 3D Vision monitors. I want to be clear that this thread is for 3D Vision monitors or projectors, not for DLP TVs, HDMI 1.4, etc.
First, if you are using Release 265 drivers, we have now posted matching 3D Vision Controller drivers for all GeForce GPU driver versions. You can see that list of downloads here http://www.nvidia.com/object/3d-vision-geforce-driver.html So if you are using Release 265 GeForce drivers and have this message, please upgrade to a matching 3D Vision Controller driver. After installing the driver, unplug and replug the emitter and see if this address your problem.
Second, if you are using Release 265 drivers and still have problems, please try upgrading to the Release 270 Beta drivers, v270.51. In release 270, we bundle the 3D Vision Controller driver with the GeForce driver from now on Here is a link to the 64-bit driver http://www.nvidia.com/object/win7-winvista-64bit-270.51-beta-driver.html Please post your results with that driver and if the red warning message goes away for you.
Thanks and I hope this helps users with this error.
We've been reviewing the red warning messages internally at NVIDIA and are trying to find solutions to users that are seeing this message on 3D Vision monitors. I want to be clear that this thread is for 3D Vision monitors or projectors, not for DLP TVs, HDMI 1.4, etc.
First, if you are using Release 265 drivers, we have now posted matching 3D Vision Controller drivers for all GeForce GPU driver versions. You can see that list of downloads here http://www.nvidia.com/object/3d-vision-geforce-driver.html So if you are using Release 265 GeForce drivers and have this message, please upgrade to a matching 3D Vision Controller driver. After installing the driver, unplug and replug the emitter and see if this address your problem.
Second, if you are using Release 265 drivers and still have problems, please try upgrading to the Release 270 Beta drivers, v270.51. In release 270, we bundle the 3D Vision Controller driver with the GeForce driver from now on Here is a link to the 64-bit driver http://www.nvidia.com/object/win7-winvista-64bit-270.51-beta-driver.html Please post your results with that driver and if the red warning message goes away for you.
Thanks and I hope this helps users with this error.
[quote name='cyberheater' date='01 April 2011 - 06:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
[/quote]
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
Andrew, It still happens in 270.52.
There are logic errors in the decision to print it, minimally once it's triggered it happens every time you launch anything in 3D until you restart.
Here's a repro, works in surround on 270.52.
3 x Acer 236HZ, 580GT SLI, 270.52, i7 950
It's a little convoluted, but I suspect the issue is games forcing a none 3D refresh rate, nvidia attempting to enable 3D throwing the message, there is then no way to get rid of the message short of restarting the computer.
Setup your 3D Vision to force 110Hz in all games (check the apply this refresh rate to all games box).
Start WoW with the DX11 renderer, set it to 6000x1080@109Hz - the DX11 renderer rounds refresh rates down not to nearest AFAICS.
Push the emitter button, assuming it didn't crash. exit. otherwise relaunch and try again.
edit the config.wtf file and remove the line from the bottom of the file that forces the DX11 renderer.
Start WoW with the DX9 renderer, you'll correctly get the red message.
WoW will have identified that there is no 109Hz mode (because the DX9 renderer rounds to nearest) and forcibly set the refresh rate to 29Hz (why 29 I don't know).
Exit
Edit the config.wtf, change the refresh rate from 29 to 110.
Restart WoW in Dx9 mode, assuming stereo is set in the config.wtf you now incorrectly get the message.
In fact running anything from this point will show the message until the machine is restarted.
There are logic errors in the decision to print it, minimally once it's triggered it happens every time you launch anything in 3D until you restart.
Here's a repro, works in surround on 270.52.
3 x Acer 236HZ, 580GT SLI, 270.52, i7 950
It's a little convoluted, but I suspect the issue is games forcing a none 3D refresh rate, nvidia attempting to enable 3D throwing the message, there is then no way to get rid of the message short of restarting the computer.
Setup your 3D Vision to force 110Hz in all games (check the apply this refresh rate to all games box).
Start WoW with the DX11 renderer, set it to 6000x1080@109Hz - the DX11 renderer rounds refresh rates down not to nearest AFAICS.
Push the emitter button, assuming it didn't crash. exit. otherwise relaunch and try again.
edit the config.wtf file and remove the line from the bottom of the file that forces the DX11 renderer.
Start WoW with the DX9 renderer, you'll correctly get the red message.
WoW will have identified that there is no 109Hz mode (because the DX9 renderer rounds to nearest) and forcibly set the refresh rate to 29Hz (why 29 I don't know).
Exit
Edit the config.wtf, change the refresh rate from 29 to 110.
Restart WoW in Dx9 mode, assuming stereo is set in the config.wtf you now incorrectly get the message.
In fact running anything from this point will show the message until the machine is restarted.
[quote name='jenson' date='03 April 2011 - 01:50 AM' timestamp='1301813428' post='1218408']
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
[/quote]
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
[quote name='jenson' date='03 April 2011 - 01:50 AM' timestamp='1301813428' post='1218408']
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
[quote name='andrewf@nvidia' date='03 April 2011 - 08:25 PM' timestamp='1301862353' post='1218708']
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
[/quote]
* Is the user interface (UI) presenting a problem that has already occurred? If not, the message isn't an error. If the user being alerted of a condition that might cause a problem in the future, use a warning message.
* Can the problem be prevented without causing confusion? If so, prevent the problem instead. For example, use controls that are constrained to valid values instead of using unconstrained controls that may require error messages. Also, disable controls when clicking would result in error, as long as it's obvious why the control is disabled.
* Can the problem be corrected automatically? If so, handle the problem and suppress the error message.
* [b]Are users likely to perform an action or change their behavior as the result of the message? If not, the condition doesn't justify interrupting the user so it's better to suppress the error.[/b]
* Is the problem relevant when users are actively using other programs? If so, consider showing the problem using a notification area icon.
* [b]Is the problem not related to the current user activity, does it not require immediate user action, and can users freely ignore it? If so, use an action failure notification instead.[/b]
* Does the problem relate to the status of a background task within a primary window? If so, consider showing the problem using a status bar.
* Are the primary target users IT professionals? If so, consider using an alternative feedback mechanism, such as log file entries or e-mail alerts. IT professionals strongly prefer log files for non-critical information.
.....
You want to know if the user experiences an error so you can correct it. Show the error "one time" so the user knows, then make the error go away. The user experience is more important above all. Sorry, I'm not trying to be a know it all or anything. It just pains me to see the core rules of error reporting violated by such a reputable company. (and yes i understand you're not using message box windows but the core concepts still apply)
[quote name='cyberheater' date='01 April 2011 - 06:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
[/quote]
This statement justifies the above response.
This is just an opinion you guys will ultimately do what you feel is best. Just my 2 cents.
[quote name='andrewf@nvidia' date='03 April 2011 - 08:25 PM' timestamp='1301862353' post='1218708']
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
* Is the user interface (UI) presenting a problem that has already occurred? If not, the message isn't an error. If the user being alerted of a condition that might cause a problem in the future, use a warning message.
* Can the problem be prevented without causing confusion? If so, prevent the problem instead. For example, use controls that are constrained to valid values instead of using unconstrained controls that may require error messages. Also, disable controls when clicking would result in error, as long as it's obvious why the control is disabled.
* Can the problem be corrected automatically? If so, handle the problem and suppress the error message.
* Are users likely to perform an action or change their behavior as the result of the message? If not, the condition doesn't justify interrupting the user so it's better to suppress the error.
* Is the problem relevant when users are actively using other programs? If so, consider showing the problem using a notification area icon.
* Is the problem not related to the current user activity, does it not require immediate user action, and can users freely ignore it? If so, use an action failure notification instead.
* Does the problem relate to the status of a background task within a primary window? If so, consider showing the problem using a status bar.
* Are the primary target users IT professionals? If so, consider using an alternative feedback mechanism, such as log file entries or e-mail alerts. IT professionals strongly prefer log files for non-critical information.
.....
You want to know if the user experiences an error so you can correct it. Show the error "one time" so the user knows, then make the error go away. The user experience is more important above all. Sorry, I'm not trying to be a know it all or anything. It just pains me to see the core rules of error reporting violated by such a reputable company. (and yes i understand you're not using message box windows but the core concepts still apply)
[quote name='cyberheater' date='01 April 2011 - 06:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
This statement justifies the above response.
This is just an opinion you guys will ultimately do what you feel is best. Just my 2 cents.
Still not supported Acer 5360 at 100 Hz :(
I use it with force 100Hz mode, but the red warning message is there.
Why not disappear after 15 sec? This time is enough to read for everyone..
[quote name='andrewf@nvidia' date='05 April 2011 - 01:13 PM' timestamp='1302034417' post='1219849']
Hi
Can you get us a screenshot of the exact red message you are seeing? Or at least tell us the exact words?
[/quote]
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[quote name='ERP' date='05 April 2011 - 09:20 PM' timestamp='1302056452' post='1219985']
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[quote name='cyberheater' date='01 April 2011 - 07:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
[/quote]
+1 to this, Nobody cares that there is a problem in 3D as long as the 3D is rendering properly, and if it doesn't we don't need an erroor message to realize it either. If the nvidia 3D driver were not free I wouldn't be using it.
I'm not saying the driver is bad, it's fairly good to the point that it does what it has to do: Render (some) games in 3D. But beyond that point it's just annoying.
[quote name='cyberheater' date='01 April 2011 - 07:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
+1 to this, Nobody cares that there is a problem in 3D as long as the 3D is rendering properly, and if it doesn't we don't need an erroor message to realize it either. If the nvidia 3D driver were not free I wouldn't be using it.
I'm not saying the driver is bad, it's fairly good to the point that it does what it has to do: Render (some) games in 3D. But beyond that point it's just annoying.
We've been reviewing the red warning messages internally at NVIDIA and are trying to find solutions to users that are seeing this message on 3D Vision monitors. I want to be clear that this thread is for 3D Vision monitors or projectors, not for DLP TVs, HDMI 1.4, etc.
First, if you are using Release 265 drivers, we have now posted matching 3D Vision Controller drivers for all GeForce GPU driver versions. You can see that list of downloads here http://www.nvidia.com/object/3d-vision-geforce-driver.html So if you are using Release 265 GeForce drivers and have this message, please upgrade to a matching 3D Vision Controller driver. After installing the driver, unplug and replug the emitter and see if this address your problem.
Second, if you are using Release 265 drivers and still have problems, please try upgrading to the Release 270 Beta drivers, v270.51. In release 270, we bundle the 3D Vision Controller driver with the GeForce driver from now on Here is a link to the 64-bit driver http://www.nvidia.com/object/win7-winvista-64bit-270.51-beta-driver.html Please post your results with that driver and if the red warning message goes away for you.
Thanks and I hope this helps users with this error.
We've been reviewing the red warning messages internally at NVIDIA and are trying to find solutions to users that are seeing this message on 3D Vision monitors. I want to be clear that this thread is for 3D Vision monitors or projectors, not for DLP TVs, HDMI 1.4, etc.
First, if you are using Release 265 drivers, we have now posted matching 3D Vision Controller drivers for all GeForce GPU driver versions. You can see that list of downloads here http://www.nvidia.com/object/3d-vision-geforce-driver.html So if you are using Release 265 GeForce drivers and have this message, please upgrade to a matching 3D Vision Controller driver. After installing the driver, unplug and replug the emitter and see if this address your problem.
Second, if you are using Release 265 drivers and still have problems, please try upgrading to the Release 270 Beta drivers, v270.51. In release 270, we bundle the 3D Vision Controller driver with the GeForce driver from now on Here is a link to the 64-bit driver http://www.nvidia.com/object/win7-winvista-64bit-270.51-beta-driver.html Please post your results with that driver and if the red warning message goes away for you.
Thanks and I hope this helps users with this error.
Please just give us the option to turn the error message off.
[/quote]
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
Please just give us the option to turn the error message off.
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
There are logic errors in the decision to print it, minimally once it's triggered it happens every time you launch anything in 3D until you restart.
Here's a repro, works in surround on 270.52.
3 x Acer 236HZ, 580GT SLI, 270.52, i7 950
It's a little convoluted, but I suspect the issue is games forcing a none 3D refresh rate, nvidia attempting to enable 3D throwing the message, there is then no way to get rid of the message short of restarting the computer.
Setup your 3D Vision to force 110Hz in all games (check the apply this refresh rate to all games box).
Start WoW with the DX11 renderer, set it to 6000x1080@109Hz - the DX11 renderer rounds refresh rates down not to nearest AFAICS.
Push the emitter button, assuming it didn't crash. exit. otherwise relaunch and try again.
edit the config.wtf file and remove the line from the bottom of the file that forces the DX11 renderer.
Start WoW with the DX9 renderer, you'll correctly get the red message.
WoW will have identified that there is no 109Hz mode (because the DX9 renderer rounds to nearest) and forcibly set the refresh rate to 29Hz (why 29 I don't know).
Exit
Edit the config.wtf, change the refresh rate from 29 to 110.
Restart WoW in Dx9 mode, assuming stereo is set in the config.wtf you now incorrectly get the message.
In fact running anything from this point will show the message until the machine is restarted.
There are logic errors in the decision to print it, minimally once it's triggered it happens every time you launch anything in 3D until you restart.
Here's a repro, works in surround on 270.52.
3 x Acer 236HZ, 580GT SLI, 270.52, i7 950
It's a little convoluted, but I suspect the issue is games forcing a none 3D refresh rate, nvidia attempting to enable 3D throwing the message, there is then no way to get rid of the message short of restarting the computer.
Setup your 3D Vision to force 110Hz in all games (check the apply this refresh rate to all games box).
Start WoW with the DX11 renderer, set it to 6000x1080@109Hz - the DX11 renderer rounds refresh rates down not to nearest AFAICS.
Push the emitter button, assuming it didn't crash. exit. otherwise relaunch and try again.
edit the config.wtf file and remove the line from the bottom of the file that forces the DX11 renderer.
Start WoW with the DX9 renderer, you'll correctly get the red message.
WoW will have identified that there is no 109Hz mode (because the DX9 renderer rounds to nearest) and forcibly set the refresh rate to 29Hz (why 29 I don't know).
Exit
Edit the config.wtf, change the refresh rate from 29 to 110.
Restart WoW in Dx9 mode, assuming stereo is set in the config.wtf you now incorrectly get the message.
In fact running anything from this point will show the message until the machine is restarted.
My Blog
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
[/quote]
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
LOL, over at nvidia the shortest distance between two points is definitely NOT A LINE.
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
[/quote]
http://msdn.microsoft.com/en-us/library/aa511267.aspx
* Is the user interface (UI) presenting a problem that has already occurred? If not, the message isn't an error. If the user being alerted of a condition that might cause a problem in the future, use a warning message.
* Can the problem be prevented without causing confusion? If so, prevent the problem instead. For example, use controls that are constrained to valid values instead of using unconstrained controls that may require error messages. Also, disable controls when clicking would result in error, as long as it's obvious why the control is disabled.
* Can the problem be corrected automatically? If so, handle the problem and suppress the error message.
* [b]Are users likely to perform an action or change their behavior as the result of the message? If not, the condition doesn't justify interrupting the user so it's better to suppress the error.[/b]
* Is the problem relevant when users are actively using other programs? If so, consider showing the problem using a notification area icon.
* [b]Is the problem not related to the current user activity, does it not require immediate user action, and can users freely ignore it? If so, use an action failure notification instead.[/b]
* Does the problem relate to the status of a background task within a primary window? If so, consider showing the problem using a status bar.
* Are the primary target users IT professionals? If so, consider using an alternative feedback mechanism, such as log file entries or e-mail alerts. IT professionals strongly prefer log files for non-critical information.
.....
You want to know if the user experiences an error so you can correct it. Show the error "one time" so the user knows, then make the error go away. The user experience is more important above all. Sorry, I'm not trying to be a know it all or anything. It just pains me to see the core rules of error reporting violated by such a reputable company. (and yes i understand you're not using message box windows but the core concepts still apply)
[quote name='cyberheater' date='01 April 2011 - 06:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
[/quote]
This statement justifies the above response.
This is just an opinion you guys will ultimately do what you feel is best. Just my 2 cents.
Hi
There are numerous reasons why this message occurs. Simply giving you an option to disable it is not a solution. We have to fix the problem and determine why it occurs since it indicates a problem.
http://msdn.microsoft.com/en-us/library/aa511267.aspx
* Is the user interface (UI) presenting a problem that has already occurred? If not, the message isn't an error. If the user being alerted of a condition that might cause a problem in the future, use a warning message.
* Can the problem be prevented without causing confusion? If so, prevent the problem instead. For example, use controls that are constrained to valid values instead of using unconstrained controls that may require error messages. Also, disable controls when clicking would result in error, as long as it's obvious why the control is disabled.
* Can the problem be corrected automatically? If so, handle the problem and suppress the error message.
* Are users likely to perform an action or change their behavior as the result of the message? If not, the condition doesn't justify interrupting the user so it's better to suppress the error.
* Is the problem relevant when users are actively using other programs? If so, consider showing the problem using a notification area icon.
* Is the problem not related to the current user activity, does it not require immediate user action, and can users freely ignore it? If so, use an action failure notification instead.
* Does the problem relate to the status of a background task within a primary window? If so, consider showing the problem using a status bar.
* Are the primary target users IT professionals? If so, consider using an alternative feedback mechanism, such as log file entries or e-mail alerts. IT professionals strongly prefer log files for non-critical information.
.....
You want to know if the user experiences an error so you can correct it. Show the error "one time" so the user knows, then make the error go away. The user experience is more important above all. Sorry, I'm not trying to be a know it all or anything. It just pains me to see the core rules of error reporting violated by such a reputable company. (and yes i understand you're not using message box windows but the core concepts still apply)
[quote name='cyberheater' date='01 April 2011 - 06:18 PM' timestamp='1301681908' post='1217586']
Please just give us the option to turn the error message off.
This statement justifies the above response.
This is just an opinion you guys will ultimately do what you feel is best. Just my 2 cents.
I use it with force 100Hz mode, but the red warning message is there.
Why not disappear after 15 sec? This time is enough to read for everyone..
I use it with force 100Hz mode, but the red warning message is there.
Why not disappear after 15 sec? This time is enough to read for everyone..
[/quote]
Hi Jenson
Great points and I actually agree with you that we need to make the message more actionable.
In the meantime, I have to figure out why its not working properly. So if anyone has problems, please post details on how it occurs.
Hi Jenson
Great points and I actually agree with you that we need to make the message more actionable.
In the meantime, I have to figure out why its not working properly. So if anyone has problems, please post details on how it occurs.
[/quote]
Hi
Can you provide me some more details:
- GPU make/model
- Operating system type
Thanks.
Hi
Can you provide me some more details:
- GPU make/model
- Operating system type
Thanks.
Hi
Can you provide me some more details:
- GPU make/model
- Operating system type
Thanks.
[/quote]
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
Hi
Can you provide me some more details:
- GPU make/model
- Operating system type
Thanks.
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
My Blog
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
[/quote]
Hi
Thank for you the info, we will begin the investigation.
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
Hi
Thank for you the info, we will begin the investigation.
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
[/quote]
Hi
Can you get us a screenshot of the exact red message you are seeing? Or at least tell us the exact words?
2x EVGA GTX580 SC
OS WIn7 Ultimate 64bit SP1
Hi
Can you get us a screenshot of the exact red message you are seeing? Or at least tell us the exact words?
Hi
Can you get us a screenshot of the exact red message you are seeing? Or at least tell us the exact words?
[/quote]
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[attachment=20504:Red Message.JPG]
[attachment=20505:Red Message 2.JPG]
Hi
Can you get us a screenshot of the exact red message you are seeing? Or at least tell us the exact words?
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[attachment=20504:Red Message.JPG]
[attachment=20505:Red Message 2.JPG]
My Blog
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[attachment=26634:Red Message.JPG]
[attachment=26635:Red Message 2.JPG]
[/quote]
Hi
Thanks for the picture. Can you confirm this occurs with every game and the message never goes away?
Attached below, note that I can now reproduce this trivially. I doubt surround has anything to do with it,but I haven't tested in none surround modes.
Setup WoW to run using DX9 in 3D @110Hz.
edit the config.wtf file, change the refresh rate to 109Hz
run WoW - message appears (incorrectly because the driver forced the refresh rate to 110Hz - see below)
exit WoW
edit config.wtf, set refresh rat back to 110
run WoW - message still appears
At this point the message will appear on every 3D app regardless of resolution or refresh rate.
[attachment=26634:Red Message.JPG]
[attachment=26635:Red Message 2.JPG]
Hi
Thanks for the picture. Can you confirm this occurs with every game and the message never goes away?
Please just give us the option to turn the error message off.
[/quote]
+1 to this, Nobody cares that there is a problem in 3D as long as the 3D is rendering properly, and if it doesn't we don't need an erroor message to realize it either. If the nvidia 3D driver were not free I wouldn't be using it.
I'm not saying the driver is bad, it's fairly good to the point that it does what it has to do: Render (some) games in 3D. But beyond that point it's just annoying.
Please just give us the option to turn the error message off.
+1 to this, Nobody cares that there is a problem in 3D as long as the 3D is rendering properly, and if it doesn't we don't need an erroor message to realize it either. If the nvidia 3D driver were not free I wouldn't be using it.
I'm not saying the driver is bad, it's fairly good to the point that it does what it has to do: Render (some) games in 3D. But beyond that point it's just annoying.