-wadinclude Created 20 years ago2003-09-09 11:31:22 UTC by Vassy

Is it possible to -wadinclude more than one texture file? I'm gonna be working on a mod with Black Cat and will require many new textures.

sure, in the CSG parameters type
'-wadinclude vassyblackcat.wad' or whatever wad you have all of your textures in. I assume you now how to put lots of textures into one wad...

Well, no. I guess you just copy 'em and paste 'em into another wad file. But can I -wadinclude multiple wads, or must I use -nowadtextures? I read that it's a bad idea to use -nowadtextures though. Why?

I seem to remember that command adds ALL of EVERY WAD included - i.e. the massive halflife.wad which everyone has anyway

Summin like that, anyway.

Actually that has left me a little confused, as I thought
-nowadtextures added all the .wad files (all textures) that you have in the Texture tab of Hammer. But I am not so sure now... It might just add the textures used in the map you are building, but doesn't give you the path flexibility of -wadinclude. Might do some more reading on the subject unless anyone knows for sure?

Atoms Custom Textures tutorial covers this problem.

the -nowadtextures parameter is what i always use, that way its makes things alot easier when it comes to packaging your map, you dont have to worry about the .wad file, it puts all the textures that you have used into your map .bsp only, not the whole .wad.

Example: if you use 10 textures out of the halflife.wad, it will only include those 10 textures into the .bsp file, not the whole .wad.

MASTeRmiNd is right on the money.
I did some testing after the previous posts and it doesn't really matter what you use. Both -wadinclude xxxx and -nowadtextures only include those textures that you have used in your map.
However, -nowadtextures includes all .wad files like halflife.wad into your .bsp, where -wadinclude only includes those files you select.
The savings in .bsp size can be considerable. It all depends on who is getting the final map. do they have the .wad files that we consider generic? Some of the Mod specific .wads are not all that common. CS is a classic example of this. If you don't have the same CS maps as the guy distributing the map, then there is a good chance that you won't have the right .wad file.
An easy way around this is to use Wally to build a common.wad (all your favorites) and -wadinclude it. No need to add generic files like cstrike.wad or halflife.wad... and we know you can't add the decal.wad, but it will save the guy at the other end a whole heap of problems.