A frustrating problem

  • If you're asking a question make sure to set the thread type to be a question!

elpee

L1: Registered
Jul 24, 2009
2
0
So I've been doing a little bit of mapping lately, and I decided the time came to actually make different save files for newer version after a lackluster improvement. This, however, is where the problem comes in.

Let's say I'm working on a map called ctf_bacon_a3 or something. I add a large sniper tower and call it a day, saving it as ctf_bacon_a4. When I run the map, though, this message appears:

The command failed. Windows reported the error: 'the system cannot find the error specified' Do you wish to continue?

looking through the (cut short) compile log, we find:
Loading c:\program files\steam\steamapps\myaccountnamehere\sourcesdk_content\tf\mapsrc\ctf_bacon_a4.bsp
Error opening c:\program files\steam\steamapps\myaccountnamehere\sourcesdk_content\tf\mapsrc\ctf_bacon_a4.bsp

This has happened before, but I solved it by opening a new file and copying my map into it and then saving and running it, but this no longer works.

So I thought hammer wanted a bsp, so I made a single block in a new map, compiled it, THEN pasted my map into it and saved it and compiled it again. This got rid of the annoying message, but the only thing compiled was the block.

I'm stumped now, does anyone have any ideas?
 

DJive

Cake or Death?
aa
Dec 20, 2007
1,465
741

elpee

L1: Registered
Jul 24, 2009
2
0
Thanks for that link, DJive. It turns out the problem was my ceaseless search for optimisation (or lazyness), which lead me to make a brush with player clip on one side and block bullets on the other.
 

Big Lou

L3: Member
Mar 17, 2008
120
27
P.S.

When saving new versions of a specific alpha release (a3 as you had put it), it's not necessary to change it to a4, a5, etc. with each minor update. Simply add an 'underscore' and 'letter' to it. Then, upon release, you can modify to a higher alpha.

For instance, if you have a map in it's 3rd alpha stage (map_a3):

If you added a few things to it, name the change "map_a3_a".
With more changes, name it "map_a3_b" and so on...

Eventually, when you become comfortable to release the map for another public release, you may upgrade it to a4.

Hope that's not too confusing! It just makes it easier for you and all of us to keep your files organized.