Morph targets is broken for large number of vertices
See original GitHub issueMorph target animation breaks the mesh apart when there is over about 100K coordinates (~33K vertices). The image below is taken from the webgl_morphtargets example. I created the box geometry with 75 segments in each dimension. This results in just over 100K coordinates.
const geometry = new THREE.BoxGeometry( 2, 2, 2, 75, 75, 75 );
Platform:
- Device: Dekstop
- OS: Windows
- Browser: Chrome
- Three.js version: dev
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Unreal Engine 5 / (4-27) - Vertex normals breaking with morph ...
I have been using morph targets for character creation and curve based facial animation. In my case it worked in both 4.27 and...
Read more >Morph targets interpolation problem - mrdoob/three.js - GitHub
Hi! I have a strange effect when I use 9 morph targets on my mesh: vertex's interpolation is not always working.
Read more >Three.js: Get updated vertices with morph targets
Morphs are updated on the GPU, not the CPU. So if you want to know the new vertex position, you have to do...
Read more >Tricks to Decrease Morph Target Sizes? - PlayCanvas Forum
Hello, I'm trying to decrease the size of glTF models that use morph targets (we just use morph targets directly, no animations).
Read more >Fix vertex order for morph targets and restore symmetry using ...
I've run into this a few times and I see there's no consistent fix for it. Until now, at least in 3ds max....
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
@mrdoob It’s a GTX 1080. Looking at the logs, I believe the driver was 471.68, but I’m not certain. It wasn’t extremely out of date.
Thanks for responding, I updated my graphics driver and it seems to work fine now.