Welcome to PBBans
![]() |
Welcome to PBBans, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of PBBans by signing in or creating an account.
|
Max Fps
#1
Posted Oct 12, 2008 - 04:27 PM
#2
Posted Oct 12, 2008 - 05:10 PM
If you really don't want players to go over that then set PB to kick players who have com_maxfps set above that.
#3
Posted Oct 12, 2008 - 05:27 PM
It is in this setting right? What would be the setting for it?
#4
Posted Oct 12, 2008 - 10:08 PM
#5
Posted Oct 13, 2008 - 01:24 AM
would lock fps to a minimum of 43 and a maximum of 150.
#6
Posted Oct 13, 2008 - 06:35 AM
pb_sv_cvar com_maxfps OUT 151 1000
why? game default is 0 (no setting/uncapped)
#7
Posted Oct 13, 2008 - 03:17 PM
#8
Posted Oct 13, 2008 - 03:28 PM
toxin, on Oct 13th 2008, 10:17 PM, said:
IN 43 150: means higher than 43 and lower than 150, or inside 43 and 150
OUT 43 150: Means not between 43 and 150, or not inside 43 and 150
Green is allowed values:
IN 43 150: --------------43-------------------------150--------------
OUT 43 150: --------------43-------------------------150--------------
#9
Posted Oct 13, 2008 - 03:42 PM
Benway, on Oct 13th 2008, 12:35 PM, said:
Have you ever tried setting it to 0 Benway.
I did and got well over 1000 fps. Trouble is the server can't handle it and you start jerking all over the place like you've got bad lag.
On the capping of maxfps at 125 as per Clanbase rules I've got an open mind and think that it should be left to server admins to do what they feel is right.
Personally I allow 333 fps on my server and use it myself. However I still play on servers capped at 125 and just adjust my settings accordingly.
I honestly don't think the 333 thing is any big deal, just slightly better jumps.
toxin OUT means exactly what it says. A players settings must be outside those values.
IN means a players settings must be within those values.
So pb_sv_cvar "com_maxfps" IN 43 150 then the player must have his fps set between 43 and 150, ie it can't be set at 42 or below or 151 and above.
The other way round for out.
#11
Posted Oct 13, 2008 - 03:55 PM
toxin, on Oct 13th 2008, 10:17 PM, said:
pb_sv_cvar [cvar_name] [IN|OUT|INCLUDE|EXCLUDE] [Param1] [optional_Param2] ... PB will kick players with cvars in/outside the specified range.
IN = setting has to be between Param1 & Param2 inclusive.
If no Param2 is present, setting must equal Param1.
OUT = setting may not be between Param1 & Param2, both Param1 & Param2 are not allowed as well.
If no Param2 present, setting may not equal Param1.
INCLUDE = setting must include the string given in Param1.
EXCLUDE = setting may not include the string given in Param1.
Does not change or remove previous blocks of same cvar, both will operate, unless a "pb_sv_cvarempty" was issued.
thus
pb_sv_cvar com_maxfps OUT 0.0001 43
pb_sv_cvar com_maxfps OUT 151 1000
pb_sv_cvar com_maxfps OUT 0
would equal
pb_sv_cvar com_maxfps IN 44 150 // 43 is connected with a no-recoil exploit of q3e
as said i see no use to restrict 0 (uncapped) as only a stable FPS value will have any effect on jumping/recoil/hitboxes.
333 is in connection with a hitbox delay exploit (player is hard to hit), has not v. much to do with jumping. Sorry to destruct your illusions, but this "unfair advantage" to be able to do the special jumps is a result of practice, i.e. of wasting time on boring Trickjump Maps like e.g. this guy --> who always used com_maxfps 76 or 125. (no, to restrict these values was ... dorky)
P.S.:
]\com_maxfps "com_maxfps" is:"125" default:"85" ]\condump sof2_fps.txtwhatever.
#12
Posted Oct 13, 2008 - 04:05 PM
#13
Posted Oct 13, 2008 - 04:12 PM
Edited by toxin, Oct 13, 2008 - 04:13 PM.
#14
Posted Oct 13, 2008 - 04:29 PM
toxin, on Oct 13th 2008, 11:12 PM, said:
hugin, on Oct 13th 2008, 10:28 PM, said:
IN 43 150 : --------------43-------------------------150--------------
OUT 43 150 : --------------43-------------------------150--------------
Edited by Benway, Mar 30, 2013 - 08:29 AM.
: i just set the colors for the numbers as well, just to fix the slackness ... as they were Black (neutral, what they are NOT)
#15
Posted Oct 16, 2008 - 05:00 PM
#16
Posted Oct 16, 2008 - 05:15 PM
#17
Posted Oct 16, 2008 - 05:16 PM
#18
Posted Mar 30, 2013 - 08:33 AM
toxin, on Oct 16, 2008 - 05:00 PM, said:
well, that* was my point to recommend :
A.
pb_sv_cvar com_maxfps OUT 0.000001 43
plus B.
pb_sv_cvar com_maxfps OUT 151 1000
rather than C.
pb_sv_cvar com_maxfps IN 43 150
for two reasons:
1.) C. does not equal A. + B.
go figure why i mentioned the old and forgotten no-recoil exploit @43 FPS, IN 43 150 will allow both values 150 and 43 ,
while A. disallows 43 , so the (almost) proper equivalent was: IN 44 150
2.) (almost) ...*some games have no default setting for com_maxfps (WTF is SoF?) and PB will handle an empty cvar value like the particular cvar was set to 0.
So restricting pb_sv_cvar com_maxfps IN 44 150 would kick for com_maxfps 0 as well for com_maxfps "" ( = if nothing is set by user and if the game uses uncapped com_maxfps = "" as default), thus A. reads OUT 0.000001 43 and not OUT 0 43
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users












