Pardon My N00bness
Coroner
Join Date: 2003-09-18 Member: 20994Members
Join Date: 2003-09-18 Member: 20994Members
<div class="IPBDescription">halflife.wad</div> I decided I want to update my maps Ive made for 2.0 to work with 3.0. Long story short I have no idea where the steam equivalent of the old /half-life/valve/halflife.wad is, or if it even exists. About 1/4 of my textures were from that wad, trying to find it.
Any help much appreciated.
Any help much appreciated.
Comments
Open them with <a href='http://countermap.counter-strike.net/Nemesis/index.php?p=25' target='_blank'>GcfScape</a>
If you included the path in your old zip file, you'll have to re-compress your package also, and change the
halflife\ns\
to
halflife\nsp\
I dont know if this is to change, since NSP is the folder they have used for the beta, and NS was the one they used for 2.x.
He can extract the WAD file to any place, mine are stored on my E drive, and my halflife runs off my F drive.
I usually <i>-wadinclude </i>my textures into my map to avoid small details and problems.
Steam automatically loads anything that's in the GCF files for end users -- Worldcraft 3.5 doesn't have Steam support, which is why mappers need the external tool for manual extraction.
A GCF file is like a more complex PAK file for steam that can be updated on the fly--it's a virutal directory system that allows file patches to be installed when the user decides to play an updated game. Because everybody's GCF files are supposed to be identical, Valve can update small portions of large files just by overwriting the correct offset in the GCF file; I guess they feel that's more efficient than updating individual files in a traditional folder tree.
Any file that was available for the WON version of Half-Life will still be available for use in Steam--Valve didn't break any backward compatability as far as file requirements are concerned. Just like PAK files can contain game information without it being present in the directory, GCF files contain everything needed to run a game.
He can extract the WAD file to any place, mine are stored on my E drive, and my halflife runs off my F drive.
I usually <i>-wadinclude </i>my textures into my map to avoid small details and problems. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
yeah but it makes more sense to put it here <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo-->
I don't know if you meant all of your textures, but using -wadinclude for textures appearing in standard files like halflife.wad or ns.wad that are garunteed to be part of the user's install just bloats your bsp size--it's redundant data.