Cannot Select BasePart In Certain CollisionGroup

Bug Reports Studio Bugs
,
#1

I am unable to see the collision group of the part I am trying to select and even select it because it is in a collision group. This makes it impossible to work manually with collision groups.


It looks like it does not get all the active collision groups. The ones shown are unrelated to the part that is having issues. This means that all active collision groups does not show up. This issue is only present in studio btw.

image

Repo File:
rails.rbxm (22.9 KB)

2 Likes
#2

For your information, check your code; if :SetPartCollisionGroup() is in your code, as far as I know, it is deprecated.

1 Like
#3

If the collision group can’t collide with the Default collision group, then it can’t be selected by the cursor. This doesn’t seem like intended behavior though

1 Like
#4

There is no code at all. It all was manually set.

1 Like
#5

Thanks for the report! We’ll follow up when we have an update for you!

1 Like
#6

The dragger uses the default collision group to raycast for things to select. Things which aren’t set to collide with the default group will not be selected.

1 Like
#7

That is new behaviour. I went back to a old cart ride project and I could not select anything that was in other collision groups. Would it be possible to make the dragger raycast to see these collisiongroups?

1 Like
#8

It’s definitely been like this ever since CollisionGroups were first introduced.

I’m actually finally looking at some solutions as part of the dragger QoL beta but as or right now this is the expected behavior.

1 Like
#9

It’s definitely worth exploring a solution. Maintaining any old work will be impossible if they used this workflow, and it will be a real pain for the creators to fix.

1 Like
#10

I want to highlight if you hold down ALT with the dragger and select parts using the box cursor selection, then you can actually select these objects.

image

However, if you try to select them by holding down ALT and attempting to click on the parts individually, then it won’t work.

(The blue dot is where my mouse is)
image

image

#11

Yes, box select will still get them because it looks at the positions of all parts in the workspace, vs clicking does a raycast which is influenced by collision groups.

The solution I have in mind is making the raycast use a dedicated “selection” collision group rather than Default, so that you can set exactly what is and isn’t selectable.

2 Likes
#12

Do you have an ETA on when this update will roll out?

1 Like
#13

At least a couple of months, and there’s no guarantee it will happen. You should look for other workarounds.

1 Like