According to the ETTV entry on WolfWiki, there are no known solutions to the MAX_GAMESTATE_CHARS problem -- is that the consensus within the ETPro team? I'm asking because I don't know who wrote that article in the WolfWiki, or if perhaps some are currently working on a solution.
For those who don't know, the problem occurs when watching ETTV demos locally, where the demo continues, but the viewer (you) is kicked out as specatator.
The MAX_GAMESTATE_CHARS problem
Moderators: Forum moderators, developers
Re: The MAX_GAMESTATE_CHARS problem
If you can link on of the offending demos, that might help.Smoke wrote:According to the ETTV entry on WolfWiki, there are no known solutions to the MAX_GAMESTATE_CHARS problem -- is that the consensus within the ETPro team? I'm asking because I don't know who wrote that article in the WolfWiki, or if perhaps some are currently working on a solution.
For those who don't know, the problem occurs when watching ETTV demos locally, where the demo continues, but the viewer (you) is kicked out as specatator.
There shouldn't be any difference from "watching ETTV demos locally". The only way you can watch an ETTV demo is by running an ETTV server.
There may be things in your particular server configuration that make the gamestate bigger. I'd suggest keeping the number of .pk3 files on the server at the minimum possible, and not using a lot of sets, long motds etc in the server config.
send lawyers, guns and money
Whenever you are running a server (which includes ETTV demo playback) you should try to use a clean copy of ET with only the stuff you actually need.Smoke wrote:Hehe. Well, it was various junk that have accumulated over time -- maps, watermarks, campaigns, etpro updates, etc.arni wrote:rofl @ 51 unused pk3's thats 3 times as many as i have total
The same applies to normal demo playback for that matter.
The wiki is updated.
send lawyers, guns and money