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
gtx's intersectRayTriangle method does backface culling. Is this intentional? If yes, then should it not be noted in some form of documentation (I might be blind but I couldnt find anything)?
The text was updated successfully, but these errors were encountered:
This extension has been in the TODO list of think to fix and write tests for a long time... Actually this is why I think your pull request needs some tests.
It could be a bug, I honestly don't know. If you fell like fixing it in a way that it is consistent with your intersectRayQuad method, you have might blessing.
Currently my methods cull in the same way the original methods do. But this is not something that is particularly hard to change if wanted. I guess the central question is: Should a generic intersect method do backface culling? I can see scenarios where triangle-ray intersection (or quad-ray) would not want this behaviour. But then again for most normal practical use-cases it probably would not matter much.
gtx's intersectRayTriangle method does backface culling. Is this intentional? If yes, then should it not be noted in some form of documentation (I might be blind but I couldnt find anything)?
The text was updated successfully, but these errors were encountered: