Talk:Hammer Cordon Usage
I have a map where the cordon is stuck permanently on and unchangeable. That is, no matter what I do to it in Hammer (turn cordon off or change its bounds), there is never any change in the compiled map, whether run in Hammer or in the HL2Ep2 engine -- I still only get the area originally cordoned off, in the state that it was when it was cordoned off (i.e. later additions of and changes to world geometry and props are ignored as well). Anyone have any suggestions? --Sagesource 16:47, 28 Jul 2008 (PDT)
One thing that I have done with this map is use map_edit and hammer_update_entity to adjust physics props when the cordon was turned on. It seemed to work fine, and is the most sensible way to work on the face of it, but it may have screwed with the map somehow. --Sagesource 10:33, 29 Jul 2008 (PDT)
If I cut and paste all of the map contents into a new map file, it won't compile at all. I just get a message that "Windows cannot find" the file that's right there and open. This is getting very frustrating. --Sagesource 22:50, 28 Jul 2008 (PDT)
Finally beat the problem by the rather extreme method of adding the six external walls to a visgroup, hiding them, selecting everything else and pasting it into a new file, and then rebuilding the external walls from scratch. But I would rather not have had to do that. --Sagesource 10:33, 29 Jul 2008 (PDT)
Cordon & VisGroups
I don't know when VisGroups were introduced to Hammer, I'm working exclusively with Portal 2 Authoring Tools. Anyway, it seems as if Cordon and VisGroups share a large amount of features and I think it might be reasonable to add a section dealing with this.
Also, there's a Create Cordon button in Portal 2 Authoring Tools, letting you name Cordons. Cordons will automatically form a VisGroup. Is that true for other current versions of Hammer? If so, that has to be incorporated!