first one is model loading based, there was a way to delay loading model until next map.

second one: never expirienced it and were is the prob hitting tab once?

third is prolly files based of the server. or its compability.

1. i think that less pk3s on the client would reduce this lag a bit

could we do something like if you use enemymodel and cg_forcemodel 1 then dont allow to search & load the player model of the joined one ..? i dont know in what area of q3 sources this is implemented.

2. Maybe it's a feature? i like having "still" scores like that in the middle of the game when im frozen it happens if i press Tab multiple times .. i dont know exactly how .. i think its about the load times of scores apparence?

a. \+scores command launched (cause the tab key was pressed)
b. scores starts loading to show
c. \-scores command launched to hide the scores but scores are not on the screen YET(cause the tab key was unpressed) - the scores still not loaded to show.
d. now the scores ended loading and it appears on the screen .. (\-scores is not launched because the tab key unpress event is no more)

if these a-d are true then it could be related to hud elements or something that makes scores to load harder .. maybe the cg_drawteamoverlay is also on ?

this scores thing was in 2.0 too but maybe now is more seenable.

3. No idea (i pass)

_________
epsislow

hmm having pk3 load on need would increase drastically the time for load .. because pk3s are zip files so .. for example if an enemy player join the server and he use the HomerSimpsons model .. that let's say you have it in pk3, the pk3 load on need would add the time for "pk3 content read"/ "pk3 decompress" which q3 does when it loads in console ... i think that no one would want something like that happening in the game ..

and besides that loading happens in the main engine which is impossible to be changed unless the exe is changed so ... this is a clear "won't implement"

how is done now its everything is loaded in the beginning and added into a queue ... when something is needed like a model or something , it is searched there and its loaded if it is founded.. if you have many pk3s (many files in pk3) then this queue is big .... this is why if epsi for example uses pepsinator skin that no-one has .. the q3 will need to search all the entries in the queue ... before saying its not found .. = bigger lag.

thats why i said less pk3s = less lag.

And i was speaking only about clients .. For servers less pk3 = less time to onload / restart of server .. but not too much.

feel free to correct me if i'm wrong .

_________
epsislow

1. Even when model loading can cause lags, a reason for server-side packet loss on player connect can also be due to large bans.txt files on the server, since it needs to load, read and parse the file every time a player connects. It also should happen on name changes.

3. As skull pointed out, that is for compatibility with 2.0a, and has no effects anywhere else.