By enabling V-Sync through hardware, the hardware actually has to work harder (go figure...) to do less work as it has to manually override its rendering paths every time it draws a scene to stop at a point rather than just having it render as fast as it can.
The better option is to limit the frames to your refresh rate through software rather than hardware (If you have a grunty CPU use software limiting.... if u have a grunt vid card use vsync limiting.... if u have crap for both... ur boned... ur not gonna get enough frames to see screen tearing anyway lol)
eg. if your refresh rate is 85... then do fps_max 85 in Half-Life.
As for the half-life menu... it is set at 640x480... nothing can be done about this unfortunately.
As for programs to fix the refresh rate bug.
As someone mentioned earlier... the best is Refresh Force... from the maker of Refresh Lock.... Refresh Force is actually pretty much Refresh Lock v2.
Refresh Force - <a href='http://www.pagehosting.co.uk/rf/' target='_blank'>http://www.pagehosting.co.uk/rf/</a>
Do not use the nVidia Refresh Tool as it is driver specific... if nVidia change their driver structure again... u get boned.
Refresh Force relies on Monitor drivers (which are uniform and have to follow a certain format so they won't change)
Refresh Lock overwrote the Windows display settings before entering into DirectX or OpenGL mode and this required RL to be running in the background. RF doesn't need to be left running... All it does is delete all the other possibly refresh rates for the particular resolution thus forcing windows to use the refresh rate specified.
The refresh rate at which eye strain is less noticeable is at 72hz. But the higher your refresh rate, the better for your eyes. At 60hz... your eyes WILL water.
You know you have V-Sync on when your fps hits a wall. ie. if your refresh rate is 75, your fps will never go above 75 but it can still go below.
oh... and one more thing... net_graph 3 is the optimal net graph to use as it uses the same amount of resources as cl_showfps 1
Good thing i am running HL in resolution where my monitor supports 100Hz and my graphiccard does 100fps <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo-->
I dropped resolutions to play 1.04/5 mainly because of the fps thing. I'll go back up once 1.1 comes out to something a little better looking <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
<!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo--> *Ahem* I belive Thing may appreciate this.... it goes a little something like this. *AHEM* OMG BUMP TEH POSTR CUZ IT R TEH COOL WITHOUT ITR I CANT NOT FIX MEH VYSNC PROPRELY! I R WANT STUICKY THREAD.
This concludes this evenings, "Bump". Good Day.
P.S. This Thread is teh pwnt. (I played Counter-Strike Today, you nub.) LOL
ThinGLord of wub and vlaaiJoin Date: 2003-04-11Member: 15400Members, Reinforced - Supporter
Oh my god, is it just me or is this post just soooooooooooooooooooooooo STICKY that it's very hard to get rid off the first page, damn what stickyness, this must be the stickiest post in a long time, so usefull, and uberly STICKY, that someone should really sticky it <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
on topic: for when the Rooster comes back from holidays:
Roo, ingame, fps can vary, like fluctuate from 70-99 very fast, so leap kills won't always be efficient, especially when your around alot of structures. Is there a way to optimize this, or should I just stay in areas where the fps is constant so I can leap the crap out of em?
I read all FOUR PAGES THOUGH and i coulnd't find how to disable vsync <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo--> <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo--> <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo--> plz repeat how to do it.
ThinGLord of wub and vlaaiJoin Date: 2003-04-11Member: 15400Members, Reinforced - Supporter
edited July 2003
<i>"You find it by right clicking your desktop, clicking on Properties, then clicking the "Settings" tab, then clicking on the advanced button, then clicking on your video card tab (i.e. GeForce4 Ti4200), then clicking on OpenGL settings, and then setting "v-sync" to On."</i>
quoted from Uh-Oh
Search function is your friend <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
*The thread is stickied, yayness!
[edit] Set vsync to OFF <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo--> [/edit]
Thing, currently the best way to deal with varying fps (I have the exact same problem) is to try to look at the floor when leaping in built-up areas. Looking directly down on a turret will keep your fps high, and enable you to leap it in 2 leaps (about 1.4ish actually), and usually yields a blind side on a TF. I know of no effective way to make the fps stay high in such areas short of adjusting your graphics right down to horribly poor (and then it's still a hit on the fps!)
Comments
By enabling V-Sync through hardware, the hardware actually has to work harder (go figure...) to do less work as it has to manually override its rendering paths every time it draws a scene to stop at a point rather than just having it render as fast as it can.
The better option is to limit the frames to your refresh rate through software rather than hardware (If you have a grunty CPU use software limiting.... if u have a grunt vid card use vsync limiting.... if u have crap for both... ur boned... ur not gonna get enough frames to see screen tearing anyway lol)
eg. if your refresh rate is 85... then do fps_max 85 in Half-Life.
As for the half-life menu... it is set at 640x480... nothing can be done about this unfortunately.
As for programs to fix the refresh rate bug.
As someone mentioned earlier... the best is Refresh Force... from the maker of Refresh Lock.... Refresh Force is actually pretty much Refresh Lock v2.
Refresh Force - <a href='http://www.pagehosting.co.uk/rf/' target='_blank'>http://www.pagehosting.co.uk/rf/</a>
Do not use the nVidia Refresh Tool as it is driver specific... if nVidia change their driver structure again... u get boned.
Refresh Force relies on Monitor drivers (which are uniform and have to follow a certain format so they won't change)
Refresh Lock overwrote the Windows display settings before entering into DirectX or OpenGL mode and this required RL to be running in the background. RF doesn't need to be left running... All it does is delete all the other possibly refresh rates for the particular resolution thus forcing windows to use the refresh rate specified.
The refresh rate at which eye strain is less noticeable is at 72hz. But the higher your refresh rate, the better for your eyes. At 60hz... your eyes WILL water.
You know you have V-Sync on when your fps hits a wall. ie. if your refresh rate is 75, your fps will never go above 75 but it can still go below.
oh... and one more thing... net_graph 3 is the optimal net graph to use as it uses the same amount of resources as cl_showfps 1
Roo
This concludes this evenings, "Bump". Good Day.
P.S. This Thread is teh pwnt. (I played Counter-Strike Today, you nub.) LOL
on topic:
for when the Rooster comes back from holidays:
Roo, ingame, fps can vary, like fluctuate from 70-99 very fast, so leap kills won't always be efficient, especially when your around alot of structures. Is there a way to optimize this, or should I just stay in areas where the fps is constant so I can leap the crap out of em?
Cheers
*pouts*
quoted from Uh-Oh
Search function is your friend <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
*The thread is stickied, yayness!
[edit]
Set vsync to OFF <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
[/edit]
I know of no effective way to make the fps stay high in such areas short of adjusting your graphics right down to horribly poor (and then it's still a hit on the fps!)
Roo
"enable conformant openGl texture clamp behaviour". It was off so i turned it on. (hehe) what is it. I got a geoforce 2 mx400 with 64 mb
in fact i think i'll turn it off again.
So what is it again?? (guessing it's a thingy that may limit something and we don't want that. hehe)
cheers
sealcomm