I'm compiling my NS map, and attempting to -wadinclude c:/progra~1/valveh~/tools/hornpipe.wad - it appears to succeed when HLCSG finishes.  BUT when I open the map in NS, it tells me it can't find valvehornpipe.wad.  I was under the impression that wadinclude made it so it didn't require you to hand out the wad file with the map?

Also, should I be worried about this:

7 brushes (totalling 42 sides) discarded from clipping hulls

(I don't think I want the compile tools to get smart with me and start throwing away parts of my map, but maybe it knows best...)

EDIT: NS also has a custom hullfile, maybe that's what is causing the second problem?

7 brushes (totalling 42 sides) discarded from clipping hulls

(I don't think I want the compile tools to get smart with me and start throwing away parts of my map, but maybe it knows best...)

LMAO...thats so funny. well i dont know much about wadinclude. i use an custom auto-compiler, everything is done for me

but i would suggest re-checking your dir paths, i do know HL and or the compilers have troubles with spaces in dir names. example: if you got wad in C:/program files/blah/blah/blah/wad.wad its not going to work. (notice space between program and files)

i had this problem with my compiler, it couldnt find wadfiles, i just reinstalled everything on my other HD. worked fine with no dir with spaces in there names.

I figured it out.  I just dropped my WAD file straight onto c: and used some nice 8.3 DOS filenames.  Also, I restarted Hammer, and it seemed to run the map fine.  So all is well, I guess.

unless its an invalid solid, and somewhere inside the map... dont concern yourself overmuch...

the removal process, to my understanding is all externally located.. you would have to memorize the entire maps structure to notice which was missing..

plus, who's to say, its not a 1 unit by 1 unit piece

"Discarded" always has negative connotations whenever I do something related to mapping.  Also "Hammer".