http://www.steampowered.com/v/index.php ... 1294cc=US

It's live... I know it's posted already here, but for those that need an official post ^^

&&&

Hammer sucks now.

So aside from Hammer sucking, can someone describe what this changes and how it will effect mapmaking and the portal community? What new stuff can we do, and what will this make easier?

Best response will get credit on the front page news story about the SDK. (Assuming someone doesn't beat me to the punch.)

Hober wrote:
Best response will get credit on the front page news story about the SDK. (Assuming someone doesn't beat me to the punch.)

If someone can get me a screenshot of the Update News, I'm going to make it.

http://www.steampowered.com/v/index.php ... wsid=1294

Get your own screenshots.

&&

No, I mean from the window in Steam.

Best thing I noticed so far is non-portal surfaces are automatic now and don't require nodraws in front of them. Also the sample map is very useful, shows most of the important stuff you need to know like correct lighting, shadow control, cube tube, moving exit lift, buttons, soundscapes etc.

News in steam hasn't been update yet.

PLEASE BAN ME

Where do you find the example map?

Steam\steamapps\user\sourcesdk_content\portal\mapsrc

Hmm, I have the updated SDK but I don't have that folder... maybe I need to re-download?

Jaxe wrote:
Steam\steamapps\user\sourcesdk_content\portal\mapsrc

I dont have a "portal" folder in the "sourcesdk_content" folder

espen180 wrote:
Hammer sucks now.

Why? What's different?

Guitar wrote:
I dont have a "portal" folder in the "sourcesdk_content" folder

Launch SDK and click refresh game content.

ok so the SDK is still updated but why can we not build cubemaps in game?? how did they do it?

I haven't really noticed any problems with hammer, other than perhaps more resource usage.

main thing I noticed is the portal cleansers are no longer "Obsolete" but are now "ERROR" in big red capital letters... Also point_spotlights are now also "ERROR" so it looks like we traded one non-working entity for 2 non-working entities, one of which is still the same one as before

I don't get error for point_spotlights. I do get it for portal cleansers though.

Both work when complied.

The ERROR model just means the model it is looking for doesn't exist, it has nothing to do with the actual working of the entity. I have heard something about directory structure changes, so this might be a side effect of that. As for the info_particle_system ERROR model, we probably don't have the model for that at all (unlike the light_spotlight).