Upgrading Shapecasts: Margins, Size Gradients, Optimizations, and More

the free speedup is huge, my game runs spherecasts on every ball every frame so this is a really nice win. is the 1024 stud max distance on shapecasts still a thing or did that change with the rewrite?

OH MY GOD SHAPECAST MARGINS ARE FINALLY HERE after years and years of begging

Roblox this is literally one of the best engine updates you have ever made thank you so much

Also… @MrChickenRocket Does this mean a Chickynoid update soon? :eyes:

The fact this is now way more accurate and more optimized is extremely impressive.

Thank you for making a QoL update that has a postive impact.

2 Likes

ohhhh this is insane especially the 4x times speedup

Hey team, that’s an amazing update! However when I play test with ‘Shapecast’ visualization enabled and I disable it while in play test, my Roblox studio crashes. Except from that amazing update!

Very cool! Can we get the ability to also visualize regular raycasts? Currently, I have to apply a non-zero margin of something like 0.001 to debug regular raycasts.

1 Like

MARGINS??? IT ACTUALLY ONLY TOOK 3000 YEARS FINALLY :smiling_face_with_tear:

1 Like

Since Capsules and other shapes are coming to Roblox as primitives, will methods for casting them also be added? For example casting primitive Capsules for custom character collision detection systems?

Awesome change! The override properties for shapecasts is huge as the requirement of cloning and positioning a part in workspace made it cumbersome to use! I hope the same will eventually be done for GetPartsInPart, allowing us to use parts as a template rather than having to physically position them before querying!

1 Like

yes they do.

if a shape with margin has initial overlap, the other shape is ignored.

Thank you for the suggestion, this is something that has come up multiple times. we want to add piercing casts.

Thank you for the bug report. We will fix this ASAP.

We wanted to add raycasts visualization with this update but without a way to filter them we end up with a lot of noise. Once we have a good way to filter debug drawing, we will enable this for raycasts. If you have any suggestions please do let us know.

1 Like

Isn’t this issue already present with shapecasts? It’s odd to exclude raycasts.

But to address your point, the issue stems from the fact every spacial query would be rendered. I propose a way to filter only queries you explicitly define need to be rendered. Maybe add a boolean flag such as VisualizeDebug in RaycastParams.

Additionally, you could group spatial query debug into logically named groups (again via RaycastParams) which get picked up by the debug tools and you can toggle them on/off as you need to.

1 Like