Running Hammer without firing up sourceSDK..

myth

Newbie
Joined
Apr 29, 2004
Messages
350
Reaction score
0
hai there,
i just started mapping recently. i just wanna know whether is it possoble to run hammer without firing up Source SDK....lot of time is wasted if i select hammer through SDK menu. thx in advance....
 
I don't think so, however it may be time consuming but it sets hammer up with the correct mod you are working on doing it this way.
 
Hmmm..... Possible I say.

You have a file called hammer.exe somewhere in your SDK files. In the bin folder i belive. Running that while steam is running will give you hammer without loading the SDK first. The backdraw is that your settings will be the same upon launch each time.

If you really dislike Steam then you will have to go back to the Hammer 3.4 (or was it 3.5?) but then you cant map for source.
 
Hmmm..... Possible I say.

You have a file called hammer.exe somewhere in your SDK files. In the bin folder i belive. Running that while steam is running will give you hammer without loading the SDK first. The backdraw is that your settings will be the same upon launch each time.

If you really dislike Steam then you will have to go back to the Hammer 3.4 (or was it 3.5?) but then you cant map for source.

i hve no issue with steam....but it takes time to fire up hammer through source sdk....especially if i compile maps very often..
 
?

So use aforesaid file instead.

And why fire hammer to compile? And what has several compiles got to do with it? Just leave the SDK open when you playtest and then re-launch hammer.
 
?

So use aforesaid file instead.

And why fire hammer to compile? And what has several compiles got to do with it? Just leave the SDK open when you playtest and then re-launch hammer.

hey mate...i found the solution.....here it is.:cheese:

Direct Shortcuts to Hammer Will Not Work (Since 8/4/2006)
With this version of the SDK you will get an error if you attempt to run hammer.exe from the 'sourcesdk\bin' directory. Here is the best way to work around this issue:

Right-click on the Source SDK item on the Tools tab in Steam.
Select Create desktop shortcut.
Add -runhammer to the end of the steam.exe command line.
For example: C:\Program Files\Valve\Steam\Steam.exe -applaunch 211 -runhammer
Rename the desktop shortcut to something appropriate, such as "Hammer Editor".
This has the added benefit of actually launching the SDK Launcher before Hammer, making sure it is the latest version.

Also, you can create shortcuts to Model Viewer and Face Poser by creating other shortcuts and adding these command line arguments:

-runmodelviewer

-runfaceposer
 
Nice. Yet that leaves you without the option of choosing a game.
 
How long does it take for the SDK to load? Are you really impatient enough to wait for that, yet patient enough for a compile? I don't understand.
 
everything related to source loads like old people sex - SDK, HL2 etc. and then once you're finally in hammer, and have your map open, it carries on loading wt****le for 10 minutes, and you get lag. valve really need to get their act together on this because it's a pain in the arse
 
5 seconds to open Source SDK...

10 seconds to open Hammer...

2 seconds to open map...

0.2 seconds to close Source SDK...

And let the mapping begin!
 
/dance

Seems to mee that VALVe dont care about loading times and instead spend their time on getting good looks ingame.

Thats cool with me.
 
5 seconds to open Source SDK...

10 seconds to open Hammer...

2 seconds to open map...

0.2 seconds to close Source SDK...

And let the mapping begin!

well dat takes 17.2 sec to open a map. just imagine if u r mapping. u need to compile every now and then to check whetherthe last made change is proportionate to the map. i my case i had to run my map 4 about say 40 times. so the totoal time lost is (17.2 * 40) /60 =11.47 minutes. i magine in the case of making professional maps......
 
Back
Top