Fine detection bug?

[ASD]

Object A "Use fine detection" Enabled.
Object B "Use fine detection" Disabled.

When a transparent area of object B and object A collided, the object was destroyed.

Is this a bug?

MFA: finedetection.mfa

[Shawn]

Well if you have fine detection disabled on Object B, its transparent area will have collision detection.

[Burfelt]

The collision engine in the non HWA version of MMF is dodgy when you have fine detection on and off like that.

Yves has confirmed that it's a bug, but it should be working fine in HWA.

If you rely on these types of collisions, use HWA for now. I'm guessing this will be fixed somewhere down the road.

[Burfelt]

Shawn: He is talking about the transparent area of object A which upon overlapping Object B shouldn't trigger a collision, but it does!

It's a known issue in the non HWA version of MMF.

[ASD]

Is there a collision detection in not only a transparent own area but also a transparent area of other objects when "Fine detection" is disabled?

[Dynasoft]

It acts like both objects have fine detection disabled.

[Shawn]

Okay I understand now. If object A's fine detection is enabled it shouldn't trigger anything if something collides with it's transparent area. As Burfelt mentioned that is a bug.

[mobichan]

I was told a long time ago that if one object in the collision uses "disabled fine detection", then both objects are treated as though they don't use fine detection. This may not be a bug, but it would be nice to have both kinds of detection able to interact with one another.

Mobichan

[danjo]

its been an old exsisting bug. just enable both on fine detection. the only reason to disable would be for speed gains.