Search results

you forgot cl_noprint 1 cg_drawfps 0

RGB FOR IMPS RGB EQUALITY NAO

some1 suggested to move the proj scoping delay before the (+) overlay applies to give feedback when exactly its ready to fire, pls implement

i like some of your ideas, however most of them seem too chaotic to be ever implemented

mb2_moseisley when?

not sure which option is better anyway, just found out that the bug fucks up the shoulder cameras too, the crosshair is in the wrong place

i edited it obv

hopefully it will work in 60 frames now

let's host a server in japan, this way everyone has equal ping

new vid thanks @Shady for support edit: accidentally the vid rendered in 30 fps, will post again after rerendering

oh come on, he was trolling, can't you tell? thanks for the tip, will try this later if only...

not a bug, that's perfectly normal disabling dynamic crosshair makes it stay in the middle of the screen no matter what, which becomes the point where bolts hit only if you are in first person view protip: disable the dynamic crosshair only for first person bind O "cg_dynamiccrosshair 1...

kek please, increase com_maxfps, my eyes hurt

does anyone else also experience more often crashing of the mb2 and jamme after patch? i can provide crashlogs if necessary

stfu chaos, this bug is serious business i'm gonna try this soon, hopefully it will keep the crosshair in the middle of the screen edit: it helps a bit, it doesn't sway much now, but it still feels a little weird when crouching and when i'm close to a wall facing the other direction

it's no use been playing with 0.9 values for a year now, it's much better (unless the bug occurs) reposting old post just in case:

whatever, crosshair swaying should be optional, not serverside /ignore chaos

try playing with cg_truefov value, i'm not sure if it's the right cvar, but the name suggests it

hold the mouse cursor over the crosshair and notice that in firs vid it sways a lot in the direction of strafe, and on the second one just a bit in the opposite direction