Recently Valve added the instancing feature set to hammer. What it basically allows you to do is have a vmf inside your map. This can be used in many ways: Easy copying of doors. Changing all instances of some copied brush. Distributed mapping. Etc…
What I wonder is the bugs of the instancing system. vbsp seems to ignore func_instances and hammer’s collapse even warns that it might be buggy.
Is it just me or this whole thing doesn’t really want to work?
Here’s what I do when I want to compile my map:
1. load map.
(1.1) Select random objects to generate undo history (handy when you have modified the map and got lots of instances)
1.5 Texture lock on (otherwise the textures get displaced in instances)
2. instancing->collapse all
4. undo changes (this is where the random object selection comes in handy. You can just hold the undo button until all instance collapses have been undoed and still not undo your changes that you might have made)
5. Start compiling
6. Wait for vbsp to finish (I’m using vbct for compiling so hammer doesn’t freeze)
7. Save (vbsp is the only thing that reads the vmf)
**8. **Keep “enjoying” the benefits of instancing
As you can see the way I do it is very prone to errors and generally just dumb. Is there some magic switch that I have to flip to get vbsp process my func_instance entities or do I really have to keep doing this until valve notices the SDK is flawed?