In Q3 maps, using the caulk texture on all unseen surfaces will shorten compile times drastically. I know that using null will help r_speeds, but will it also shorten compile times? Thanks.

Probably, it doesn't have to do lighting and **** on the null faces, does it?

it doesn't have to do anything to the null faces, it just disgards them near the beginning of the compile; so it seems logical that it would decrease compile time as well

yes, a little faster if you use NULL right.

no, if you use NULL wrong.

btw, Cagey at NS mapping forum is working on a beta for new compile tools. been reports of 30% faster RAD, more planes, less clipnode errors......and bugs. it is a beta - do you feel brave?

the link (http://www.natural-selection.org/forums/index.php?act=ST&f=4&t=21248&)

I'll give it a shot :)

A good practice is when you make your brushes to create them with the NULL texture then edit them into the shape you want then add the texture individually for each face this is much eaier and faster then adding the null texture after creatying a brush

If If you are i nthe texture properties editor and you RIGHT click on a brush face it will add apply whatever texture u have selected to that face and with what ever alightment/rotation ect the face you got that texture from

Yeah, thats exactly how you use Caulk Textures in Q3. Shouldnt be too hard to apply null in the same manner for DoD. :)

Originally posted by tommy14
yes, a little faster if you use NULL right.

no, if you use NULL wrong.

btw, Cagey at NS mapping forum is working on a beta for new compile tools. been reports of 30% faster RAD, more planes, less clipnode errors......and bugs. it is a beta - do you feel brave?

the link (http://www.natural-selection.org/forums/index.php?act=ST&f=4&t=21248&)

Less clipnode errors, does this mean brushbased rubble without sticky points? We can only hope ;)