banimod / etpro / ettv forums

But how come I only get these errors to etpro3.0.0/3.0.1 and not etpro 2.0.7 or shrub?

I also get kicked for configstring>MAX_CONFIGURATIONS quite a bit if any of these errors are related?

I also got kicked for cl.snap.servertime<cl.oldFrameServerTime once when the same thing happens that normally kicks me for client communication failure.

I did connect there and well I can tell i'll have that problem there when the server is populated but when its just me I start as a 999 ping and go down.

Yup I could reproduce that error 100% of the time as well like meez says on goldrush battery or oasis.

someone said punkbuster needs to be updated to solve this but a fresh reinstall didn't help. does anyone know the answer to this?
Btw, rate snaps and cl_maxpackter aren't the problem (25000.20.30)

why do networks settings that work perfectly with shrub or normal ET and etpro2.0.7 fail to work with ETPro 3

I never had a problem with hotmail until msn bought them and then literally the day of I got over 100 spam mails and continued to get that many even after turning on all the blocks including only send mail to me if you are a contact. Hotmail would make hte person a temporary contact just so they cou...

sadly that doesn't solve my problem and I can't play matches until I find hte solution to this.

On etpro 3.0.0/3.0.1 servers I get instant 999 ping that goes down on some servers if i'm the only one there but otherwise I get kicked for 'client communication failure.' What does this mean and how do I fix it?

Yeah I always get 125 fps (my cap) anywhere on any map at anytime on any version of shrub or etpro prior to etpro 3.x.x now I get max 70 but down as low as 20 which makes no sense to me.

another problem is the tank breaking on goldrush if you damage it at that certain spot at the start of spawn and then it can't be repaired and hte map has to be restarted.

I have this issue too but it always kicks me for 'client communication failure' and my ping only comes down slowly on some servers but on most stay 999 til i'm kicked for 'client communication failure.'