Hunk_AllocateTempMemory?

(hummer) #1

One of my testers got the following message as my map was loading:

Hunk_AllocateTempMemory
failed on 786488

Anyone know what causes this / how to fix it? I haven’t been able to recreate this myself…

(Drakir) #2

Probably because u have a rather big pk3 file and the tester have the default com_hunkmegs set wich is only 56mb, tell him to set it to a higher value like 128 or so, but that depends on how much mem he´s got installed…if he only has 128 then hes got a problem.

(hummer) #3

Looks like it’s related to BSP size.

I shrunk the pk3 down to 14 megs from 23 megs. Same thing.

The BSP is 22-23 megs, which isn’t far off from ET’s which are like 15-16 max I think. Arghh…

Time to find ways to bring the BSP size down.

(TombardieR) #4

i’m not sure, but it might be to do with the value in hunkusage.dat, which is a plain text file with the hunkusage of each map. If ur map has had several revisions then there will be an entry in hunkuiage.dat that doesn’t really correspond to the map ur currently on, especially as it’s probably bigger than when u first tested it. just remove the line with this map, and then you’ll find that u don’t get a loading bar next time you load because it doesn’t know how much memory it needs,this is when it measures the hunkusage, and you should find it’s rewritten hunkusage.dat with a non bogus value
it should be in etmain with all ur map pk3z