Collisions disabled: what does this do exactly ?

In the Region/Estate panel, there is a feature that allows you to disable Collisions. In what cases is this desirable ? Thank you for your time.

Steve

on edit: Disable Collisions: Stops objects from causing collisions on the Region. Where you have a rogue physical object causing problems, this can allow you to reach the object and remove it.

https://support.secondlife.com/ics/support/security.asp

well all I can add is that i have access to this, being a manager, but the guru scripter who I answer to, instructed me "NEVER touch disable collisions, because SL is buggy as hell and you really have to know what your doing".

So ignore it?

<random guess>
Without collisions, physical objects can interpenetrate and since avies are physical every single prim would probably act like it's set to phantom. It would probably also be impossible to stand on anything since you'd simply fall through the prims and the land never to be seen again .
</random guess>

Probably best to resist temptation to see what it actually does .

I thought I heard somewhere that this disables the collision events in scripts etc. but I can't find a reference to that. This reference here:
http://wiki.secondlife.com/wiki/Estate_Menu
Seems to corroborate Kitty's post, that physical objects would become sort of phantom.

-Atashi

My understanding of attempts at collision detection in other games, Star Wars Galaxies in particular where they have failed most spectacularly to implement it, is that it has to do with the AV detecting objects. So I would suspect your AV would become phantom to objects, not that the objects would become phantom. Not a pretty sight, I would think!

@Dekka Raymaker *waves* Hi Dekka!

Well I was curious so I just went inworld and disabled collisions for one of my regions.

It did not make me phantom, it did not make everything else phantom, and I didn't fall through the floor or fall through the ground.

All it did, was disable the collision event from firing in scripted objects. At least, in 2 or 3 minutes of empirical experiment, that was the only thing I could determine. Physical stuff stayed physical and solid, everything behaved normally, but scripted stuff no longer triggered the collision event.

Once collisions were re-enabled, the collision events could happen again, but collision events that had happened while it was disabled, were not queued or saved, so turning collisions back on did not result in an 'avalanche' of stored collision events.

-Atashi

...To boldly go where no AV has gone before! You've got some guts Atashi, I have to hand you that.