tieing displacement brushes to a detail entity

[WAR_Nuker]

dont ever do it....ever....never ever do this....just fair warning to my fellow editors. the map will not compile correctly.

 

[DaMaN]

lol, went bad did it?

-DaMaN

 

[gh0st]

Heh, why would you do that anyway?

 

[DaMaN]

I guess it could come in handy, but...

Didn't Valve warn us about that?

-DaMaN

 

[Raeven0]

Having a displacement as a func_physbox could be quite useful, but a displacement as a func_detail would just be redundant

 

[RomeoJGuy]

Displacements must remain static that is why they are not allowed to be tied to any entity. They are designed for static collision and world geometry.

 

[WAR_Nuker]

it was an accident....i went multiselect crazy....

 

[PMonkey]

lol, not the best of ideas I did that once and forgot that I had tied quite a lage chunk of my map to it. Had to build it all again

 

[Raeven0]

lol, not the best of ideas I did that once and forgot that I had tied quite a lage chunk of my map to it. Had to build it all again

Couldn't you have depressed the ignore-groups button and toWorlded all the displacements?

(Word of the day: toWorlded, past tense and past participle of "to toWorld" )

 

[WAR_Nuker]

yeah thats what i did to fix it (toworld). problem was they were taken out of their visgroups so i had to reorganize those. never heard of ignore-groups button.

 

[Raeven0]

It's really neat. It lets you edit the individual brushes of entities without editing the entity itself.

 

[Phisionary]

isn't that the same as using the 'solid' sub-selection level?

 

[Raeven0]

Well, sure, but I removed that selection... bar... thing... because new things scare me.