Disappearing model parts
See original GitHub issueHello,
I experience a weird problem when rotating some models in three.js. Under certain angles of view some parts of a model become invisible. The problem is definetely has nothing to do with material.side
.
Front view:
Back view (‘good’ angle):
Back view (‘bad’ angle):
Sample model: Sample_GLTF.zip
Three.js version
- Dev
- r98
- …
Browser
- All of them
- Chrome
- Firefox
- Internet Explorer
OS
- All of them
- Windows
- macOS
- Linux
- Android
- iOS
Hardware Requirements (graphics card, VR Device, …)
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Model Parts Disappearing During Live Sessions??
The only real fix is to decompile the model, fix the hit boxes and recompile or move your camera to an angle where...
Read more >Parts Disappearing - SketchUp Community
You've been hiding parts of your model. You'll need to get in there and start unhiding things.
Read more >parts of my models are disappearing as my scene gets ...
As I navigate around my growing scene parts of my models disappear. Is this a settings issue or is it because my computer...
Read more >Random parts have disappeared from my model ... - Reddit
Random parts have disappeared from my model, does anyone know what i can do to fix it? Specifically the upper right arm &...
Read more >Parts Disappearing for no reason?? - Scripting Helpers
I see a (bug?) that objects disappear from the game when transparency is 0 and can collide is false. ... 02, local children...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also related – https://github.com/mrdoob/three.js/issues/16055.
This isn’t a loader issue. Careful modeling can avoid the problem, but there are probably things we could do within threejs to handle more (but not all) similar cases, and documentation would be a nice addition.
I think this can remain closed, given the other threads that exist.
@donmccurdy, apologies, I think we posted at the same time. If you think this is covered in other issues adequately it’s ok to close this one, but could you link the other ones here?
Edit: oops, you already did 😁