Releases: pixiv/three-vrm
v3.3.0
π VRMUtils.combineMorphs
π
In #1546, we have a new function, VRMUtils.combineMorphs
, that combines morphs based on VRM expressions.
If you are not using morphs directly via mesh.morphTargetInfluences
, This function might improve the performance, reduce the VRAM pressure, and prevent shader errors in mobile devices caused by models with many morphs.
We recommend adopting this function especially if you are building an application that loads arbitrary models.
VRMUtils.removeUnnecessaryVertices( gltf.scene );
- VRMUtils.removeUnnecessaryJoints( gltf.scene );
+ VRMUtils.combineSkeletons( gltf.scene ); // introduced in v3.2.0
+ VRMUtils.combineMorphs( vrm ); // π introduces in v3.3.0
β¨ New Features
- #1546: Add
VRMUtils.combineMorphs
for reducing the number of mesh morphs
πͺ Performance
v3.2.0
β ATTENTION! β
In #1535, we have a new function VRMUtils.combineSkeletons
that took the place of the existing VRMUtils.removeUnnecessaryJoints
. VRMUtils.combineSkeletons
is much more performant than VRMUtils.removeUnnecessaryJoints
.
Using VRMUtils.removeUnnecessaryJoints
is now deprecated and will produce a warning in the console. The function will be removed in the next major release.
I believe you can safely replace VRMUtils.removeUnnecessaryJoints
with VRMUtils.combineSkeletons
without any errors or performance degradation.
If you have any issues, please let us know.
- VRMUtils.removeUnnecessaryJoints( gltf.scene );
+ VRMUtils.combineSkeletons( gltf.scene );
β¨ New Features
π‘ Behavior Changes
- #1540: Put a deprecation warning to
VRMUtils.removeUnnecessaryJoints
πͺ Performance
- #1532:
VRMUtils.removeUnnecessaryJoints
now supports interlaved buffers (@mrxz)- Also,
VRMUtils.removeUnnecessaryVertices
is more performant
- Also,
π§Ή Chores
- #1531: Update GitHub Actions
- #1536: NodeMaterials,
.temp()
->.toVar()
.temp()
is deprecated in r170
π¦ Deps
v3.1.6
v3.1.5
v3.1.4
π‘ Behavior Changes
- #1489: Modify behavior of expressions, interaction between isBinary and override (Reported by @mattrossman)
- According to the VRM spec update: vrm-c/vrm-specification#487
v3.1.3
v3.1.2
v3.1.1
π‘ Behavior Changes
- #1449: VRMAnimation, emit a warning if the rest hips position is approximately zero
- #1462: Change VRMSpringBoneManager circular dependency error to warning
π Bugfixes
- #1473: Fix behavior of UnlitTransparentZWrite in VRM0 models
π Docs
- #1460: Fix three-vrm-animation examples
π¦ Deps
v3.1.0: SpringBone Extended Collider
This version supports VRMC_springBone_extended_collider
that adds supports of inside colliders and plane colliders to the existing spring bone system.
For end developers: You don't have to change your implementation to support the new extended collider extension. The spring bone module inside the three-vrm will automatically load the new colliders!
β¨ New features
π Docs
v3.1.0-beta.0: Extended collider beta
About VRMC_springBone_extended_collider support
This beta release supports VRMC_springBone_extended_collider
that adds supports of inside colliders and plane colliders to existing spring bones.
Note that the specVersion
of VRMC_springBone_extended_collider
must be 1.0-draft
at the moment.
For end developers: You don't have to change your implementation to support the new extended collider extension. The spring bone module inside the three-vrm will automatically load the new colliders!