Hammer start up problem

[Pegg]

Hey guys,

Iv just tried to open my maps in hammer and it seems my hammer is broken. Untill 20 mins ago it was working fine but not whenever i try open any map (itll load it then when the 3d screen is about to show the 3d image) i get this message.

the instruction at "0x0d6f3618" referenced memory at "0x0d6f3618". The momory could not be read

Any idea

[drp]

try and verify your .gcf files by right clicking on the sdk game in steam, and selecting the verification tool.

good luck

[Intraman]

hrmm it seems I'm having a similar problem. Whenever I load a map, Hammer closes itself after the loading is done.

[Snipergen]

I heard tf2 just had an update... might have to do with that? Dont know.

[YM]

I also am experiencing this problem since about 7pm today (GMT) :(

Edit: looks more like a full scale source update, ALL my source games now have 'news' in the update column

[drp]

ewww another bad update. this sucks.

[YM]

Thats so lame, I was going to get one and do a pretty heavy mapping session tonight, guess I'll just have to playtest the current version, I'm gunna run it on 'colts playground' in a short while if anyone wants to join me.

[Intraman]

Yeah, it seems a lot of other people are having the same problem.. gah.. just when I thought of a solution for an issue I was having too.

[MasHeeN]

I'm getting...

"The instruction at "0x0d593618" referenced memory at "0x0d593618". The memory could not be "read". Click on OK to terminate the program"

whenever I try and open a map created before the TF2 update that was released today. I can create a new map and save it and open it without issue but nothing from previously.

Have verified the cache on the sdk and refreshed the files, no joy. Does this look like a borked update?

[ZargonX]

Yikes. Looks like I better not update when I get home today.

[Paddy]

omg i got it too! when i open a map it loads but before i see it it just closes!

[Intraman]

is there anyway to rollback to a previous version or something? And how would you no update? it does it automatically.

[q2slinger]

Doing the same thing for me D:
Don't get the latest update.

[Haas]

no problems here i have seen the update dialog so there should be an update there is only no changelog :S

[drp]

http://tf2maps.net/showthread.php?t=489

[greenridge]

I cannot open old maps, nor can I do anything in a newly created map. Hammer crashes when I try to create a brush

[Mundinator]

Damn...hate to be the cheese standing alone, but everything seems fine to me. Loads, saves, creates new brushes just like before the update. Obviously something is messed up, but it might be something like old video card drivers or something strange like that.

[jakeparlay]

just use the old engine hammer. works fine!

under Source SDK launch options --> "-engine ep1" (without quotes)

reload SDK, hammer, etc .. and rock on!

edit: i just released, you'd still have to have an old ep1 hack for TF2 editing already in-place (like the type we used during TF2 beta mapping).. the only reason i still have it is, well, my gfx card doesnt work right with the new hammer :(

[Intraman]

...that's quite the work around though..

[Intraman]

Someone on the Steam Forums found a solution to the issue!!

I've possibly found a temporary solution!

It seems that certain textures now crash Hammer's 3D Shaded Textured Polygons viewport. Open up Hammer, create a new map, then choose wither 3D Wireframe, 3D Filled Polygons or 3D Textured Polygons from the View menu and quit Hammer so it saves the new default 3D view. Now try opening your maps. :)

[greenridge]

That fix works for me, thanks.

[Buddikaman]

Oh god damn, i wish i had read this before i thought it was just me! I tried reinstalling the sdk and everything, i was freaking out!!! Thanks for that tip Intraman, you rock.

-Buddikaman-

[Squirrelly]

well that was kinda scary coming home to a broken Hammer!

but the workaround works good enough for now at least

thx for the update!

[A Boojum Snark]

...shaded mode was broken period since the orange box SDK, why would anyone have been using it :(

[Kernel]

As stated prior, only shaded texture view is crashing. Func_respawn visualizer's and other shaders don't display properly anyway in this mode. I have always used 3d textured only views, so i don't have this issue. Just create new map, select 3d textured for camera view, close and reopen your map. You'll be back to business.

[Thristhart]

i have a similar problem, except that i get that error when trying to texture with nodraw. D:

[YM]

...shaded mode was broken period since the orange box SDK, why would anyone have been using it :(

just incase they fixed it and we didn't notice that it had been. But instead they go and b0rk it.

[Intraman]

I think a lot of people used it becuase on the wiki's "Building your first map in hammer" tells you to use it.

[phatal]

Ok. So it's not just me having these issues either. http://www.tf2maps.net/showthread.php?t=500

Someone on the Steam Forums found a solution to the issue!!

I tried this and it did not work for me.

Oh god damn, i wish i had read this before i thought it was just me! I tried reinstalling the sdk and everything, i was freaking out!!! Thanks for that tip Intraman, you rock.

-Buddikaman-

I did all this too that did not help. :crying:

The fix does not work for me either.

[Mundinator]

I think a lot of people used it becuase on the wiki's "Building your first map in hammer" tells you to use it.

Don't hesitate to change the Valve Wiki. The more people who do the better. I did for the first time the other day and now more people hopefully won't make the same mistake that I did by following the wiki.

[jahrain]

I have experienced the problem since I updated as well. I tried everything from reinstalling hammer/orangebox to updating video drivers etc. However I found out the error is caused by the 3d viewport. It seems when ever the mode is set by default to "3d textured shaded polygons" it crash on start up when loading a map. Also, it will crash when creating a brush, or applying certain textures in that mode.

You can some what get around this issue by first creating a new empty map, set the 3d viewport to "3d textured", saving the map, then reopening your map. It should not crash now that the viewport is not set to default to "3d shaded textured polygons".

[MacNetron]

Your post almost makes it looks like it is the first one in this thread which identifies the culprit and has the solution to it...

[timberghost_paintball]

I tried the fix mentioned above and it worked fine for a day. but now it keeps doing it regardless of the 3d view mode (even solid polys and wireframe). Is anyone else having this problem? I got the most recent update (after the one that probably caused the problems) and it still didn't help this problem.