A problem with Urban Terror?

Ever since like 3.0, I've had like this lag problem. It only happends when I am using an automatic weapon such as LR or MP5K. If I am sniping, I am dead accurate, even at real close range, but for some reason I cant hit what I am aiming at using auto's. I have to aim like a few steps behind them. I have played around with the cl_timenudge command, no help there.

Did I get like a bad download of the release?

Has anyone else had this problem?

I am more confident using my sr8 at close range instead of my secondary.

Ya make sure your aiming at the guy, it helps

timenudge is locked in urt anyways doesn't do shit... and maybe you got cg_smoothclients set to 1 try experimenting with that on 1 or 0.
"Power in the hands of a few" -Steve Saleen

Thanx man, I'll try it.

No help with that command, still havin the problem. Prolly (not to be confused with brolly) will end up re-formatting and re-installing.

Originally posted by: aBc|KEEPER
Ever since like 3.0, I've had like this lag problem. It only happends when I am using an automatic weapon such as LR or MP5K. If I am sniping, I am dead accurate, even at real close range, but for some reason I cant hit what I am aiming at using auto's. I have to aim like a few steps behind them. I have played around with the cl_timenudge command, no help there.

Did I get like a bad download of the release?

Has anyone else had this problem?

I am more confident using my sr8 at close range instead of my secondary.

Yeah I have the same thing and I use burst with the g36 for extra accuracy so its not just you. As far as I know its standard in urban. Could be something in my config though I play pretty much default so maybe others might not experience it if they really twed their cfg out.

Ok fixed my problem.

I had my com_hunkmegs set to like 800, it was way to high and was using virtual memory.

Hehehe!

what should hunkmegs be set to?

Well, I heard it should be 2/3 of your memory. but that wasnt the case for me, that was to high. I have a gig of ddr and I have mine set to 350 now. Oh well, just play around with it.

You don't need that much memory allocated. Quake3 was released in 1999 (or was it 98' ? Anyway...) and most systems didn't even have that much memory. Hence, you won't see any performance gains if you go above around 120 megs. So basically, by allocating that much ram, you are just making your computer slower every time you load and quit out of quake. If you have any other configuration questions, I'll be glad to address those as well.

Wow, your the best nadsaq, all other saq's should be jealous.

I would (supersticiously?) only use exponents of 2.
Post edited by BludShoT at 3/26/2004 4:42:22 PM

well, there are hunkmegs, zonemegs, and sound megs. 3 different things.

hunkmegs for models (players, weapons, items mostly), zonemegs for areas of maps, and sound megs for sound. soundmegs should be set to a max of 16, and maybe even 8, because over that could cause serious performance problems. zonemegs is fine at 32 and hunkmegs is fine at 160. anything over those numbers would just be redundant because the game wont use that much ram to it's advantage. q3 was designed for 64 meg systems. anything more is really unusable by the game.
Post edited by rashly at 3/26/2004 4:49:42 PM