Page 1 of 1

zonemegs latch?

Posted: Sat Apr 01, 2006 8:31 pm
by dzjepp
Is it possible to have a higher than default (16) setting of com_zonemegs? Any higher value stays latched, even after restart.

I'm trying to use

com_hunkmegs 192
com_zonemegs 64
com_soundmegs 32

Would this be considered the preferred optimal value or is there anything else that might be used? On big maps like the team arena maps I've had map loading failures before with 128 for hunkmegs.

:drool:

Posted: Sat Apr 01, 2006 9:00 pm
by Oeloe
It's not very clear what zonemegs are for and if it can improve performance in any way. It doesn't seem to be important.

Posted: Sat Apr 01, 2006 9:38 pm
by ^misantropia^
Due to the way the engine initializes, com_zonemegs does absolutely nothing. The zone memory is allocated before the q3config.cfg and command line cvars are parsed.