Quote from WinstonSmith on July 25, 2011, 10:24 pm

I'm guessing this means that the prop's collisions aren't being updated for some reason. I'm not sure if there's a some way to manually update collisions; I don't think there's an output to do so unless you want to try DisableCollision and EnableCollision.

Quote from MissStabby on July 25, 2011, 10:37 pm

i figured out that the problem is related to the button being attached to a panel arm
if i change that to a func_rotate or func_door it has no problems.

now i have the model parented to those object, though is it possible to have the parented model move relative to it's attachement point?

like the inverse of setparentmaintainoffset (or something that sounds similar)

Quote from WinstonSmith on July 25, 2011, 11:18 pm

You might want to try parenting the button to the panel that's parented to the arm model.

Quote from MissStabby on July 26, 2011, 5:57 am

That was the initial situation...
then i tried linking it directly to the arm, with no results, and then i just did 2 tests.

1. button linked to a door_rotating, not breaking
2. button linked to a move_linear, not breaking

And it seemed that those 2, and after that, a combination of those 2 didnt cause a problem.
Maybe the button breaks if it goes in a certain, 3 axis random, rotation.

Quote from Skotty on July 26, 2011, 10:12 am

You could create a nodraw brush for alternative collisions. So it doesn't care if the collisions of the button are active or not.

Quote from WinstonSmith on July 26, 2011, 10:40 am

Skotty wrote:

You could create a nodraw brush for alternative collisions. So it doesn't care if the collisions of the button are active or not.

This. You can use a func_brush and enable/disable solidity based on whether the button's in one position or another.