Posted by $loth on Wed Jul 28th 2004 at 1:20pm

Where would you put the wads? In the SteamAppsadamnaser@comcast.nethalf-lifevalve folder?

Posted by Crono on Wed Feb 25th 2004 at 5:03am

Thanks Omega, Something to remember when using model viewing in Hammer with Steam is that, you must be able to actually select the models, which means you have to extract them (meaning there's technically two copies on your Hard drive) so that Hammer can use them.

Also, as you'll probably find, once you start importing models, you have to create a res file for the map. Seems like a lot of work, huh? But I think it's becoming a very stable and reliable system such that more games then just half-life can rely on.

Posted by Crono on Fri Jan 16th 2004 at 8:04pm

Yeah . . . . like I said I can't edit the tutorial, If I could I would. And that last comment was to clear up a lot of confusion people might have about how it actually works. Sorry about the length.

Honestly, I feel like a morron for posting the tutorial and then an hour later finding a completly different way, practically on accident!! Which happens to be easier and more diverse.

[EDIT]
I wasn't explaining the tutorial in that post, I found other ways to make this work better, but it's being annoying. Such as, Hammer insists on putting compiled maps in the /SteamApps/ directory, which is not in any of the settings. It's doing some pretty random things suddenly. But for the most part, doing it the way I suggested in the tutorial will work just fine. I'm trying to figureout the reason why it's being so odd. If anyone wants to help out, by all means do so. If you can tell me why Hammer insists on everything being in the /SteamApps/ Directory whence compiling finishes (literally, before the copy commands) then you get extra brownie points . . .[/EDIT]

Posted by Crono on Fri Jan 16th 2004 at 12:56pm

All that is needed to compile a map into a bsp is the .map file.
And yeah Sinner, you're right, but that's exactly what this is doing.

If you're using a 3rd party compiler console then why would you configure hammer at all? Past the FGD file and the Wad files needed for the actual map editing. Unless you want hammer to call the 3rd party compile dialog . . . which it can probably do.

All that's going on when you compile with hammer is a series of calls to certain programs (or compilers) in whatever order you want.

Ok, let me see if I can briefly explain what I was talking about in the previous comment.

When compiling in Hammer, in the Advanced compiler Dialog you list the commands.

I took out the Change Directory command, because it will default at the rmfs path directory (e.g. if your rmf is saved on your desktop, your desktops path in hammer is the same as saying $path) thus allowing you to have the rmf anywhere instead of in the $gamedir directory.

Now, as you said, once the map is compiled into a bsp, all you need is the bsp in the maps directory. ($bspdir) which is the part where you put your map directory "place compiled maps here before running".

The steam.exe is ran by the parameter $game_exe

These are all set up seperatly and they are all in the Build Programs tab, these are the only things needed for building the map (thus the name of the tab).

obviously the last parameter left is $file which is just the name of your rmf.

Lets assume you have an RMF file in 'C:/MAPS' called 'fubar'

When it says:

$csg_exe $path$file

It means:

Run "/ZHLT/hlcsg.exe" with "C:/MAPS/fubar'

The compilers need a .MAP file (that type of encription). What it most likely does is looks for fubar.MAP since it knows there should already be a .MAP file there, made by you or Hammer or whatever, it will add the .Map portion in on it's own, if it's not then it whines at you.

Everything else continues in the same way. So, if it never calls the mod directory (and for steam is doesn't, not as long as your map folder path and such is inputed properly) then it will never be a problem because it is simply not needed.

Now, I'm not saying these things aren't needed for compiling WON maps. Because I really don't know, I've never messed around with removing and adding compiling options there.

But this works well, and it is actually less work, I apologize that I didn't spend as much time before I wrote the tutorial as I did afterwords, I was just excited that it ran with steam lol.

But this will work well. And if you're using a 3rd party compiling console, why are you messing with it at all? Just open your rmf over there and let it be compiled.

This tutorial is basically just to have everything compile properly and run automatically with steam, just as it did when mapping with WON from within Hammer.

on a side note, matt, to be honest it's easier. But if it makes you feel better, HL2, I'm assuming, will ship with a brang-new Hammer which is 100% tailor made for steam, as was hammer 2.0-3.5 tailor made for WON (Which is why some stuff isn't needed for a steam compile). I assure you everything will work out well.

If you haven't noticed, the recent updates of steam have cut the system recource cost. Now, your internet browser takes up about 6 times as much recources as steam (both being Idle). While Steam is running Half-Life your Browser still takes up twice as much system recources, while the browser is idle and steam is not.

Anyway, I suppose Steam has no where to go, but up.

Posted by matt on Fri Jan 16th 2004 at 10:35am

Now I'll never map for steam. Ever.