The refresh rate problem under Windows 2K (stuck at 60hz in Direct3D and
OpenGL Games) is well known.
The fixes for 2K are also well known. NVRevFix takes care of it in 2K.
However, they have purposely disabled support in XP in this program, citing
some kind of hardware detection issue.
So, anyone know how to work around this under Windows XP for OpenGL?
It's easy to fix for Direct3D. I just use the over-ride feature in DXDiag.
However, this doesn't change OpenGL.
OpenGL is far superior to Direct3D in Nascar Racing 4, and I want to switch
back to it as soon as possible.
TIA!
-Larry
Not sure what you mean, as I can set any refresh rate I want in XP in the
monitor tab using a GF2 Ultra. This is the same rate that D3D and OGL use.
Iain
"Larry" <[email hidden]> wrote in message
news:pmrf7.134517$[email hidden]...
> The refresh rate problem under Windows 2K (stuck at 60hz in Direct3D and
> OpenGL Games) is well known.
>
> The fixes for 2K are also well known. NVRevFix takes care of it in 2K.
>
> However, they have purposely disabled support in XP in this program,citing
> some kind of hardware detection issue.
>
> So, anyone know how to work around this under Windows XP for OpenGL?
>
> It's easy to fix for Direct3D. I just use the over-ride feature inDXDiag.
> However, this doesn't change OpenGL.
>
> OpenGL is far superior to Direct3D in Nascar Racing 4, and I want toswitch
Quoted text (7 lines)
> back to it as soon as possible. > > TIA! > > -Larry > >No, that's not correct. If you have the capability to check your refresh
rate _directly on the monitor_ (most do via an on-screen control), you will
find that whenever a Direct3D or OpenGL screen is in action, the refresh
rate drops to 60hz.
Direct3D and OpenGL do NOT use the 2D refresh rate at all. It's completely
separate.
-Larry
"Iain Mackenzie" <[email hidden]> wrote in message
news:Litf7.1619$[email hidden]...
Quoted text (32 lines)
> Not sure what you mean, as I can set any refresh rate I want in XP in the > monitor tab using a GF2 Ultra. This is the same rate that D3D and OGL use. > Iain > > "Larry" <[email hidden]> wrote in message > news:pmrf7.134517$[email hidden]... > > The refresh rate problem under Windows 2K (stuck at 60hz in Direct3D and > > OpenGL Games) is well known. > > > > The fixes for 2K are also well known. NVRevFix takes care of it in 2K. > > > > However, they have purposely disabled support in XP in this program, > citing > > some kind of hardware detection issue. > > > > So, anyone know how to work around this under Windows XP for OpenGL? > > > > It's easy to fix for Direct3D. I just use the over-ride feature in > DXDiag. > > However, this doesn't change OpenGL. > > > > OpenGL is far superior to Direct3D in Nascar Racing 4, and I want to > switch > > back to it as soon as possible. > > > > TIA! > > > > -Larry > > > > > >Eh, no. I say again, D3D and OGL use the same refresh rate that I set it to
in the monitor tab and DOES NOT drop to 60Hz. It's a fact! My monitor
tells me what rate it uses on screen when it changes mode.
Sorry if it doesn't work for you.
Iain
"Larry" <[email hidden]> wrote in message
news:8Uvf7.135568$[email hidden]...
> No, that's not correct. If you have the capability to check your refresh
> rate _directly on the monitor_ (most do via an on-screen control), youwill
> find that whenever a Direct3D or OpenGL screen is in action, the refresh
> rate drops to 60hz.
>
> Direct3D and OpenGL do NOT use the 2D refresh rate at all. It'scompletely
the
> > monitor tab using a GF2 Ultra. This is the same rate that D3D and OGLuse.
> > Iain
> >
> > "Larry" <[email hidden]> wrote in message
> > news:pmrf7.134517$[email hidden]...
> > > The refresh rate problem under Windows 2K (stuck at 60hz in Direct3Dand
> > > OpenGL Games) is well known.
> > >
> > > The fixes for 2K are also well known. NVRevFix takes care of it in2K.
Quoted text (7 lines)
> separate. > > -Larry > > "Iain Mackenzie" <[email hidden]> wrote in message > news:Litf7.1619$[email hidden]... > > Not sure what you mean, as I can set any refresh rate I want in XP inQuoted text (24 lines)
> > > > > > However, they have purposely disabled support in XP in this program, > > citing > > > some kind of hardware detection issue. > > > > > > So, anyone know how to work around this under Windows XP for OpenGL? > > > > > > It's easy to fix for Direct3D. I just use the over-ride feature in > > DXDiag. > > > However, this doesn't change OpenGL. > > > > > > OpenGL is far superior to Direct3D in Nascar Racing 4, and I want to > > switch > > > back to it as soon as possible. > > > > > > TIA! > > > > > > -Larry > > > > > > > > > > > >"Iain Mackenzie" <[email hidden]> kirjoitti viestiss�
news:_ywf7.2440$[email hidden]...
> Eh, no. I say again, D3D and OGL use the same refresh rate that I set itto
> in the monitor tab and DOES NOT drop to 60Hz. It's a fact! My monitor
> tells me what rate it uses on screen when it changes mode.
> Sorry if it doesn't work for you.
> Iain
WinNT-based w2k and WinXP differ here from w9x/me -systems. Do you still
stand behind your words?
If yes, I think many people would like to know what kind of directx/nvidia
driver configuration you are using :)
--
Mika Takala
[email hidden]
Please remove the invalid parts from my email address if replying by email.
I created these http://www.catalog.com/paint/tmp/xprefresh.zip to solve the
problem for myself.
Use these registry files at your own risk
Not sure if the fact that I'm using a Sony Trinitron monitor will cause a
problem for you or not. At 1280x1024 my refresh rate is 100Hz. At 1024x768
it may be get set as high as 144Hz. I can't remember - I'm back on WinMe
and that's what it shows now.
These registry entries will take away all the lowest refresh rate entries so
that Windows XP is forced to use the highest (for my monitor). You can take
the chance with these or search your own registry and make the changes your
self. BACKUP your registry first if you decide to use mine.
David
"Mika Takala" <[email hidden]> wrote in
message news:9lmaaj$2k6$[email hidden]...
email.
>
>
Quoted text (19 lines)
> "Iain Mackenzie" <[email hidden]> kirjoitti viestiss� > news:_ywf7.2440$[email hidden]... > > Eh, no. I say again, D3D and OGL use the same refresh rate that I set it > to > > in the monitor tab and DOES NOT drop to 60Hz. It's a fact! My monitor > > tells me what rate it uses on screen when it changes mode. > > Sorry if it doesn't work for you. > > Iain > > WinNT-based w2k and WinXP differ here from w9x/me -systems. Do you still > stand behind your words? > > If yes, I think many people would like to know what kind of directx/nvidia > driver configuration you are using :) > > -- > Mika Takala > [email hidden] > Please remove the invalid parts from my email address if replying byOK, I sort of take it back. I changed my desktop to 100Hz and the D3D/OGL
modes kick out of 100 into 75Hz. It does not drop to 60 though, definitely
75 in all resolutions.
Iain
"Mika Takala" <[email hidden]> wrote in
message news:9lmaaj$2k6$[email hidden]...
email.
>
>
Quoted text (19 lines)
> "Iain Mackenzie" <[email hidden]> kirjoitti viestiss� > news:_ywf7.2440$[email hidden]... > > Eh, no. I say again, D3D and OGL use the same refresh rate that I set it > to > > in the monitor tab and DOES NOT drop to 60Hz. It's a fact! My monitor > > tells me what rate it uses on screen when it changes mode. > > Sorry if it doesn't work for you. > > Iain > > WinNT-based w2k and WinXP differ here from w9x/me -systems. Do you still > stand behind your words? > > If yes, I think many people would like to know what kind of directx/nvidia > driver configuration you are using :) > > -- > Mika Takala > [email hidden] > Please remove the invalid parts from my email address if replying byOk, I know the answer.
You ain't runing Windows 2000 or XP...
You are running 9x of some sort.
Different animal.
-Larry
"Iain Mackenzie" <[email hidden]> wrote in message
news:_ywf7.2440$[email hidden]...
> Eh, no. I say again, D3D and OGL use the same refresh rate that I set itto
refresh
Quoted text (9 lines)
> in the monitor tab and DOES NOT drop to 60Hz. It's a fact! My monitor > tells me what rate it uses on screen when it changes mode. > Sorry if it doesn't work for you. > Iain > > > "Larry" <[email hidden]> wrote in message > news:8Uvf7.135568$[email hidden]... > > No, that's not correct. If you have the capability to check yourQuoted text (53 lines)
> > rate _directly on the monitor_ (most do via an on-screen control), you > will > > find that whenever a Direct3D or OpenGL screen is in action, the refresh > > rate drops to 60hz. > > > > Direct3D and OpenGL do NOT use the 2D refresh rate at all. It's > completely > > separate. > > > > -Larry > > > > "Iain Mackenzie" <[email hidden]> wrote in message > > news:Litf7.1619$[email hidden]... > > > Not sure what you mean, as I can set any refresh rate I want in XP in > the > > > monitor tab using a GF2 Ultra. This is the same rate that D3D and OGL > use. > > > Iain > > > > > > "Larry" <[email hidden]> wrote in message > > > news:pmrf7.134517$[email hidden]... > > > > The refresh rate problem under Windows 2K (stuck at 60hz in Direct3D > and > > > > OpenGL Games) is well known. > > > > > > > > The fixes for 2K are also well known. NVRevFix takes care of it in > 2K. > > > > > > > > However, they have purposely disabled support in XP in this program, > > > citing > > > > some kind of hardware detection issue. > > > > > > > > So, anyone know how to work around this under Windows XP for OpenGL? > > > > > > > > It's easy to fix for Direct3D. I just use the over-ride feature in > > > DXDiag. > > > > However, this doesn't change OpenGL. > > > > > > > > OpenGL is far superior to Direct3D in Nascar Racing 4, and I want to > > > switch > > > > back to it as soon as possible. > > > > > > > > TIA! > > > > > > > > -Larry > > > > > > > > > > > > > > > > > > > >If you haven't already done it, try this--
Start>Run>type "dxdiag" (minus quotes)>More Help (once DX Tool
appears)>override
That will fix the 60hz problem.
Alanb
"Larry" <[email hidden]> wrote in message
news:pmrf7.134517$[email hidden]...
> The refresh rate problem under Windows 2K (stuck at 60hz in Direct3D and
> OpenGL Games) is well known.
>
> The fixes for 2K are also well known. NVRevFix takes care of it in 2K.
>
> However, they have purposely disabled support in XP in this program,citing
> some kind of hardware detection issue.
>
> So, anyone know how to work around this under Windows XP for OpenGL?
>
> It's easy to fix for Direct3D. I just use the over-ride feature inDXDiag.
> However, this doesn't change OpenGL.
>
> OpenGL is far superior to Direct3D in Nascar Racing 4, and I want toswitch
Quoted text (7 lines)
> back to it as soon as possible. > > TIA! > > -Larry > >No. I am able to read the headers in posts. I'm running XP RC1 with GF2
Ultra.
But, I did some experimentation - see other post - and if I change my
desktop rate to say 100, all D3D and OGL modes kick me back to 75 NOT 60Hz.
Iain
"Larry" <[email hidden]> wrote in message
news:wcDf7.137303$[email hidden]...
refresh
in
> > the
> > > > monitor tab using a GF2 Ultra. This is the same rate that D3D andOGL
> > use.
> > > > Iain
> > > >
> > > > "Larry" <[email hidden]> wrote in message
> > > > news:pmrf7.134517$[email hidden]...
> > > > > The refresh rate problem under Windows 2K (stuck at 60hz inDirect3D
> > and
> > > > > OpenGL Games) is well known.
> > > > >
> > > > > The fixes for 2K are also well known. NVRevFix takes care of itin
> > 2K.
> > > > >
> > > > > However, they have purposely disabled support in XP in thisprogram,
> > > > citing
> > > > > some kind of hardware detection issue.
> > > > >
> > > > > So, anyone know how to work around this under Windows XP forOpenGL?
> > > > >
> > > > > It's easy to fix for Direct3D. I just use the over-ride featurein
> > > > DXDiag.
> > > > > However, this doesn't change OpenGL.
> > > > >
> > > > > OpenGL is far superior to Direct3D in Nascar Racing 4, and I wantto
