Sphere and block casts do not work and only return nil

Bug Reports Engine Bugs
#1

System Information
Intel Core i9 9900K
16GB DDR5 RAM
Nvidia GeForce RTX 2080Ti

Whenever I try to shapecast my attempts always result in nil.

image
image1485Ă—55 5.69 KB 

local p = RaycastParams.new() p.FilterType = Enum.RaycastFilterType.Blacklist p.IgnoreWater = true p.FilterDescendantsInstances = {game:GetService("RunService")} print(workspace:Blockcast(workspace.EtSapientisMagna:GetPrimaryPartCFrame(), Vector3.new(50, 50, 50), Vector3.one, p))

local result = workspace:Blockcast(CFrame.new(0, 0, 0), Vector3.new(5, 5, 5), Vector3.zero)
print(result)

Expected behavior

I expect my character to be returned in a raycast result or the baseplate itself.

2 Likes
#2

i thought it was just me.
i’ve been using it for a week now and for some reason it’s not working

#3

yeah i’ve been trying to use it for a character controller and it’s not working

would be nice to have it to work for it since the alternative is so slow

#4

System Information
12th Gen Intel Core i9-12900H
16GB DDR5 RAM
Nvidia GeForce RTX 3070Ti

I can confirm

#5

I thought this was just a classic “Works on My Machine™” bug on my end… I’ve been trying to find the culprit to this issue for ~ a week!
This definitely needs to be fixed ASAP.

#6

When did they add these? I know they were a highly requested feature, but I didn’t see any announcement about them.

1 Like
#7

So I was testing shapecasts for a while and here’s some stuff i found

  • If you have anything within the shapecast’s radius/size, It gets ignored
  • There’s also a minimum distance between the shapecast and the geometry in its path that depends on the size of the face (default baseplate’s top face for example, ~0.2 studs)

The only way i found to avoid these 2 issues is to shapecast from behind origin and ignore anything that it hits that isn’t infront of origin

Also shapecasts consistently crash if the terrain is blacklisted or not whitelisted

1 Like
#8

Thanks for the report! We’ve filed a ticket in our internal database and we’ll follow up when we have an update for you.

1 Like
#9

Glad ya’ll found them :slightly_smiling_face:

Shapecasts are actually in a soft-release mode while we’re staying (somewhat) quiet and looking for issues. We’ll be coming out with a more formal announcement and documentation.

The crash is fixed in this week’s release, and the “parts extremely close to other geometry don’t hit” is fixed next week. We have a few other bugs and optimizations we’re flipping on this week too - 34% faster casts against parts, memory reductions, and a fix for CornerWedges (whoops).

For the original post: Shapecasts don’t collide with objects that intersect the starting shape.
If you have a repro for a case where shapecasts don’t hit a shape that isn’t intersecting the starting shape, you should supply a .rbxl so we can debug it.

12 Likes
#10

I also can’t seem to get the shapecasts to work, tried both spherecast and then blockcast. Essentially just returns nil no matter the condition

image
image733Ă—630 76.1 KB

shapecastsbroken.rbxl (41.6 KB)

1 Like
#11

It’s not working for you because the direction of your blockcast is Vector3.zero

#12

I’ve noticed that shapecasting tends to miss (or hit at a wrong position) meshes & unions with collisionfidelities that aren’t hull or box

Here’s some gifs of it happening, you can easily replicate it with most meshes and unions.
https://gyazo.com/0aff1142019329ad64f408efc87494bd
https://gyazo.com/09d08382676105908c338d821d7793b4

#13

Thanks for the repro and the cool debug visualizer.
We found the problem; our bounding volumes for mesh hulls were off. Fix is in for next week’s release.

And yeah, this is exactly the sort of thing the soft launch was done to catch.

6 Likes
#14

I noticed this is also a problem for unions too where it just won’t detect them and go straight through, also noticed that when you use sphercast on the client it does crash immediately.
image
image

#16

It doesn’t seem that the starting position intersecting geometry spherecast issue was fixed? I believe it was supposed to come last week…? Or maybe I’m testing it incorrectly.

1 Like
#17

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

#18

Can confirm this is fixed! Thanks again for the report.

3 Likes