WorldModel looses CollisionGroupId causing collision groups to be ignored in Raycasts and etc

Bug Reports Engine Bugs
,
#1

When parts are added to a WorldModel they loose their CollisionGroupId property (Or it never gets set?).
However The raw CollisionGroup is kept, and the CollisionGroupId can be manually set after.

image
image1353×589 69.3 KB

image
image1297×126 17 KB

Full repo example:
WorldModelGroupIdRepo.rbxl (48.6 KB)

Even after fixing this manually it looks like WorldModel:Raycast still doesn’t respect RaycastParams CollisionGroup, which could be a separate issue, or a further symptom that WorldModel’s don’t respect CollisionGroups at all.

Expected behavior

I expect WorldModel to respect CollisionGroup just like workspace does without having to perform a second manual cleanup step.
Or if WorldModels are unable to use collision groups then I would expect that to be documented somewhere (With an explanation, as this seems like deeply useful and expected behavior)

#2

Thanks for your report! We’ll make sure to get to work on this when we can.

#3

Duplicate of CanCollideWith does not respect CollisionGroups when Parts are under a WorldModel that is not workspace
We will update the other thread if we have an update.