@sebavan the bone under morph seems to drift away from it’s skeletal positioning:
CPU skinning:
GPU skinning:
@sebavan the bone under morph seems to drift away from it’s skeletal positioning:
CPU skinning:
GPU skinning:
Nope:( but we did several change recently around that function so this needs to be investigated
@Evgeni_Popov could you have a look into this one ?
I tried all version since 3.3 and they are all consistently oulining differences between gpu and cpu process that I can t find at the moment.
I guess the problem is this one:
?
The PR (Fix #6526 · BabylonJS/Babylon.js@3b7c0f8 · GitHub) did not fix that, it fixed being able to use the GPU to compute bones when needInitialSkinMatrix=true
.
I will have a look at it.
Computing bones on the CPU and using morph targets are incompatible, I have updated the doc about that:
Note it is not a regression, it has never worked (it is “by design”).