Updates to Collision Groups

Updates Announcements
,
#65

As a developer that used the collisiongroupid value very much and now needing to type a long string for them to work is quite annoying.

2 Likes
#66

If you prefer, you can still use the id as a string for collision group name. No need to set it to a long string.

2 Likes
#67

honestly not sure what the point of this change was, I presume it’s some backend stuff, but this is going to be a pain to fix all of our collision group scripts. welp, time to spend hours finding which scripts use this…

1 Like
#69

use findAll/replace all to find which scripts use the deprecated function.

#70

I still have to go through all my scripts to do that… ctrl+F right?

2 Likes
#71

There is a way to find sound id’s, Names, etc. There is a tab in Studio called “VIEW”, find “Find All / Replace All”. It allows you ctrl + f in all scripts with that “name”. Allowing you to replace all “CreateCollisionGroup” to “RegisterCollisionGroup” in a second or two in all scripts.

2 Likes
#72

do you know if there is a hotkey for this?

1 Like
#73

No, I tried to screen shot. It looks like a magnifying glass.

#74

How would I use either of these. This is how I used one of them.

PhysicsService:SetPartCollisionGroup(Ddummy, “KEEpDummy”)

Do I just put BasePart.CollisionGroup in this place of SetPartCollisionGroup
like: Ddummy.CollisionGroup(Ddummy, “KEEpDummy”)

#75

I think you would just put

Ddummy.CollisionGroup = "KEEpDummy"
4 Likes
#76

Ctrl/cmd + shift + f should bring it up

1 Like
#77

Hey! going back to this, has there been an update on whether this is coming out, or if it already is?

#78

Here you go.

1 Like
#79

The current state of the Collision Groups Editor is unsatisfactory. Unfortunately, I am unable to share my concerns on other threads, so I hope this will suffice.

My concerns are not limited to the Collision Groups Editor alone but extend to the Collision Group service as a whole.

Firstly, I would like to address the issues with the Collision Groups Editor.

2nd It is challenging to move and set up collision groups in other experiences, unlike the new Material service. The Collision Groups Editor is cumbersome to work with and slows down the workflow. It is frustrating to have to repeatedly set up the same collision groups in new experiences. Simplifying the process, similar to the Material service where you can copy and drag items, would significantly alleviate this issue.

While the Collection Service could benefit from similar improvements, it already has multiple community-driven plugins and a well-functioning inbuilt editor within Studio. In contrast, Collision Group lacks such advantages.

Once again, I would like to emphasize that I do not intend to come across as mean or entitled. If I have given that impression, I apologize. My aim is solely to inform the staff team about the issues that I have encountered.

6 Likes
#80

Hi Joe, thank you for taking the time to provide such thorough feedback.

We addressed a couple of issues recently with the CGE, after a bug was reported here: Collision Groups Editor unable to select proper group. The bug in the video snippet you recorded should be fixed with that update, please let us know if you’re still encountering issues.

This won’t be the last time we update the CGE, and I’d like you to know that your feedback is valued and will help us in development of future changes to the tool.

3 Likes
#81

For some reason, i can’t really figure out how to use the new ones.
Can someone tell me?
I’ve tried to do v:CollisionGroup(“Ragdoll”), v.CollisionGroup(“Ragdoll”), didn’t really work.

1 Like
#82

The newer CollisionGroup is a property that you set like a string variable. In your case, you would use:

v.CollisionGroup = "Ragdoll"
2 Likes
#83

What about “:CreateCollisionGroup()”? What do we replace with that?

1 Like
#84
1 Like
#85

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.