Hammer Crashes after update...

DaMaN

Newbie
Joined
Jan 19, 2005
Messages
405
Reaction score
0
Yea, Valve sucks.

Upon release of the new 64-bit-tech update, whenever i (and others) try to load up hammer, it has a fatal error fit and closes.

Here's the lovely error message you will see when trying to load up hammer:
Hammer_extra_ip.jpg


It really pisses me off that valve releases a patch without testing it completely.

It also pisses me off because i was one compile away from releasing the map i've been working on for the last few months.

-DaMaN
 
I have the same problem anyway around this while valve fixes this bug?
 
Wow, you people still have this problem? :|

Just load Source SDK and choose Refresh SDK Content.

If that fails, open sourcesdk.gfc and extract the .gfc bin folder to your sourcesdk's bin file.
 
I'd better wait for Valve to fix this officially.

Yes, I know. I won't be making maps until February...
 
Just got an update that fixed it.

Seems the beta isn't beta anymore.
 
PsychoFreak said:
Wow, you people still have this problem? :|

Just load Source SDK and choose Refresh SDK Content.

If that fails, open sourcesdk.gfc and extract the .gfc bin folder to your sourcesdk's bin file.

nope, doesn't work.

Seems valve have made the same mistake again with this new 64-bit architecture.
 
Hmmm. I've found out a workaround.

Go to the mod folder for which you're making a map, and edit the GameInfo.txt. Change the ToolAppId to AppId. This causes another, but a passable error. Not sure if it affects the compilation or anything else, but it's bound to work. Worked for me and a lot of others. Any questions, start up Source SDK and go to Online Discussion. Mapping section.
 
Oh, odd. I put in the -beta sdk line and after 3-4 steam restarts later it finally picks up on it.

Anyway, it works for me with no troubles.
 
i thought this was old...but right now it is saying updating steam platform....at least im prepared to get rather pissed.

Edit: OH NO! Source SDK is updating....

Edit2: CHRIST ALMIGHTY!!!!
 
Have you guys ran HL2 before opening up Hammer? Obviously you would have to run HL2 after you installed the 64x component. It as solved some problems with me in the past
 
no this is a different problem. i am very unwilling to use beta sdk...but could ol valve leaves me no choice. im gonna be mighty pissed off if i end up screwing my map up completely because of it.
 
DEATH eVADER said:
Have you guys ran HL2 before opening up Hammer? Obviously you would have to run HL2 after you installed the 64x component. It as solved some problems with me in the past
Har har.
 
Limpet said:
Just got an update that fixed it.

Seems the beta isn't beta anymore.

so why does trying to navigate the 2D windows with the arrow keys now make the window contents vanish? using the scrollbar is a frankly same-sex oriented way of doing things

it's funny, but the first time i started with hammer i thought how crap it was only model bounding boxes drew in the 2D windows and not the wireframe (radiant, for instance, draws the wireframe). now i've tried the sdk beta where they finally implemented that and it just looks cluttered. lol
 
incidentally, i found running hl2 before hammer to fix probs didn't work. what DID work was running hammer from the .exe in the sdk folder rather than via steam (which is what i usually do anyway)
 
UltraProAnti said:
so why does trying to navigate the 2D windows with the arrow keys now make the window contents vanish? using the scrollbar is a frankly same-sex oriented way of doing things

it's funny, but the first time i started with hammer i thought how crap it was only model bounding boxes drew in the 2D windows and not the wireframe (radiant, for instance, draws the wireframe). now i've tried the sdk beta where they finally implemented that and it just looks cluttered. lol

Odd, works for me. But now info_player_terrorist/counterterrorist are errors as I'm sure others are too.

I guess I spoke too soon. Hammer suddenly worked after downloading 2 updates and I assumed that valve had made a fix.

Stupid me :frown:
 
changing toolsappid to appid makes hammer run....but its hardly useful when all your textures turn black in camera view.

i had a free day today and i was planning on mapping and making a bunch of progress....

this really sucks.
 
UGH! Well, there was another update, which now forces people to accept the beta sdk. It also refuses to draw vertical gridlines.

Damnit valve...

The only good thing about the new hammer: auto-saves.

-DaMaN
 
WAR_Nuker said:
changing toolsappid to appid makes hammer run....but its hardly useful when all your textures turn black in camera view.

i had a free day today and i was planning on mapping and making a bunch of progress....

this really sucks.
I hear ya. So much my ear drums hurt.
 
might have to go BACK to the beta... after it was too buggy to work productively on.
 
DaMaN said:
UGH! Well, there was another update, which now forces people to accept the beta sdk. It also refuses to draw vertical gridlines.

Damnit valve...

The only good thing about the new hammer: auto-saves.

-DaMaN

My vertical gridlines are fine =/
 
ok, it turns out using the arrow keys to navigate in the 2D window works fine if:

1. you have scrollbar turned on as well :retard:
2. you click inside the 2D window you want to navigate first

the lack of context-dependent cursor changes is slightly annoying though
 
so we all have no choice but to use -beta sdk as of now....so i did a bunch of work last night on my map and i compiled it overnight. ran the map this morning and it said steam validation rejected. i can run different maps...just now my own. im guessing this has to do with me using the -beta sdk to compile. any way around this or do i have to wait till valve fixes?
 
So far the beta works pretty good for me.

Still want to fix that info_player_terrorist/counterterrorist error thingy though.
 
ive tryed the updates and refresh sdk, also the work arounds... no luck, the best i can get is hammer to run with no 3d view!
Funny how I searched and found that steam "fixed" the error, allthough it still pops up for me every time.

If this keeps up much longer ill be switching engines.

is this some sort of sick joke?
http://www.steampowered.com/index.php?area=news&id=489
 
omg i was about to finish up my training level for my mod and look what happens i tryed to refresh concept but wtf:S
 
yeah they did fix it when this error first came around...too bad its back.
 
Im still getting the error too, i dont want to change anything just incase i screw it up, and i dont really want to temporarily circumvent it using the gameinfo.txt as im not sure if that would mess up model compiling.

For now that update is obviously a joke.
 
well everything works for me now. i actually had two updates 2-3 days apart, which was strange. after the 2nd one, everything worked (at one point, the hammer.exe disappeared entirely...)

btw for people have issues with the 3D window, i find it initially loads looking mostly black but if i just run the mouse pointer over it everything appears. even the editor prop fade preview works but frankly it's worthless since the concentric mesh spheres already do a good enough job in this department

i did however get one instance of that weird error where the texture normals of a brush's faces were inverted after using the vertex tool on it, but vertex tool worked fine elsewhere

i expect we'll be getting fixes for the fixes for some time on this one. i mean ffs, valve made the entire game without the sdk beta. why are fixing something that isn't broken?
 
is there any other program i can use? even if i ahve to pay for it?
 
yeah,... sure they did.
Thats why im staring at the error right now?

valve are realy loosing face with steam.
what a horrible program, and all so they can track customers.

sad.
 
another day, and the same error, i want to compile some models pls valve, i paid money k thx :p
 
ey.. not all of us want to mess around with the gameinfo, and .gcf files.. its a nice quick fix for using hammer.. but if you want to compile models and create new content the directory is still messed up so you cant, whats been suggested isnt really a fix, its more like a temporary work around/shortcut, not everything works properly, and your at risk of cocking everything up.
 
It Works

Yet another update.....

AND NOW IT WORKS!!

finally....
 
Back
Top