Q3Map2 parameters and safe_malloc allocation failed
Posted: Fri May 09, 2014 10:05 pm
So I realize compilation is divided into three stages:
bsp, vis and light
If I want to make a final one, what additional parameters would you recommend me to use?
Currently I am using GTK1.5 and I keep running into safe_malloc failed on allocation of 155713536 bytes during the light stage.
So I have downloaded Q3MapGUI and here I am basically going to add -lowmem to the light stage in order to hopefully make it work.
My OS runs Win 7 at 64 bit with 8 GB ram so i'm not quite sure why that isnt enough, maybe the lights are just too complex in my map.
But what other functions should I use? For a final run, would this suffice?
BSP: -meta
VIS: -vis
LIGHT: -lowmem -light -super 2
Should I use anything else?
There is a quick list of Final (long time compile) that has:
BSP: -meta -v
VIS: -vis -saveprt -v
LIGHT: -light -patchshadows -v -bounce 2 -samples 2 -super 2
What exactly makes this one so much longer? The patch shadows? Should I go for it instead and ofcourse add -lowmem to the LIGHT stage for a final compile?
Also is there any additional tips that could perhaps prevent me from using -lowmem alltogether seeming as it makes the compilation slower?
bsp, vis and light
If I want to make a final one, what additional parameters would you recommend me to use?
Currently I am using GTK1.5 and I keep running into safe_malloc failed on allocation of 155713536 bytes during the light stage.
So I have downloaded Q3MapGUI and here I am basically going to add -lowmem to the light stage in order to hopefully make it work.
My OS runs Win 7 at 64 bit with 8 GB ram so i'm not quite sure why that isnt enough, maybe the lights are just too complex in my map.
But what other functions should I use? For a final run, would this suffice?
BSP: -meta
VIS: -vis
LIGHT: -lowmem -light -super 2
Should I use anything else?
There is a quick list of Final (long time compile) that has:
BSP: -meta -v
VIS: -vis -saveprt -v
LIGHT: -light -patchshadows -v -bounce 2 -samples 2 -super 2
What exactly makes this one so much longer? The patch shadows? Should I go for it instead and ofcourse add -lowmem to the LIGHT stage for a final compile?
Also is there any additional tips that could perhaps prevent me from using -lowmem alltogether seeming as it makes the compilation slower?