You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, just trying to clarify what this issue is about.
I'm currently having a problem where I have a mesh whose material is set to THREE.FrontSide, but I want to receive both forward facing and backwards facing intersections when I do a raycast.
Does this issue mean I could configure the raycaster to "ignore" the material parameters and just give me all intersections? If so that would be great.
No - this is for shader functions. The cpu raycast functions match the behavior of three.js' built-in functions. If you need both sides of the raycast hits both three.js and this project are flexible enough for you to change material settings or provide custom bvh raycast parameters to get what you're looking for.
Related to #463
The text was updated successfully, but these errors were encountered: