safe_malloc - spitting it out too soon?

(WadeV1589) #1

I’ve got a large map and was getting the safe_malloc error in lighting. Using -lomem the light time is 6 hours which is insane.

My friend Scott modified Q3Map2 to work around the error and my lighting dropped to 1 hour; there were no problems with the map.

So my question is, can you take a look at this error because it seems to be able to compile just fine and in a fraction of the time if it is ignored, provided you have the memory.

I have 1GB ddr and set the swap file to at least 1.5GB btw and with that the safe_malloc error could be ignored after editing the source.

(phobos) #2

I seem to remember something about hard coded limits in the light compile stage, like it only uses a fixed amount of memory internally. I could be wrong. Try using some options like -fast -cheap and -fastbounce and use the latest Q3map2 version. Link’s in the sticky at the top of the forum.

(WadeV1589) #3

Like I said before, I’m using a modified version of Q3Map2. Just to work around that error a little. It’s 2.5.13 code. I’m hoping YDNAR will be able to shed some light on this.

(ydnar) #4

What changes did your friend make?