razorace Posted July 29, 2005 Share Posted July 29, 2005 Hi Guys. Does anyone have an idea on how to deal with the MAX_CVARS problems that seem to crop up in Siege mode? I assume it's due to there being too many CVARS when you're playing in local mode, but is there anyway around this? Link to comment Share on other sites More sharing options...
ensiform Posted July 30, 2005 Share Posted July 30, 2005 i dunno how you can get around it, we just disabled siege cause of it. we may even strip siege code out too speed it up. although you could try: making siege use config strings instead of cvars. make the unusable by someone cvars not store with cvar_archive. Link to comment Share on other sites More sharing options...
CerberuS_21 Posted July 30, 2005 Share Posted July 30, 2005 The method Raven used for displaying forcepowers, weapons and items in Siege uses a lot of cvars unfortunately... As far as I remember, it uses 16+ (UI) cvars alone just for storing the forcepower icons and descriptions which are displayed on the Siege "Join Game" screen. Which is why the MAX_CVARS error usually pops up when you click on "Join Game" since those cvars I mentioned are being initialized at that point. Link to comment Share on other sites More sharing options...
razorace Posted July 30, 2005 Author Share Posted July 30, 2005 Hmmm, well it looks like it was related to the .cfgs I had in my directory while running it. Interesting note thou, I continued to have the problem even thou I deleted my jampconfig.cfg files of both my debugger dir and the game /base. The only way to fix the problem was to remove my other .cfgs that were in the directory. This means that the engine is somehow using the files even thou the shouldn't have been touched at all during normal operation. My current thought is that maybe the engine still looks at the linuxserver.cfg or maybe all .cfgs in the /base directory even thou they aren't actually used. Link to comment Share on other sites More sharing options...
stubert Posted July 30, 2005 Share Posted July 30, 2005 yea it would take alot of work to sidestep this but in reality, the thing is just crashing because the engine has this error hard coded in it... if the devs removed it there would probably be no problem at all Link to comment Share on other sites More sharing options...
razorace Posted July 30, 2005 Author Share Posted July 30, 2005 Well, that could be stated about any problem. Anyway, my point is that the problem can be caused by .cfgs other than your jampconfig.cfg file. Just a word to the wise. Link to comment Share on other sites More sharing options...
stubert Posted July 31, 2005 Share Posted July 31, 2005 i see no reason that the game can't have more than 1024 cvars in siege mode i think 1-2ghz machines can cope just fine Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.