Constant having 60 fps
Moderator: Moderators
Constant having 60 fps
As comming back to the scene (by the way, hey! ) i'm constantly trying to fix my AQ2. I forgot all the fancy commands, which means that I need some help
First of all, i finally managed to fix my Q2 and it ran nicely, but suddenly (after closing and opening again) I lagged a little bit. Meaning, that if I shoot, the shot comes like ½ sec after.
I tried typing timerefresh, and wtf, i had 60 fps. I tried changing cl_maxfps, but that doesn't help - cl_maxfps 10 = 60fps , cl_maxfps 200= 60fps. Also, if I run a local server I have ping 16. Constantly.
If anyone has had a problem like this, feel free to help me out Also, if anyone has some uber gfx settings, post away.
-krede
First of all, i finally managed to fix my Q2 and it ran nicely, but suddenly (after closing and opening again) I lagged a little bit. Meaning, that if I shoot, the shot comes like ½ sec after.
I tried typing timerefresh, and wtf, i had 60 fps. I tried changing cl_maxfps, but that doesn't help - cl_maxfps 10 = 60fps , cl_maxfps 200= 60fps. Also, if I run a local server I have ping 16. Constantly.
If anyone has had a problem like this, feel free to help me out Also, if anyone has some uber gfx settings, post away.
-krede
/care
-
- is connecting
- Posts: 14
- Joined: Thu Sep 14, 2006 2:19 am
- Location: fi
- Contact:
off course setting vsynch to 0 is the wrong way, unless you are trying to measure up your maximum quake rendering performance or you need a really high packetrate for some wierdo jumps.
otherwise setting vsynch (gl_swapinterval) to 0 will just make you harm. will not allow you to see "more frames" per second. it will just generate all sorts of visual artifacts to the game and break dynamic lightning.
the right way that actually increses the number of frames you see per second is setting (in aprq2) vid_displayfrequency to what is your monitors maxmium refreshrate with your quake's resolution (it defaults to 60, hence your constant 60fps in quake). possible choises are for exmple 75 85 100 or 120. not all monitors support the bigger refreshrates so you have to either know the right refreshrate or just try differet values.
oh and same command for r1q2 is vid_forcedrefresh, dont know about other clients.
edit: seems that vid_displayfrequency is broken in aprq2 1.20... well it worked atleast in 1.8b2... maybe in 1.19, maybe not... try it... or use r1q2
otherwise setting vsynch (gl_swapinterval) to 0 will just make you harm. will not allow you to see "more frames" per second. it will just generate all sorts of visual artifacts to the game and break dynamic lightning.
the right way that actually increses the number of frames you see per second is setting (in aprq2) vid_displayfrequency to what is your monitors maxmium refreshrate with your quake's resolution (it defaults to 60, hence your constant 60fps in quake). possible choises are for exmple 75 85 100 or 120. not all monitors support the bigger refreshrates so you have to either know the right refreshrate or just try differet values.
oh and same command for r1q2 is vid_forcedrefresh, dont know about other clients.
edit: seems that vid_displayfrequency is broken in aprq2 1.20... well it worked atleast in 1.8b2... maybe in 1.19, maybe not... try it... or use r1q2
Last edited by starttimartti on Mon Dec 18, 2006 11:49 am, edited 1 time in total.
-
- killed itself
- Posts: 401
- Joined: Tue Dec 28, 2004 1:52 pm
- In-game Name: kk'lok
- Location: oslo
- Mouse: diamondback
- Location: no
- Contact:
starttimartti wrote:off course setting vsynch to 0 is the wrong way, unless you are trying to measure up your maximum quake rendering performance or you need a really high packetrate for some wierdo jumps.
otherwise setting vsynch (gl_swapinterval) to 0 will just make you harm. will not allow you to see "more frames" per second. it will just generate all sorts of visual artifacts to the game and break dynamic lightning.
the right way that actually increses the number of frames you see per second is setting (in aprq2) vid_displayfrequency to what is your monitors maxmium refreshrate with your quake's resolution (it defaults to 60, hence your constant 60fps in quake). possible choises are for exmple 75 85 100 or 120. not all monitors support the bigger refreshrates so you have to either know the right refreshrate or just try differet values.
oh and same command for r1q2 is vid_forcedrefresh, dont know about other clients.
And you dont have to turn v_sync off on your graffic card to enable this?
I pleasure myself, everyday.
>kk'lok
>kk'lok
-
- is connecting
- Posts: 14
- Joined: Thu Sep 14, 2006 2:19 am
- Location: fi
- Contact:
no. vsynch stays on.Lotus wrote:And you dont have to turn v_sync off on your graffic card to enable this?
edit: after i actually read the first post, i have to say that i have no clue if my "guide" will help the original poster's particular problem at all (if before alt-tabbing quake was running more smoothly than 60 fps).
but still... in 99% of cases, turning v-synch off will not benefit you in any way.
turning monitor refresh rate up, on the other hand, most definately will.
Last edited by starttimartti on Thu Dec 14, 2006 6:50 pm, edited 2 times in total.
-
- tripped on its own grenade
- Posts: 325
- Joined: Thu Jun 02, 2005 6:16 am
- In-game Name: Keeent
- Location: no
fuct wrote:If it were the same would there be a need for two commands?ZoRoXo wrote:is gl_swapinterval the same as gl_ext_swapinterval?
look, im just curios. And im not fond of rethorical questions.
ok so your signature says "In case of emergency my ass can be used as a floatation device" so are you really that fat? hows that for a rethorical question huh?
Aka. kK >> Keeent
( ) ( )
(^_^)
(~)(~)
( ) ( )
(^_^)
(~)(~)