Upon new map, CI occurs!

(guitarman584) #1

Whenever I go into an Enemy Territory server, no matter which one it is, after the map completes and a new one is loading, I get a CI error! Every time, every sever this happens, and it’s getting really annoying. I can’t reconnect. I have to close the game entirely and restart the game. Am I the only one with this problem? If not, how can I fix it?

(Kendle) #2

What are your system specs? CPU / RAM / OS. Look in the file /etmain/profiles/yourname/etconfig.cfg and see what value you have set for com_hunkmegs.

(guitarman584) #3

My CPU is a Pentium 4, 2.4ghz, 800mhz fsb, 512 mb ddr ram, WIndows XP Pro. And the value for com_hunkmegs is “56”

(Eh?) #4

Try changing com_hunkmegs to at least 128; 256 would also work.

(Kendle) #5

Yep, up the value of com_hunkmegs, but no need to go above 192 (which would be the ideal value for you anyway with 512Mb RAM). You might want to check the other memory allocation settings as well. For 512Mb RAM I’d recommend:-

seta com_hunkmegs 192
seta com_zonemegs 64
seta com_soundmegs 64

Not entirely sure what the other 2 do, mind you, but that’s what I use and I load maps pretty quick (with a much slower CPU than yours).

Although I have to say I’m not entirely convinced this is the cause of your problem. Normally exceptionally slow map loading would lead to being kicked by PB, rather than CI’s.

(Loffy) #6

For 512Mb RAM I’d recommend:-
seta com_hunkmegs 192
seta com_zonemegs 64
seta com_soundmegs 64

Kendle, thanks.
Related to this, I want to clarify with you the following: Should I use seta in my autoexec.cfg (which loads at game-start) and set in my other cfg (the one that I execute after the game has started)? This is the old seta - set discussion, I know I should search for it/google - but I felt lazy.
I think it is seta in autoexec.cfg and set in the cfg that I execute manually. I wonder why they have made it this way? It’s like those accum/globalaccum script-commands, darn it - why not just accum (or set), and nothing else?
:banana:
// Loffy

(Kendle) #7

In ET set and seta are interchangeable (whereas they weren’t in RTCW), and indeed you don’t actually need either. All these are equivalent when used in any config:

set com_hunkmegs 192
seta com_hunkmegs 192
com_hunkmegs 192

I’m just RTCW “old-school” and so use seta out of force of habit. :wink: (and also I guess because that’s how they’ll appear in the etconfig.cfg config generated by ET itself).

(pgh) #8

RTCW old school? Here was me thinking it was based of Quake 3 which also had seta. :wink:

(Loffy) #9

Thanks kendle!
// L.

(Kendle) #10

RTCW old school? Here was me thinking it was based of Quake 3 which also had seta.
[/quote]
Probably, but I don’t go back that far. Sci-fi shoot-'em-ups / deathmatch never appealed to me.

(pgh) #11

Hehe… make me sound old even tho im what? 18. :slight_smile: - Only 4 yearsish now Quake 3s been out…

(Kendle) #12

I know, even though I’m old enough to be your Dad…(fuck me, that’s a scary thought, need to go lie down for a bit…
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
OK, recovered now…
.
.
I just never got into online gaming before RTCW as it was the first to really inspire me. The main attraction being the fact it’s Class based and isn’t all about aim / fastest net connection, etc. (neither of which I had at the time, and the former still eludes me).

(pgh) #13

Hehe… played Ra3 and CA on 56k for a year fs :slight_smile: and Q3F 56k for 2.

(guitarman584) #14

Well, your suggestion somewhat helped. I can go at least 1 map, 2 if i’m lucky, before it happens again.

(Domipheus) #15

i always thought if u did ‘seta bleh 1’ in the console, it would automatically set that Cvar in autoexec.cfg. if you did ‘set bleh 1’ it would set that cvar in the currently active .cfg, in q3 that qaas like baseq3.cfg or wotever, et it would be your profile.

(Kendle) #16

In RTCW seta would write the cvar to wolfconfig_mp.cfg, whereas set would simply set the variable for that session.

In ET the whole seta, set thing is broken. Whatever you set a cvar to it gets written to etconfig.cfg, whether you use set, seta or neither.

(Domipheus) #17

thats the way it should be tho, you set a cvar just by having /<cvar> <value> , set it SUPPOSED to save it.

(Domipheus) #18

actually, as you say doing niether still saves it. Which it should’nt, but using either seta or set should save it as I remember.

(Sauron|EFG) #19

Seta is also supposed to add the cvar to the config even if it’s not there already, but it doesn’t.

(Kendle) #20

Yep, should’ve qualified that. If the cvar exists in etconfig.cfg set, seta or neither changes it. If the cvar doesn’t exist already, none of them will add it, you’ll need to do it manually or put the cvar in autoexec.cfg so it’s set everytime you play.