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
Quad support in current Three.js version #11655
Comments
This should probably be handled outside of the core. Why limit things to quads anyway? I've been using my own BTW, this:
😄 I love this attitude, three should at it's core be a better way to use webgl. Arbitrary data structures should be built on top of it. |
How could the THREE.js versions below 60 supported quad and why that could not be incorporated into the current version.? |
Three does not have any opinions on quads. You can support it yourself.
It would be more code to download that is not used by everyone. |
We decided to simplify the codebase. The renderer no longer handles quads. Instead, loaders that support quads, convert the quads to triangles during the loading process. |
Description of the problem
Upon my thorough studies and research, I came to know that current Three.js version doesn't support quad and supports only tria and quad was deprecated since Three.js 60 version.
I do want to know whether we could incorporate quad support in current Three.js version and whether it associates with the performance or rendering issues.
What could be done to optimise the performance with quad support in current Three.js version.
Thanks & Regards,
Aasha Joney
Three.js version
Browser
OS
The text was updated successfully, but these errors were encountered: