Holy sh*t! I figured out -wadinclude!

[J-M v2.5.5]

Read topic title!!!
!!!!!!!!!!!!!!!!!!!!!

 

[Crow]

el oh el?

just tell me which one is the one that doesnt add the entire wad to the bsp, or w/e :roll:


__________________________
Artwork by Adam Phillips
http://www.biteycastle.com/html.shtml

 

[J-M v2.5.5]

There are two ways to embed textures (not wadfiles, but loose textures from wadfiles) in your map.

The old method (which Thothie prefers for reasons unknown to me) is

-nowadtextures

This method embeds every single texture your map uses in your map. That's right, even textures such as "SKY", or "CLIP", or "{BLUE" which everybody has (in halflife.wad). This method makes your map quite big if you use alot of different textures.

-nowadtextures Include all used textures into bsp.

This option is obsoleted by -wadinclude and is only left in to retain some backwards compatibility.

The new method (which I finally got working) is

-wadinclude "wadfilename.wad"

This method embeds every single texture your map uses from the wadfile(s) you specify in your map. In comprehendable (if this a word?) English: if you do a -wadinclude on "Crow.wad", the textures you used, and only the textures you used, from Crow.wad will be embedded in your map. You won't be embedding textures everybody has (such as "CLIP" etc. etc.) which causes your map to stay smaller in filesize. If you want to do a -wadinclude on multiple WAD files, you have to add the parameter multiple times.

-wadinclude file Place textures used from wad specified into bsp.

This option will cause csg to include used textures from the named wadfile into the bsp. It does partial name matching, is not case sensitive, and can also match directory names. If multiple includes need to be done, -wadinclude must be specified multiple times, once for each include. Only textures actually used in the map are included into the bsp.

Here's a (working) batch example for -wadinclude which I used for a test compile of Wicard Oven:

cd "C:\Hammer\zhlt"
set WADROOT=C:\Hammer\wad
hlcsg -high -wadautodetect -wadinclude "ts_neobaroque_miptex.wad" "C:\Hammer\zhlt\ms_wicardoven_etest.map"
hlbsp -high "C:\Hammer\zhlt\ms_wicardoven_etest.map"
hlvis -high -full "C:\Hammer\zhlt\ms_wicardoven_etest.map"
hlrad -high -extra "C:\Hammer\zhlt\ms_wicardoven_etest.map"
copy ms_wicardoven_etest.bsp "C:\Games\Steam\SteamApps\[email protected]\half-life\msc\maps"
del ms_wicardoven_etest.lin
del ms_wicardoven_etest.p0
del ms_wicardoven_etest.p1
del ms_wicardoven_etest.p2
del ms_wicardoven_etest.p3
del ms_wicardoven_etest.prt
del ms_wicardoven_etest.wic
pause

Be sure to set your wadroot (the folder where you store all your wadfiles). If you don't have one folder where you store all your wadfiles, I suggest you make one.

And if you need to include multiple WAD files, the HLCSG parameters will look like this:

hlcsg -wadinclude "wadfilename1.wad" -wadinclude "wadfilename2.wad" "mapname.map in correct dir"

 

[Thothie]

It wasn't a matter of not knowing how it is used...

It has issues of it's own. It sometimes gets all sorts of weird hammer errors, in very much the same way you get when you have too many wads. (Very odd unpredictable errors, z_mollacs / ex_extents post compile with no visible cause, full bright with no error report, compile crashes) ...Something is simply 'off' with its memory allocation, or it mis-predicts the amount of memory needed to space out room for the textures it's ommiting.

There are VERY few universal textures and they are all very small, so you usually don't save more than 5-10k anyways.

Hence, I still say, -nowadtextures FTW.

 

[Crow]

what if you've combined every single wad into one?




__________________________
Artwork by Adam Phillips
http://www.biteycastle.com/html.shtml

 

[PBarnum]

yea... i still like -nowadtextures

old pals kind of thing