I'm just about to install a 'steam backup-ed' version of the source sdk which is about half a year old and which works fine, is it safe to let it connect to the net and update or have the new updates buggered it up too badly?
Also will the sdk run straight from the 4meg steam install + DOD:S backup + SDK backup or do I have to connect anyways?
Ta.

Latest version of Hammer seems to work fine for me,

The only thing I had a problem with was the Models loooking like they were torn apart in the 3d view.

But a simple fix was found and now its all good

This was the fix that worked for me:

Place a shortcut on your desktop to hammer.exe and place this in your target line: (obviously change the loaction to where you have hammer installed)

e.g D:\Steam\SteamApps\<username>\sourcesdk\bin\hammer.exe -dxlevel 80

This made hammer use dx level 8 to draw models etc, works well for me and now there are no other major issues at all :)

Workaround aside, are they planning to address these Hammer bugs in the update on the 28th?

SDK updates are never announced, so I wouldn't hold my breath until the 28th. It'll come when the release schedule allows, and clearly the free SDK we get (which is different than the one the companies get) should be the least of their worries with said schedule being as congested as it seems

I never had a single problem with any update on hammer and I use it every day.

Originally posted by Dash
I never had a single problem with any update on hammer and I use it every day.
Then you are of the lucky few :sheep:
At least there is a large enough community to whinge loud enough for valve to take notice

Originally posted by Ca-Chicken-Soup
Then you are of the lucky few :sheep:
At least there is a large enough community to whinge loud enough for valve to take notice Same here. Since they fixed the .1 brush scale everything's been fine.

I just wanted to say that I have been having a lot of problems with the SDK since the last update. I haven't been mapping for over a month because of it. I have a horrible time doing anything with HAMMER as all of the models in the map are corrupted and are just splintered all over the place in tons of triangles. I was even working on a house before I realized there was a problem with the editor, I saved what I had done, and the next time I went back to work on it the WHOLE front of the house was gone... I wasn't even using models, except for the window frames, but those were there and looking just fine... but yea, the front was gone, no textures, all there was was when I clicked on the invisible part there was a red outline of what I had built...

So hopefully something can be worked out and released soon as I have been really wanting to finish up what I have been working on!

Good luck VALVe :)

Christopher

I guess I'm one of the lucky few...hammer works just fine for me.

Also the compile tools are fubar for wome reason . . .

When i compile my latest map dod_gamein i get very tweaked lightmaps even after reinstalling the sdk and there havnt been many changes to the map since the last successful compile . . .

Originally posted by TOP GUN Mav
Place a shortcut on your desktop to hammer.exe and place this in your target line: (obviously change the loaction to where you have hammer installed)

e.g D:\Steam\SteamApps\<username>\sourcesdk\bin\hammer.exe -dxlevel 80

This made hammer use dx level 8 to draw models etc, works well for me and now there are no other major issues at all :) Does this work for the model viewer also???

I have temporarily halted skinning until the update, BUT my model viewer is showing torn apart models since the update, making skinning an impossibility for me unless it is fixed moment.

Just leting ya'll all know I installed the SDK and the models are doing the tearing thing, quite annoying, the tearing even causes it to render slower. I came up with a work around of just turning the rendering distance of models to 0 so they are all just yellow boxes :rolleyes:

My VRAD is bugged all to hell (crashes every time) and hammer wont let me have overlays, a single one on ANY surface causes a OVERLAY_BSP_FACECOUNT error.

These errors happen independantly of eachother, of course.

Originally posted by FMPONE
My VRAD is bugged all to hell (crashes every time) and hammer wont let me have overlays, a single one on ANY surface causes a OVERLAY_BSP_FACECOUNT error.

These errors happen independantly of eachother, of course.

That's a map error and not a Program error :p

Not if its any overlay anywhere on any number of real and box test maps XD

Then it stops being under my control and becomes an entity hammer (the program :O) wont let me use.