-
Notifications
You must be signed in to change notification settings - Fork 294
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
Force all backfaces visible in XKT models created with xeokit-convert #804
Comments
"It's not a bug, it's a feature" |
is there any way to change it so it will be shown? |
There is some low-level stuff but I never used it. |
Only when building scenes using the That's by design, because we rarely want to slice open things built with those components, to see their backfaces (eg. NavCubePlugin). However, you can control backface visibility within models loaded into the That's used to represent models loaded by the various loader plugins, from XKT, glTF, CityJSON, IFC etc. The The Viewer will render "surface" geometries with backfaces visible, and "solid" and "triangles" geometries with backfaces hidden. Maybe you could switch to using VBOSceneModel? As long as you don't need animated transform hierarchies (ie. as supported Node and Mesh components), it should have all the methods you need otherwise.. |
I'm loading all using XKT files instead of generating the geometry. |
Currently, We can't override that currently - it does not currently expose an option to force all triangle mesh primitives to be "surface". We'd be open to adding that as an option within For this feature, we'd want a PR on |
when I create a mesh with a geometry - as long as it is not sliced it looks ok,
but when it is sliced - you can see that it is hollow, and if you look at it exactly from the top - you can't even see it.
I used buildCylinderGeometry. I tried playing with the properties - but nothing helped.
also tried with phongMaterial , and emphasis material using xray , but all are hollow.
when not sliced:
when sliced:
when exactly top:
The text was updated successfully, but these errors were encountered: