Q3Map2 parameters and safe_malloc allocation failed

[Atera]

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?

[Atera]

I just attempted the following:



BSP: -meta

VIS: -vis

LIGHT: -lowmem -light -super 2



Only to recieve this error during compilation:



WindingFromDrawSurf failed:
MAX_POINTS_ON_WINDING exceeded



Oh god, what's this now? :S

[Bacon]

I think brushes can only have 16 (?) max sides, any more and you get this error. You need to split up brushes into more pieces that have more than this many sides to it. This happened to me when I used the clipper tool and made a brush with a ton of sides to it.

I've also read it can be caused by fog or water brushes touching the void, or overly large fog brushes (lava too, usually has fogparms).

[^Ghost]

MAX_POINTS_ON_WINDING exceeded
making these brushes detail can fix it

[Bliccer]

Don't know what your error message means?
Take a look here: Common Error Messages v1.5

[obsidian]

If I want to make a final one, what additional parameters would you recommend me to use?

The ones you are using have been deprecated since forever. -super is slow and yields pretty poor results, samples replaces it. I've included a good default set of build options in GtkRadiant 1.6.4.

-meta
-vis
-light -fast -patchshadows -samples 3 -bounce 8 -gamma 2 -compensate 4

Tweak as needed for your map.

[KittenIgnition]

I've used -super and -samples, -samples had no visible effect, with any value between 2 and 64 (powers of 2 obviously). -super 2 had huge impacts, though obviously it also made the compile take a lot longer, and cost a lot more RAM.