Yes it was my fault. I blocked the script to run in my browser

ah ye is ajax u need js...

_________________

We had 16 new players on Sunday. 13 on Saturday. 17 on Friday. 10 Thursday. 11 Wednesday. 26 on Tuesday. We're on a good way.

If the player base tends to build in this speed there might finally be a real bomb server populated in 4.2(Not a dust2 only server).

Today on nepal something was wrong with the map. The client loads the map and then the game crashes. (The short time i spent ingame the world looked too big.) Not only my client disconnected. I tried to reconnect with 3 different clients - no success. Nepal is now taken out of the mapcycle. I do not know what caused the problem.

EDIT: Connecting worked fine, but as soon as the map loaded framedrops came down to 10fps or so and not shortly after the game crashed. (Having a connection as low as a ping of 4 and frames easily at 95 usually.)

coolcool (:

_________________

So I found out what the problem was:
I deactivated dmaHD (seta dmaHD_enable "0"). But left seta s_khz "44" at those 44khz. This does not seem to work for me; had to reduce it when with dmaHD at 0 to s_khz "22". Weird huh? With dmaHD 1 it works with 44khz btw..