Click Detectors stop working when using a collision group that has can collide disabled to the default collision group

Bug Reports Engine Bugs
#1

Hello! I was developing my game and I just found this bug. Which basically happens when the parent of the click detector has a collision group with this configurations:


What happens is that the click detector just stop working, it dont show the icon, nothing happens. I tested it on a empty baseplate soo I know theres no script affecting it.

As you can see on this GIF the bug happens:

But if you change the collision group to the default one it automatically starts working again. The bug started today when I discovered it. 03/31/2020 (Probally this bug was happening before, but I just discovered it today.)

To reproduce this bug:

Following my steps it will happen 100% of time.

1 - You need have a collision group with these configs like I said above:

2 - Set the collision group of the click detector’s parent to the ID of the collision group.
And the click detector will stop working. This can be done while on the test mode and normally on studio.

375Ă—508 11.6 KB

My computer specs:

Processor: Core 2 quad Q8300
GPU: Sapphire RX 550 (4GB)
Ram: 4GB
Windows version: Windows 10 Pro 1909 64 Bits.

File:

ClickDetectorBug.rbxl (17.9 KB)

3 Likes
#2

I just ran into this today too. I started making my collision groups for the behavior I would like, and my Click Detectors stopped working. Same as OP reported.

Can anyone confirm if this is a bug or is expected behavior?

If it is expected, what would be the correct way to make an item system where the character isn’t physically blocked by items, but is able to mouse-click (ie click detector) to “pick them up” (to add to their inventory)?

EDIT: Never mind about the suggestion. I thought it was because the player-item couldn’t collide. But it was really because the item couldn’t collide with the Default group specifically (as OP reported). So I can work around that aspect.

Thanks

2 Likes