When debugging I cannot get the results now from raycast (it says can’t convert to string). Can only be viewed if you write raycastResults.Instance in ‘watch’. If it could please be fixed, makes debugging harder.
in the same vein as @RuizuKun_Dev, I am receiving issues with raycasts hitting impossible places. I confirmed this by calculating the distance of the hit point from the actual raycasted line - in normal scenarios, it should never exceed 0.01 studs, but in some cases it exceeds 1 stud.
I have made the most minimal repro file I could, but the issue only seems to occur when raycasting in bulk by the looks of it, as raycasting from the exact same positions doesn’t work.
I have created a thread on it but it gained no traction, and as this bug is very dangerous for games, I’d appreciate any sort of support in regards to it:
Blacklist/Whitelist are taking the same times for me in a 5000 part moving assembly area.
Is the raycast now just naive cast and then checked against the blacklist? Old form had performance benefits to using a whitelist only iirc. Or do physics updates force updates on raycast, even if its from parts ignored?
This is a serious performance issue for me, with 15 rays/frame. The first RaycastBroadphase takes wayy too long, at 2.3ms on a 3070. The subsequent ones being negligible (~.05ms less).
(“fat ray” being a user profile just encompassing the raycast call)