Talk:Func portal bumper
The discription should be clarified. --Darthkillyou 21:27, 21 Nov 2007 (PST)
It is. Haha.--Gear 23:09, 21 Nov 2007 (PST)
No it isn't. It just doesn't seem to make sense to me... --Darthkillyou 20:31, 22 Nov 2007 (PST)
Well it makes sense to me. Maybe due to the way its written.--Gear 21:28, 22 Nov 2007 (PST)
- "An area that portals cannot enter, or in other words, overlap. Used to prevent portals from overlapping onto non-portal textures."
That's still not quite right... Make a big cube room and put a metal texture on half of one of the walls. Portal won't let you fire a portal within 32 inches of the metal even if your crosshair is on the portable surface. I'm pretty sure that the Bumper will both let you fire a portal no matter how close your crosshair is to the metal, and then move the portal so that its edge is on the metal. --volt 23:51, 22 Nov 2007 (PST)
- Putting this into words is pretty hard, although, a picture might demonstrate it pretty easily.--Remmiz 00:09, 23 Nov 2007 (PST)
If you make the automatic portal border (even in official maps, try testchmb_a_02) if you shoot about 32 units above either border side, your portal will clip about 32 units into the frame. I tried to solve this with an 8x8x8 func_portal_bumper on each side and it didn't stop the portals from doing the same. Just so you know. --volt 05:43, 23 Nov 2007 (PST)
- Not quite sure what you are talking about...frame? If you have an area that labeled as portal-able in it's texture .vmt, but you dont want it to be, you should cover it with func_noportal_volume. func_portal_bumper is just used between a portal-able and a nonportal-able surface.
- Sorry I was very unclear... I meant a prop_static with model "autoportal_frame" --volt 12:46, 23 Nov 2007 (PST)
