Please or Register to create posts and topics.

Toggling a brush's visibility?

PreviousPage 2 of 2

The map might compile and load up, but that doesn't change the fact that is NOT how the func_areaportalwindow should be used and, when used in a map with proper func_areaportalwindow's, could cause some big problems.

[Important Threads] Forum Rules | Welcome to the new Thinking With Portals
Please do not Private Message me for assistance. Post a thread if you have questions or concerns.
If you need to contact the staff privately, contact the Global Moderators via Discord.

No problem here :
http://hl.logout.fr/images/tuto_opti/areaportalwindow0.jpg
http://hl.logout.fr/images/tuto_opti/areaportalwindow1.jpg
http://hl.logout.fr/images/tuto_opti/areaportalwindow2.jpg
It's used for what it's supposed to be used, and it acts like a ghost wall.
But well, ok. I agree that it should not fall in inexperimented hands.

Actually that is a totally legitimate use of areaportalwindow. Granted you are exploiting the fade on it to do stuff besides what it was intended, but that's not what I meant. If you make a free floating brush - one that is not sealed on all sides by world brushes - and make it a func_areaportalwindow, you will get problems.

Neat trick by the way. ;)

[Important Threads] Forum Rules | Welcome to the new Thinking With Portals
Please do not Private Message me for assistance. Post a thread if you have questions or concerns.
If you need to contact the staff privately, contact the Global Moderators via Discord.

Enabling then disabling the brush does the trick perfectly. Thank you all for the help.

So THAT'S how you do that!
msleeper wrote:
If you make a free floating brush - one that is not sealed on all sides by world brushes - and make it a func_areaportalwindow, you will get problems.

Yeah, lol, of course.
I thought it was obvious, but I forgot that it's not for everyone.
Sorry :)

PreviousPage 2 of 2