Quake3World

Trying to get the most out of my bfg geforce 7800 gtx oc...

1.I have tried com_maxfps 0

But when I do this near the top left hand corner of the screen it says"max_packet_usercmds" and it keeps streaming this for a sec then it goes away..

It seems to be averaging the high 300+ and going into the 400 at this setting..I am running high quality in set up...

Any other tricks..or tips..to get the fps screaming with retaining quality graphics..

:icon25:

online do not set com_maxfps to 0

set it to 125

the more fps the more data that needs to sent and received.

you really don't want your fps uncapped in q3 for a couple reasons: first, your eye really won't be able to distinguish anything beyond about 80, if not lower. second, if your fps go too high it'll really mess with the physics (compare movement at 125 to 300). third, as ax mentioned, uncapped fps will destroy your ping. stick to 125 for online play and maybe 142 for offline.

i have the sneaking feeling that in a perfect world you'd have a great connection and be able to run at 125fps and set cl_maxpackets to 125 with rate 25000 and snaps 40. that would give you the smoothest gameplay.

you need an upstream higher than 128kb to use cl_maxpackets 125, fyi.

also, do you just want to see how high your framerate goes with maxed out settings or are you looking for a decent framerate to play? just do a timedemo to find the avg.:

timedemo 1
demo four

and like these guys said, 125fps is all you want to achieve. most pb enabled servers will kick you for com_maxfps 0 anyway.

menkent wrote:(compare movement at 125 to 300)

Interesting factoid: a consistent 333 FPS will give you an insane speed boost, which is esp. noticeable on jump pads.

and for getting straight up to the quad on DM17 without using a rocket

That's possible in 125 aswell, if you hit the correct spot. ;]

and most pb-enabled servers will lock you at 125, so it's not worth getting used to 333.

Dont really go 1.32 so pb means nothing to me...pb is weak too many cheats..sry...I can go get a hack for pb in like 3 min...that works..at least 1.16n has antibot..that works..cuz not as many hacks they are too busy with 1.32..LoL..

I run my /snaps 60
/rate 40000

Seems lame to cap off the fps, why not get the most out of the card...

also, do you just want to see how high your framerate goes with maxed out settings or are you looking for a decent framerate to play? just do a timedemo to find the avg.:

timedemo 1
demo four

Everytime I do this it says timedemo is cheat protected and kicks me...

aloha wrote:Dont really go 1.32 so pb means nothing to me...pb is weak too many cheats..sry...I can go get a hack for pb in like 3 min...that works..at least 1.16n has antibot..that works..

I challenge you to get a hack that works for PB, then play me on a server with it.

Foo wrote:

aloha wrote:Dont really go 1.32 so pb means nothing to me...pb is weak too many cheats..sry...I can go get a hack for pb in like 3 min...that works..at least 1.16n has antibot..that works..

I challenge you to get a hack that works for PB, then play me on a server with it.

What is this, the mid 14th century ?

Damned straight, my leige

Foo wrote:I challenge you to get a hack that works for PB, then play me on a server with it.

He's right though. PB almost only catches public cheats. Write your own hack, keep it to yourself and you're never going to get caught.

^misantropia^ wrote:

Foo wrote:I challenge you to get a hack that works for PB, then play me on a server with it.

He's right though. PB almost only catches public cheats. Write your own hack, keep it to yourself and you're never going to get caught.

So then by your own definition he's wrong, becuase he can't 'go get a hack'.

Foo wrote:

^misantropia^ wrote:

Foo wrote:I challenge you to get a hack that works for PB, then play me on a server with it.

He's right though. PB almost only catches public cheats. Write your own hack, keep it to yourself and you're never going to get caught.

So then by your own definition he's wrong, becuase he can't 'go get a hack'.

could get a hack then mod it

[FTF]Pyro wrote:

Foo wrote:

^misantropia^ wrote: He's right though. PB almost only catches public cheats. Write your own hack, keep it to yourself and you're never going to get caught.

So then by your own definition he's wrong, becuase he can't 'go get a hack'.

could get a hack then mod it

That's true

aloha wrote:Seems lame to cap off the fps, why not get the most out of the card...

because it screws up your movement. at some point you just float around and can't make jumps.

aloha wrote:Dont really go 1.32 so pb means nothing to me...pb is weak too many cheats..sry...I can go get a hack for pb in like 3 min...that works..at least 1.16n has antibot..that works..cuz not as many hacks they are too busy with 1.32..LoL..

By joining PunkBuster-enabled servers under PR 1.32 you can be assured most if not all public released cheats are detected. While PB is not 100% cheat-proof (especially in respects to privately made and distributed hacks), it does an adequate job of preventing and deterring people from using them. A majority of people playing under 1.16 are cheaters or simply ignorant of newer patches.

Seems lame to cap off the fps, why not get the most out of the card...

A culture of competition has arisen among game enthusiasts with regards to frame rates, with players striving to obtain the highest fps count possible.

