Releases: pixiv/three-vrm
Releases Β· pixiv/three-vrm
v0.6.0
π¨ BREAKING CHANGES π¨
master
branch is renamed torelease
- If you are a developer of @pixiv/three-vrm, you should do this:
git branch -m master release git fetch origin git branch -u origin/release release
- #588:
VRMRendererFirstPersonFlags
: The public membermesh
is replaced byprimitives
, which isGLTFPrimitive[]
instead ofGLTFMesh
. - #527:
.module.js
builds are now ESM
π Bugfixes
- #588: Fix handling of gltf meshes with children
- A single glTF node can have both mesh and children and it causes issues to first person, blend shape, and materials. This PR fixes this.
- #589: Add a missing line to MToon Shader
- MToon rendering was slightly wrong without this change
- #594:
keywordMap
ofmaterialProperties
is now okay to be null- Now interprets VRMs exported from UniVRM-0.63.1 properly
- #609: Texture transform was opposite from UniVRM's
π§Ή Chores
- #527: It's now bundled using rollup instead of webpack
.module.js
builds are now ESM
- 794af2a: Update copyright year
- ec46a06: Preparing renaming the branch
master
->release
π¦ Deps
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
π¨ BREAKING CHANGES π¨
- #507:
VRMHumanoid
, Greatly changed the behavior ofgetPose
/setPose
- It now explicitly receives / returns local, relative transforms that is described in
VRMPose
restPose
is now explicitly NOT compatible withgetPose
/setPose
- It now explicitly receives / returns local, relative transforms that is described in
β¨ New Features
- #507:
VRMHumanoid
, New method: resetPose- It just resets the pose to its initial pose (that should be T stance)
- It's actually identical to
setPose({})
π‘ Behavior Changes
- #507: Greatly changed the behavior of
getPose
/setPose
- It now explicitly receives / returns local, relative transforms that is described in
VRMPose
restPose
is now explicitly NOT compatible withgetPose
/setPose
- It now explicitly receives / returns local, relative transforms that is described in