![Smile :)](./images/smilies/icon_smile.gif)
Known ETPro 3.0.0 bugs
Moderators: Forum moderators, developers
I am also having the same problem with MASSIVE kicks:
Just 5 minutes ago on my clan server (64.237.43.201) it 'disconnected' the entire allied team...
All the people who were disconnected report the same thing: they get an error 'etpro error - check console'. However, they report there is nothing useful in console![Sad :(](./images/smilies/icon_sad.gif)
Any thoughts on what might be causing this?
I read about disabling lvl 4 field ops... but I would like to keep them on.
Just 5 minutes ago on my clan server (64.237.43.201) it 'disconnected' the entire allied team...
All the people who were disconnected report the same thing: they get an error 'etpro error - check console'. However, they report there is nothing useful in console
![Sad :(](./images/smilies/icon_sad.gif)
Any thoughts on what might be causing this?
I read about disabling lvl 4 field ops... but I would like to keep them on.
Well unless he tells you how all I did was take my Demo's,Screen Shots and CFG file out of the ET Pro dir and then take out the ETPRO dir and reconnected to a 2.7 server and redownloaded ETPRO and I was good to go.totc wrote:Bani is there any way i can get a fix for the demo crashes?? My team is in the middle of Playoffs and i can't even watch demos for strats :/
Pls let me know..
I'm happy because i have waited enough and not upgraded my server to 3.0, i've read about lots of bugs in forums and i think it's better to stay with 2.0.7 for a whiledefragga wrote:disabling lvl4 fops is just a work around, until 3.0.1 will be released ... so if want that this error doesnt occur anymore u should disable them
but I think, there will be a 3.0.1 release pretty soon
hm, well since 3.0.0 is out we JUST play our clanwars / trains on 3.0.0 servers, without any problems. just with some small work arounds ...
even demo play works, ...
if u want to watch a demo, just connect on bani's server where the new et pro is uploaded, then u can disconnect, and watch a demo (but allways load the et pro mod when playing a demo)
if u did right, u see "et pro (compat)" in the lower left corner, where the server info's is placed :>
even demo play works, ...
if u want to watch a demo, just connect on bani's server where the new et pro is uploaded, then u can disconnect, and watch a demo (but allways load the et pro mod when playing a demo)
if u did right, u see "et pro (compat)" in the lower left corner, where the server info's is placed :>
thx for the info!defragga wrote:hm, well since 3.0.0 is out we JUST play our
even demo play works, ...
if u want to watch a demo, just connect on bani's server where the new et pro is uploaded, then u can disconnect, and watch a demo (but allways load the et pro mod when playing a demo)
if u did right, u see "et pro (compat)" in the lower left corner, where the server info's is placed :>
![Very Happy :D](./images/smilies/icon_biggrin.gif)
all valuable material for my frag video is in etpro3 demos ^.^
Re: Known ETPro 3.0.0 bugs
i got the same problem...very laggy gaming with ping 48 and lagometer not showing any lags!epospro wrote:I can confirm these sympoms in linux:
lag issues with high ping players (my ping is about 30-50)
weaponswitch / reload issues
On non etpro-3.0.0 servers this problem is not appeared. I have 512/128Mb link.
For me 3.0.0 is unplayable.
![Sad :(](./images/smilies/icon_sad.gif)
Hi!
When I'm starting my own sever with etpro on localhost only for me I'm getting this error :
BG_INDEXFORSTRING: unknown token NOT: (animations/scripts/human_base.script, line 3351)
and of course server is not starting.
I have this problem since i get etpro 3.0.0 bugfix 14 and 15 too.
In my folder with etpro i have older versions 2.0.0 and 3.0.0.
I don't know what is going on...
When I'm starting my own sever with etpro on localhost only for me I'm getting this error :
BG_INDEXFORSTRING: unknown token NOT: (animations/scripts/human_base.script, line 3351)
and of course server is not starting.
I have this problem since i get etpro 3.0.0 bugfix 14 and 15 too.
In my folder with etpro i have older versions 2.0.0 and 3.0.0.
I don't know what is going on...
- Lekdevil.NL
- Posts: 89
- Joined: Fri Sep 12, 2003 8:59 am
In 3.0.0 bugfix 15 it's possible to set conflicting sv_cvar values for one cvar, resulting in the client entering an endless error reporting loop. For example:
On the server:
sv_cvarempty
sv_cvar cg_announcer eq 1
sv_cvar cg_announcer eq 0
map_restart
Resulting output on client:
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup5.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup6.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup7.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup8.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup9.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup10.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup11.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup12.cfg
...
etcetera.
Note that I don't like the whole idea of servers changing the client side config one bit, but that's a different story. I guess it's time to write-protect my ETpro config file to protect myself from overzealous server admins...
On the server:
sv_cvarempty
sv_cvar cg_announcer eq 1
sv_cvar cg_announcer eq 0
map_restart
Resulting output on client:
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup5.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup6.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup7.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup8.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup9.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup10.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup11.cfg
etpro: cg_announcer CVAR_EQ violation - [0] should be EQ [1]
etpro: cg_announcer CVAR_EQ violation - [1] should be EQ [0]
etpro: Saved old cvars to cvar_backup12.cfg
...
etcetera.
Note that I don't like the whole idea of servers changing the client side config one bit, but that's a different story. I guess it's time to write-protect my ETpro config file to protect myself from overzealous server admins...
gonna be at quakecon again this year lekdevil? :p
(if there's an et tourney this year, no lms w/ hw as tiebreaker :)
being that public.config's are already being made by server admins.. i think a "recommended" public config should be released with 3.0.1.
of course the overzealous server admins would probably modify the config, but a majority of server admins would probably use it without modifying anything being that it is "official" (bani-approved :). then there's the argument that bani would be "forcing" changes upon the community through the use of a config and blah blah blah..
anywho, i think it'd be a good idea.
(if there's an et tourney this year, no lms w/ hw as tiebreaker :)
being that public.config's are already being made by server admins.. i think a "recommended" public config should be released with 3.0.1.
of course the overzealous server admins would probably modify the config, but a majority of server admins would probably use it without modifying anything being that it is "official" (bani-approved :). then there's the argument that bani would be "forcing" changes upon the community through the use of a config and blah blah blah..
anywho, i think it'd be a good idea.