Even with expensive monitors that can reach even higher frequencies, the effect is somewhat lost as the human eye has difficulty in perceiving differences in frame rates above around 50-60 fps. Indeed, this is why televisions operate at 50 Hz and 60 Hz with PAL and NTSC standards respectively.

It should also be noted that there is a rather large controversy over what is known as the "feel" of the game frame rate. It is argued that games with extremely high frame rates "feel" better and smoother than those that are just getting by. This is especially true in games such as a first-person shooter. There is often a noticeable choppyness perceived in most computer rendered video, despite it being above the flicker fusion frequency. Despite this, as already stated, you you should set your com_maxFps to 125 and r_displayRefresh 125, as there is little if no advantage toward setting to a higher setting (unless you plan to use 333, which is looked down upon for obvious reasons).

aloha wrote: Trying to get the most out of my bfg geforce 7800 gtx oc...

If you're looking to benchmark your video card either download 3dMark2k5 or benchmark your card with more recently released games, such as Battlefield 2, Doom 3, Far Cry, or Half-Life 2. If you're trying to get the most out of it, overclock the card.

aloha wrote:Everytime I do this it says timedemo is cheat protected and kicks me...

Under PR 1.16 the commands to run a timedemo are:

• /timedemo 1 [enter]
  /demo demo001 [enter]

aloha wrote:I run my /snaps 60 /rate 40000

I use the following settings:

• // network connection
  seta rate "25000"
  seta snaps "40"
  seta cl_maxPackets "125"
  seta cl_packetdup "1"
  seta cl_timeNudge "-12"
  seta cl_allowDownload "0"
  seta cg_smoothClients "0"
  seta cg_optimiseBW "1"

Snaps is determined by the server, usually it is set from 20-40. So it will automatically adjust this value to the maximum according to the server, (so if sv_fps is set to 40 and your snaps is at 60 it will change to 40).

Good Luck and Happy Fragging!

I stopped playing at fragpimp clanarena because they hacked osp to allow 333 fps. Now the n00bs over there can finally make bridge-to-rail.

Cooldown wrote:Snaps is determined by the server, usually it is set from 20-40. So it will automatically adjust this value according to the server.

Is this right? It caught me as off when I read that is all.

CoolDown. Could you look in your lists of quoted stuff and double check that one?
Which don't get wrong on this, comes in handy for answering the
same question asked time and time again.

Yes it is adjusted server side. You can check with the /pb_cvarval command (so it would be /pb_cvarval snaps) on most servers it will say 40. When you set it to /snaps 60 in-game yourself while on a server it does not actually change it, just that cosmetically it shows what you have inputed, but it has no effect (and here, it won't even tell you 'server-restricted snaps (40)... adjusting') like it does to say cl_timenudge. Just one of those things I guess.

Strangely enough pb_cvarval does not work on every pb server. My guess is that there is a server command for enabling the client to allow these checks, and some servers have it disabled?

I don't think that's exactly right. My understanding:

The server determines SV_FPS. Which is the number of unique updates the serve produces per second. SNAPS is the number of updates you request from the server per second.

The server doesn't (to my knowledge) transmit the same update to the same client more than once, so if you set snaps to 1000, you'll still only get the 20 that the server wants to push. On the other hand, if you set snaps to 5, you'll only get 5 out of the 20 updates (for example) that the server has to offer per second.

But I don't know the Q3 netcode. This is an assumption I've made from reading a bit and seeing what happens when you play with the setting.

I think it only forces you the server restricted value if you go over it, but lower than it should allow it (to compensate for the fact that not everyone has uber leet connections)... although, if there is a _min and _max cvar, I suppose you would be able to set both and 40 and then everyone would be imposed by it.

PieceMaker wrote: Is this right? It caught me as off when I read that is all.

To elaborate, snaps is the maximum number of ’server frames’ or ’snapshots’ which you will recieve from a server per second. The default value of 20 matches up with a server’s default sv_fps of 20. Snaps is the client setting that related to sv_fps server side, so snaps and sv_fps dictate how much the server will send you, not client to server info. You can never receive more info via snaps than what sv_fps is set at.

If you set your snaps higher than the rate at which the server is sending out snapshots, it will not do anything. So for example, if the sv_fps is set to 20 on the server, anyone using snaps of 40, 60, 100 will actually still only receive 20 from the server, so it limits client receive info only. Those packet sizes can vary though, but shouldn't vary above the maxrate command (this is from server to client). However, if a server has say sv_fps 100 (sending 100 snapshots a second), and you are bandwidth-starved, you can set snaps to a lower value.

I hope I clarified that for you.

dzjepp wrote:I think it only forces you the server restricted value if you go over it, but lower than it should allow it

Correct.

Another thing: snaps is clamped to the 1-30 range. From server/sv_client.c: I think you could call this a bug because it effectively cancels the effect of running a server at, say, 40 FPS.