Hi.
I've been trying to get 3dVision working on my main workstation. This is not going well.
When i started messing with it all full-screen content using 3dvision was presented at 85hz.
Since this is rather uncomfortable I used the test-program and told it to always use 100 hz.
This changed nothing.
After trying a couple more times going back and forth between the testprogram and my viewer; the test-program
now decided to be stupid as well, claiming to use the proper refresh while in reality using 85 hz.
Trying a couple more times and rebooting suddenly resulted in that the refresh-rate now was 75 hz instead...
In a desperate attempt to fix this I added a new custom resolution a couple of pixels smaller than normal and
defined the only usable refreshrate as 100 hz.
Now my desktop is at 100 hz, the test-program is at 100 hz, Sview crashes and Nvidia 3d-player say that it
cannot create directx 9 device.
(Both these programs works fine at the normal resolution just veeery flickery..)
Any suggestions?
/Nisse
Info:
Card 8600gt
Monitor: Large crt, connected without ddc so all refreshrates and resolutions are available for windows.
OS: Server 2008 r1 ( Yeah I know...but it is like vista without all the crap.)
Replying to myself here. Problem solved but not without a lot of headache.
Installed a fresh copy of Vista 32 bit on a different computer and moved the 8600 to that machine.
Installing only the drivers resulted in the same problem.
Since I was now running 32 bit I downloaded RefreshLock and ran that.
This showed that the computer considered the maximum safe refresh to be 85 hz.
Very odd since both windows and nvidia's control panel happily changed to frequencies much higher than that.
Obviously directx cares nothing for what windows think about the monitor and looks directly at
the monitor-driver and when this is one of the default non-specific drivers it decides that 85hz is
a reasonable maximum limit.
Solutions:
*Let the monitor answer over ddc. This does not often work since those answers often are very restrictive.
*Install the model-specific driver, if you can find one then it might work. Or the same thing might happen as with ddc.
*Install a modified driver....
This does work. Problem is that this might work too well...so that directx suddenly decides 200 hz is a good number..
This is what I did. Using davemon.inf (http://www.videoi.com/~pietro/monitor/).
I checked the "apply this frequency to all.." in the nvidia test-program. This seems to stick for me but
it might be a good idea to edit the davemon file and replace the v and h intervals with what the manual for your
monitor claims...
Why Nvidia can't alter their 3d-wizard to detect when these problems occur is beyond me..
A simple box saying something like "You seem to be missing a proper driver for your monitor and
will be limited to a maximum of 85 hz when using the 3d-function in fullscreen." would have
saved me and probably many others a lot of headache!!
I've been trying to get 3dVision working on my main workstation. This is not going well.
When i started messing with it all full-screen content using 3dvision was presented at 85hz.
Since this is rather uncomfortable I used the test-program and told it to always use 100 hz.
This changed nothing.
After trying a couple more times going back and forth between the testprogram and my viewer; the test-program
now decided to be stupid as well, claiming to use the proper refresh while in reality using 85 hz.
Trying a couple more times and rebooting suddenly resulted in that the refresh-rate now was 75 hz instead...
In a desperate attempt to fix this I added a new custom resolution a couple of pixels smaller than normal and
defined the only usable refreshrate as 100 hz.
Now my desktop is at 100 hz, the test-program is at 100 hz, Sview crashes and Nvidia 3d-player say that it
cannot create directx 9 device.
(Both these programs works fine at the normal resolution just veeery flickery..)
Any suggestions?
/Nisse
Info:
Card 8600gt
Monitor: Large crt, connected without ddc so all refreshrates and resolutions are available for windows.
OS: Server 2008 r1 ( Yeah I know...but it is like vista without all the crap.)
I've been trying to get 3dVision working on my main workstation. This is not going well.
When i started messing with it all full-screen content using 3dvision was presented at 85hz.
Since this is rather uncomfortable I used the test-program and told it to always use 100 hz.
This changed nothing.
After trying a couple more times going back and forth between the testprogram and my viewer; the test-program
now decided to be stupid as well, claiming to use the proper refresh while in reality using 85 hz.
Trying a couple more times and rebooting suddenly resulted in that the refresh-rate now was 75 hz instead...
In a desperate attempt to fix this I added a new custom resolution a couple of pixels smaller than normal and
defined the only usable refreshrate as 100 hz.
Now my desktop is at 100 hz, the test-program is at 100 hz, Sview crashes and Nvidia 3d-player say that it
cannot create directx 9 device.
(Both these programs works fine at the normal resolution just veeery flickery..)
Any suggestions?
/Nisse
Info:
Card 8600gt
Monitor: Large crt, connected without ddc so all refreshrates and resolutions are available for windows.
OS: Server 2008 r1 ( Yeah I know...but it is like vista without all the crap.)
Installed a fresh copy of Vista 32 bit on a different computer and moved the 8600 to that machine.
Installing only the drivers resulted in the same problem.
Since I was now running 32 bit I downloaded RefreshLock and ran that.
This showed that the computer considered the maximum safe refresh to be 85 hz.
Very odd since both windows and nvidia's control panel happily changed to frequencies much higher than that.
Obviously directx cares nothing for what windows think about the monitor and looks directly at
the monitor-driver and when this is one of the default non-specific drivers it decides that 85hz is
a reasonable maximum limit.
Solutions:
*Let the monitor answer over ddc. This does not often work since those answers often are very restrictive.
*Install the model-specific driver, if you can find one then it might work. Or the same thing might happen as with ddc.
*Install a modified driver....
This does work. Problem is that this might work too well...so that directx suddenly decides 200 hz is a good number..
This is what I did. Using davemon.inf (http://www.videoi.com/~pietro/monitor/).
I checked the "apply this frequency to all.." in the nvidia test-program. This seems to stick for me but
it might be a good idea to edit the davemon file and replace the v and h intervals with what the manual for your
monitor claims...
Why Nvidia can't alter their 3d-wizard to detect when these problems occur is beyond me..
A simple box saying something like "You seem to be missing a proper driver for your monitor and
will be limited to a maximum of 85 hz when using the 3d-function in fullscreen." would have
saved me and probably many others a lot of headache!!
/nisse
Installed a fresh copy of Vista 32 bit on a different computer and moved the 8600 to that machine.
Installing only the drivers resulted in the same problem.
Since I was now running 32 bit I downloaded RefreshLock and ran that.
This showed that the computer considered the maximum safe refresh to be 85 hz.
Very odd since both windows and nvidia's control panel happily changed to frequencies much higher than that.
Obviously directx cares nothing for what windows think about the monitor and looks directly at
the monitor-driver and when this is one of the default non-specific drivers it decides that 85hz is
a reasonable maximum limit.
Solutions:
*Let the monitor answer over ddc. This does not often work since those answers often are very restrictive.
*Install the model-specific driver, if you can find one then it might work. Or the same thing might happen as with ddc.
*Install a modified driver....
This does work. Problem is that this might work too well...so that directx suddenly decides 200 hz is a good number..
This is what I did. Using davemon.inf (http://www.videoi.com/~pietro/monitor/).
I checked the "apply this frequency to all.." in the nvidia test-program. This seems to stick for me but
it might be a good idea to edit the davemon file and replace the v and h intervals with what the manual for your
monitor claims...
Why Nvidia can't alter their 3d-wizard to detect when these problems occur is beyond me..
A simple box saying something like "You seem to be missing a proper driver for your monitor and
will be limited to a maximum of 85 hz when using the 3d-function in fullscreen." would have
saved me and probably many others a lot of headache!!
/nisse