- Feb 19, 2009
- 147
- 11
Hammer has recently (about an hour ago) been acting up on me in very odd way. When I compiled my map to take a look at some lighting, the version that TF2 ran was not the version that I had sitting in Hammer, but instead the version that I had compiled and ran previously. I figured I had accidentally screwed up some settings, so I closed Hammer, Source SDK, and Steam, then ran them again. Still no luck. This persisted until I tried deleting the .bsp file in both the TF2 folder and the SDK Content folder, at which point it gave me an error that it couldn't find the file to copy. I then tried renaming the file completely and compiling that, and it gave me the same error. So I tried compiling the "real" map again after throwing away some more files associated with it, and it worked. Once. Not a half hour later and I'm running into the exact same problem.
I've already taken the compile log to Interlopers, and it returned this:
In unrelated news, the border around the TF2 window is now visible when it wasn't previously. This may or may not have something to do with the above.
tl;dr: When I go to compile my map to look at changes, it runs the old version, not the new one. Attempting to delete the existing .bsp and .vmx files returns an error when it attempts to compile.
I've already taken the compile log to Interlopers, and it returned this:
Which has been appearing in the compile log since day one, so I doubt this is the cause.can't load skybox file skybox/sky_nightfall_01 to build the default cubemap!
In unrelated news, the border around the TF2 window is now visible when it wasn't previously. This may or may not have something to do with the above.
tl;dr: When I go to compile my map to look at changes, it runs the old version, not the new one. Attempting to delete the existing .bsp and .vmx files returns an error when it attempts to compile.