Quake3World

been having a few problems with multiplayer and the game not cacheing certain gameplay elements. using the machine gun zoom as an example, first time pressing it in game results in a momentary freeze as it loads from the game files. rail zoom is smooth first time.

there are other items that i can't pinpoint causing the same thing. momentary freezes as the item or sound gets loaded. i noticed a display in the console last time i played.

" warning- loading non-cached item, etc etc.."

who knows the magic command to cache all this shit up when the game loads?

this happens regardless the settings. high or low.

1.5gigs
800xtpe
a64 2.45ghz.

all drives are defragged, config has been set up for my ram amount.

Good Tweak guid here from tweakguides.com.

http://www.tweakguides.com/Quake4_4.html

Go forward abit till you see the cache tweaks section.

which is on this page if you have trouble finding it.

http://www.tweakguides.com/Quake4_8.html

nope. not working. played around with low and high values for all the tweaks. still can't get rid of it.

hmm, anyone else getting at least the machine gun hitch when first switching to zoom?

i had the same type of hitching with bf2 untill i grabbed more ram then it was always smooth.

I get the same thing with the machine gun, but it only lasts a second if that, nothing too big, but still annoying.

AMD Athlon XP 2800+ @ 3200+ (2.2GHz)
1 gig Corsair ram
9800 pro overclocked

playing at 1024x768, settings all high, no shadows or AA.

50-65 fps most of the time.

EDIT: I read somewhere that the MSG zoom lag/freeze was caused by high quality special effects turned on. however I will leave mine on. the zoom on the machine gun is pretty much useless anyhow, same thing with the rail, even though it dosn't freeze with rail.

Zoom sucks.. ignore it

shadd_ wrote:been having a few problems with multiplayer and the game not cacheing certain gameplay elements. using the machine gun zoom as an example, first time pressing it in game results in a momentary freeze as it loads from the game files. rail zoom is smooth first time.

No single magic command, in fact some files can't be cached. Have a look at the following cvars and URLs.

image_preload
r_useCachedDynamicModels
image_useCache
image_cacheMegs
image_cacheMinK

http://ucguides.savagehelp.com/Quake4/FPSVisuals.htm
http://ucguides.savagehelp.com/Quake4/fullcvarlist.htm

Well how about a magic phrase..."ram drive"

You got a 64bit processor...why not make use of it...slap in 6gigs of ram, install WinXP64, then install Q4 on a ram drive of 4 gigs.

Course thats just throwing money at the problem...then again how else does one solve the problem.

Yea, I've got 2 gigs of ram, but I've seen a lot of messages for loading non-cached items; a lot of them are things that seem like they should be loaded at any MP game's start, like enemymodel animations.

MP is pretty limited in the things that are going to be rendered/played. As soon as you start a game, you know every model, sound, animation, skin, texture, etc. that is going to be used through that whole game. Why not allow the game to cache it? It's not like the SP game, where you're constantly coming up on new things that need to be loaded.

this has gotta be fixed up. it's not only the machine gun but other shit as well. the more i play the more i notice the game hitching due to loading non-cached elements.

its REALLY bugging me.

/me likes nologic's solution :icon28:

tbf i've hardly noticed the cache problem, seems my fps makes things like that unnoticable

so i assume that once loaded thats it for the duration of the what ?- map, evening ? - does it constantly load things in and out of memory, sounds a bit ropey tbh

kleeks wrote:/me likes nologic's solution :icon28:

tbf i've hardly noticed the cache problem, seems my fps makes things like that unnoticable

so i assume that once loaded thats it for the duration of the what ?- map, evening ? - does it constantly load things in and out of memory, sounds a bit ropey tbh

my fps are fine, doesn't matter if i put it at 640x480. yeah once loaded it's good. like if i play a busy game for 10 minutes go through the hitches once it's very smooth for the duration.

now that i think about it, it's kinda like doom3 timedemo. the first time through it hitches, the second time it's smooth.

there was a command that fixed it up though. can't remember it.