Another one is my metal textures, they seemed to have adapted some sort of "shiny" cubemap style effect, the 'problem' is though... is that it doesn't look right and almost has a checkerboard style to it.

Here, I took a screenshot. I'm interested in seeing what everyone else here makes of this.

What's also strange is, these "cube maps" or what ever they are, don't show up in the actual game either.

In addition, my Non-portal surfaces seem to work fine, regardless of the fact that I downloaded the "fix" for them and used it on my maps. Was this new SDK designed to be 'backwards compatable' with our jury-rigged SDK's or something? I find all of this... very strange to say the least.

As for using the pre-SDK workaround for non-portalable textures, no, those are no longer the case and you can safely delete those. The new VBSP correctly deduces which textures can and cannot have portals placed on them, as determined by the $noportal flag in the VMT.

msleeper wrote:
I think the cubemap fix will come with an update to Portal and not the SDK, since those files are located in Portal. We'll know soon enough, I think.

I hope you're right.

Just a thought though, and this is just flying off the top of my head. Has anyone considered that perhaps we're missing a setting or variable within the textures or surfaces themselves?

I'm quite new to Hammer, and the whole Source engine all together, so excuse me if this is rather silly to ask, but I just thought I'd ask.