fixedtime (0-1) ?
Moderators: Forum moderators, developers
fixedtime (0-1) ?
fixedtime (0 or 1)
//info? Run without dropping frames
ITS CHEAT PROTECTED BY PB?
FIRST...is the information that i could get searching around right?
2) ? why would this be a problem if left open as an option?
3) what would happen if all clients were forced serverside 2 use the cvar set 1 ?
//if pb dos'nt force kick on the clients if set?
//info? Run without dropping frames
ITS CHEAT PROTECTED BY PB?
FIRST...is the information that i could get searching around right?
2) ? why would this be a problem if left open as an option?
3) what would happen if all clients were forced serverside 2 use the cvar set 1 ?
//if pb dos'nt force kick on the clients if set?
-
- Posts: 126
- Joined: Sat Sep 25, 2004 7:12 am
- Contact:
ReyalP:=> ok... still input on what the cvar changes would still be very nice information.... and the range of valid values...
..and allso if pb will deafault kick?... never minde the last bit.. i can check that myself...
Nail:=> sounds interesting... if ur right...that is if the client engine waits if it is not on the "most recent snap" ?
if its a buggy option "alias" of r_finish set 1 that just hurts fps in general... then its a no go zone...
The Necromancer:=> so u think its a "event spacer option" if i understand u right ie... set 100 "simulates" com_maxfps 100.... set "0" = com_maxfps 0... and this is default client behaviour? concering the timmings?
..and allso if pb will deafault kick?... never minde the last bit.. i can check that myself...
Nail:=> sounds interesting... if ur right...that is if the client engine waits if it is not on the "most recent snap" ?
if its a buggy option "alias" of r_finish set 1 that just hurts fps in general... then its a no go zone...
The Necromancer:=> so u think its a "event spacer option" if i understand u right ie... set 100 "simulates" com_maxfps 100.... set "0" = com_maxfps 0... and this is default client behaviour? concering the timmings?
gotenks wrote:from what i read it is boolean (so it probably checks 0 or not 0), it makes your computer render all your frames (fps) even though you can only display at the rate of your monitor... so 1 sec will take up to 2 sec's to be displayed (asuming you have 120fps and 60hz monitor)
That's the only place it is used.Quake 3 GPL qcommon/common.c:Com_ModifyMsec wrote:Code: Select all
if ( com_fixedtime->integer ) { msec = com_fixedtime->integer; } else if ( com_timescale->value ) { msec *= com_timescale->value; } else if (com_cameraMode->integer) { msec *= com_timescale->value; }
Get your own copy of quake3 at ftp://ftp.idsoftware.com/idstuff/source ... source.zip
send lawyers, guns and money