Source SDK - NemPosted: Nov 5th, 2004 - 11:30:34 pm

For those of you who haven't noticed, the Source SDK has been released via Steam. I gave it a run through and was a little disappointed; nonetheless I realize it isn't the final SDK.

During my run though, I noticed that Hammer's compiling interface hasn't improved one bit. As a result I've uploaded some shinny new Source specifications. These specifications were generated by running each tool in verbose mode without any other options. I noticed that some of the options listed didn't work or were misspelled or otherwise lacked a decent description so don't expect these specifications to be perfect.

You can pick the new specifications up on the specifications page, or by running an automatic update from within Batch Compiler. The specification you are looking for is "Source Tools Normal". You can also expect a new Batch Compiler in these coming days with some overdue improvements.

Modified: Oct 1st, 2005 - 7:39:25 pm[ 13553 Views ]

1. kiLLuPosted: Nov 6th, 2004 - 3:33:38 pm

packagepackage

2. SlackillerPosted: Nov 6th, 2004 - 4:20:22 pm

nice apple

3. BluefangPosted: Nov 7th, 2004 - 10:05:29 am

I was going to write that I was going to update HL-Compiled with the new tools/specification, but they all require the Steam service, so that makes it pointless.

I'll just do a quick update to include configuration for the new compile tools in steam. I'll get that done by the end of the day.

4. NemPosted: Nov 7th, 2004 - 10:25:52 am

That is one thing I forgot to point out: Steam needs to be running to use the new specifications.

5. BluefangModified: Nov 11th, 2004 - 3:53:45 pm

Found a problem with your specification files.

the old spec files had a line thaty set the 'wadroot'

"set WADROOT=${InputPath}\n"_


if you are compileing a map for CSS and it is not in the games map folder, you need to set the VPROJECT path or you get an error. just add the following:

"set VPROJECT=${InputPath}\n"_

Updated Source Tools Normal.bcs


Also, when you run it from the batch compiler, the compile tools create a 'bin' folder in the directory is in.
but if you execute the .bat file manually, it will create a 'bin' folder in the directory of the .bat file.

also:
new version of HL-Compiled is up. it is the same link.

6. NemPosted: Nov 11th, 2004 - 5:13:06 pm

I'm currently debating what to do with the input variable. As you pointed out it can be used to set the VPROJECT environment variable (though this can also be set in the CSG tab under the game option). Also, as you have pointed out, the tools create a Bin directory (which is very annoying) but can be fixed by doing a cd to the bin directory. The input variable could also be used for this. Neither solution is very intuitive and I'm thinking I should have made configurable variables part of the specifications. Maybe its not too late for that...

7. BluefangPosted: Nov 12th, 2004 - 2:25:13 pm

well isn't the 'input path' technically suposed to be set to the MOD Dir path anyways?

The VPROJECT path is just the location of the GameInfo.txt, which happens to be the MOD dir.

By 'configurable variables' do you mean that the variabled set in the Setup would depend on the Specification? (kind of like the way the tool opetions work?)

of course the short-term hack could be just creating a ${BinPath} variable and adding another path setting in the path setup.

8. NemModified: Nov 12th, 2004 - 9:19:45 pm

In reality, InputPath and OutputPath were just made to satisfy the Half-Life requirements (in a generic way). What I should have done, and to a certain extent what I planned to have done, was make configurable variables that the users could set in the GUI with something like the following specification entry:

Code:

Variable
{
Name "VProject"
Type "Folder"
Hint "The path your GameInfo.txt file is located in."
}

Hindsight is always 20/20 isn't it? Oh well, maybe it isn't too late. The automatic update tool might require some fundamental changes too...

9. MastahKillahPosted: Nov 22nd, 2004 - 6:37:50 am

Oh my God....
I hate those tards.
I just keep encountering error after error....
They should other ppl handle hammer or something...waaa

10. BluefangPosted: Nov 22nd, 2004 - 12:09:42 pm

if it is compile errors, then that is your own problem.

if it is Hammer errors, then the probably cause is that this is a 'beta' pre-releae of the SDK

You must be logged in to post a comment.
New users can register here.
Nem's Tools v2.0 © 2006 Ryan Gregg.
Execution time: 0.023481s; Queries: 17.
dishes served.
Powered by The Wavelength.

Valid XHTML 1.0 Transitional Valid CSS
π