Hammer Lag After CS:S Compile Created 17 years ago2007-02-27 23:47:38 UTC by RotatorSplint

I've decided to attempt my first CS:S map, and I was compiling to test a small entity setup I had made, but after it was compiled (I have the game set to auto-run after compile), CS:S loads, but the map loads and returns me to the menu screen. I can load the map via the Create Server option or the console.

However, the problem arises when I exit CS:S and highlight Hammer. The computer lags like both processors are loaded to their capacity. Even Windows Media Player lags. The only way to stop it is to highlight an other window, and use the Task Manager to manually exit Hammer. This only happens with CS:S.

Any ideas?

Both processors? You have two processors?

Dual core, I meant. Sorry for the confusion... srry (TEE HEE )

I'm still having this problem even when I disable $game_exe. After running the map in CS:S, The entire computer is bogged down. I looked in the task manager, and Hammer.exe is taking up every last bit of my RAM, even though I'm not doing anything in it.

Has anyone else had this problem?

I'm used to my computer being sluggish for a while after exiting any Source games. I usually close Hammer before checking the map ingame, since it'll give me a more accurate vision of what the performance will be like.

"Sluggish" as in the mouse even lags when Hammer is highlighted? :

Oh well. Opening Hammer isn't much of a problem.

Sluggish as in it takes more than 5 seconds for a mouse click to have effect on anything, and almost a minute until the Hammer 3D window is visible again.

What drivers are you using for your graphics card? The old ATI catylist drivers did somehting like that to me but then the newer ones dont.

The "Run map after compile" never worked properly for me, and i don't find it too much of a burden to just create my own server to play on. Even console "map mapname" will do fine for me. I say try compiling without the run after compile checked.

Why bother trying to run a Source game with hammer 4 open? Both are immense resource hogs.

Close Hammer and test your map through the console.

1. Don't run Hammer and Source at the same time, you're just asking for doom.

2. Windows Media Player is a worthless resource hog as well.

The Hunter is correct. I always shut down Hammer after a compile is done before I manually load CS:S to test the map. Frees up resources and doesn't cause me any problems.

I always close Hammer and compile through the batch compiler. Saving resources, saving lives.

i can run source and hammer 4 at the same time np. even with wmp open. i still get like 120 fps =]

i can run source and hammer 4 at the same time np. even with wmp open. i still get like 120 fps =]

That's easy if you don't say how much detail there is in the map in Hammer (and what Hammer settings you are using, like clip distance), how big is the playlist in wmp and how many effects are enabled in the Source game and what map you're running. I doubt you'd get 120 fps in cs_fallingliquid

Kasperg, what batch compiler do you use?

Batch Compiler 3.1.1, Nem's tools.
But I only use it occassionally. I do 90% of my compiles in Hammer, close Hammer and then run the game.