-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invert Colliders #521
Comments
So, I think you can simply reverse the sphere face direction. |
Appreciate the speedy reply Yomotsu doesn't seem to affect the outcome... |
unless you mean id have to construct my own custom sphere buffergeometry and somehow do it in the constuction of that? |
What about this? Also, to better understand your case, would you mind providing a simplified example in JSFiddle, CodeSandbox, or any other similar platform? This would greatly assist me. |
Is your feature request related to a problem? Please describe.
I'm trying to use the colliders array in a particular scenario where the camera is inside a collider.
(Specifically a generative planet model that has its height map displaced inward) & I'm trying to avoid the camera going a)outside of the containing sphere as well as avoid the "mountains" etc that extrude inward.
For simplicity, I created a collider mesh with radius equal to the planet radius minus the tallest peak of the displacement with the view this would stop the camera going any closer to the interior surface than the heighest displaced point.
Evidently the colliders function with the camera assumed to be outside of the collider.. When the camera is moved outside / between the collider and the real mesh, I cant re-enter the collider so its obviously doing its job, but the wrong way round to what i desire.
Describe the solution you'd like
Is there any way the collider detection can be inverted so that it stays inside the collider mesh rather than avoids the outside?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: