Hello
Was it really necessary to Set those settings ? (is there any interest to set those settings ??)
OR is the Server doing that automatically ?
Please, What kind of setting do you use ??
Should I use set or seta ?
Does those settings depend of the number of slots ?
Thanks
com_hunkMegs 64 is what i use.
OK, here is the scoop, on the Hunk, Zone, and Sound Megs.
192 hunk Megs is all ET will use, even if you set it higher.
The Zone and Sound Meg values are both subtracted out of the Hunk Megs, not added to it.
Not surpassing 3/4ths of total memory is easy to figure, 192 is the most memory that ET requires, or will use.
There fore, on a system with 256 Mb of Ram, 192 Hunk Megs, is 3/4ths of the 256.
Systems with more memory would still use 192 Hunk, so on to Sound and zone.
You can use the meminfo command to see the Hunk and Zone usage in the ET console, but Zone is latched, and will only show 24 is used.
If you change this setting in a config file, it will not get changed because the zone Megs are loaded before any config files are run.
To get around this, you can create a short cut, and then add a set command to load the Zone Megs, and Hunk, and Sound as well.
Default settings for Zone and Sound are 24 Megs each, and ET will run with these settings, but those settings were designed for the small RAM of early computers.
The Sound Megs default was set at 24 Mb, and it will work, because ET will remove and reload as needed, but it’s not the best for performance.
To check the sound Megs use the s_info command, and I have found that the best setting for ET Sound Megs, is to set it on about 48 sound Megs, if you use the 22 MHz setting.
We subtract 48 from 192, and that leaves 144 Mb.
Now the Zone is loading Map texture, etc, and please be aware that the higher the quality of graphic settings you use, the more Zone Megs, ET will require.
Also, large servers with 30 to 60 player slots, will also require, more of the left over Hunk, so you may have to play around with the Zone setting, to leave enough Hunk, and remember the Zone has worked, set at 24 Megs, its default setting, for years now.
Therefore, I would recommend 32 to 48 maybe even 64, but it depends on the above variables I mentioned.
So the get the Latched Zone to change, create a short cut, then right click on it, and select properties.
Then in the “Target” text box after ET.exe add this command and put quotation marks surrounding the number value settings, as follows:
"C:\Program Files\Wolfenstein - Enemy Territory\ET.exe +set com_hunkMegs “192” +set com_zoneMegs “32” +set com_soundMegs “48”
I f you find these settings are slower, then just change them, in the short cut, but a word of advice, only change one setting at a time.Hope this settles the Hunk, Zone, and Sound Meg issues for all you players out there, so enjoy.
Billdoe
Do not stress over it. Just set…
com_hunkMegs “192”
com_soundMegs “32”
com_zoneMegs “32”
I put this in my clan menus, so it takes effect when players connect. I also made a utility for my clan which patches Windows Vista/7 and it includes these hunkmegs settings.
http://www.supremeclan.com/t405-et-ready-utility
There was always debate years back on what to set, but it is safe to use these optimized values now because computers are higher-end. Anything higher than these values is a waste of time, but anything less than these values is also pointless. I have had several people test these values on all mods, and even older systems with 256MB, and it does the trick!
32MB for soundmegs is way too low. Check how much RAM the game uses for sounds with s_list command. I’d suggest to set your com_soundmegs to at least 128.
I have standard com_soundmegs 24 and never had any problems with the sounds on our server (or others) which btw. has a lot of sounds. The com_hunkmegs is 110 (server and client) and i see no reason to raise that but maybe it is mod dependent.
I raised it yesterday a few games without noticing performance issues. If you know your perfomance goes down then tell me where in the game do you notice that so i can keep an eye on that.
Well, if this value is default my FPS is not stable, with com_soundmegs @ 160 I got stable 125 FPS on almost every map.
It will not impact “performance”. It is not like how windows manages memory on PC. That is a big misconception.
It WILL impact disconnect errors. Either you have enough memory for the game tasks…or you don’t.
I’m just saying how it works for me. My FPS are below 100 with low values while higher ones provide better performance, that’s all, lol.
… it will impact performance because it avoids I/O operations. The value of com_soundmegs defines the ‘cache’ size for the sounds. As Dragonji mentioned call /s_list and you’ll see. My personal value is about 160MB for com_soundmegs (all sounds are cached).
For com_hunkmegs you’ll never need a value higher than 72MB - see /meminfo.
ok so i got a little bit confused right now lol 
I have that in my command line:
C:\ET\et.exe +set com_hunkmegs 512 +set com_zonemegs 192 +set com_soundmegs 192
is that ok???
This reminds me of the “vcache” and swapfile tweaks back in the windows 95 days. Yes, these are valid tweaks, but they hardly make a difference.
I have tried every combination of et megs for performance, and regardless of what the system reports, it makes little difference. However I have used these settings to fix disconnect problems with NQ and other mods.
But I wish you luck in your tweak archeology.
@ IRATA
I thought that the zone and sound meg values are minused from the hunkmegs? If so, wouldn’t 72 be kind of low??? That would create a negative value.
[QUOTE=cheesy;403835]@ IRATA
I thought that the zone and sound meg values are minused from the hunkmegs? If so, wouldn’t 72 be kind of low??? That would create a negative value.[/QUOTE]
No, you’re wrong. Soundmegs are separated from hunk.
[QUOTE=cheesy;403835]…
@ IRATA
I thought that the zone and sound meg values are minused from the hunkmegs? If so, wouldn’t 72 be kind of low??? That would create a negative value.[/QUOTE]
Definately not the case… at least not for the soundmegs.
As far as I know zonemegs aren’t really used in mulitplayer so I did correct the above value to default 24. Lower values are set to 24 anyway - see common.c (if (cv->integer < DEF_COMZONEMEGS))
You’ll notice these ‘tweaks’ on systems with low RAM. The system doesn’t have to swap memory when other apps are started.
ok, I was not 100% sure on the memory sharing, but I must admin out of all the settings and philosophy I have seen over the years
com_hunkmegs 72 +set com_zonemegs 24 +set com_soundmegs 160 seems the most “unique”.
You said “you’ll never need a value higher than 72MB”. What are you basing this on? I have heard this same statement made about values of 128, 192, and 196. I would love to know the logic behind this.
[QUOTE=cheesy;403881]
You said “you’ll never need a value higher than 72MB”. What are you basing this on? I have heard this same statement made about values of 128, 192, and 196. I would love to know the logic behind this.[/QUOTE]
/meminfo …
[QUOTE=cheesy;403881]…
You said “you’ll never need a value higher than 72MB”. What are you basing this on? I have heard this same statement made about values of 128, 192, and 196. I would love to know the logic behind this.[/QUOTE]
I’ve never seen any mod & map combination using more memory. /meminfo … 
… the logic behind 128MB is a power of 2 memory size but this isn’t really required.