Releases: pixiv/three-vrm
Releases Β· pixiv/three-vrm
v0.6.5
v1.0.0-beta.2
v0.6.4...v1.0.0-beta.2
v1.0.0-beta.1...v1.0.0-beta.2
π¨ Breaking Changes (from v1.0.0-beta.1)
- #785:
VRMExpressionPreset
->VRMExpressionPresetName
β¨ New Features
- #785: Add new interfaces to
VRMExpressionManager
.presetExpressionMap
.customExpressionMap
π‘ Behavior changes
- #785:
VRMExpressionPreset
->VRMExpressionPresetName
π Bugfixes
- #785: Custom expressions was not loaded properly from VRM1.0-beta
π¦ Deps
- 379d539:
@types/three
is now0.126.2
v1.0.0-beta.1
This is the first ever release of three-vrm with VRM1.0 support.
π¨ Breaking Changes
- Notable: three-vrm is now implemented as a loader plugin instead of mere importer method.
- Three.js r126 or more is required
- usage:
const scene = new THREE.Scene(); const loader = new THREE.GLTFLoader(); // Install GLTFLoader plugin loader.register( ( parser ) => { return new THREE_VRM.VRMLoaderPlugin( parser ); } ); loader.load( // URL of the VRM you want to load '/models/three-vrm-girl.vrm', // called when the resource is loaded ( gltf ) => { // retrieve a VRM instance from gltf const vrm = gltf.userData.vrm; // add the loaded vrm to the scene scene.add( vrm.scene ); // deal with vrm features console.log( vrm ); }, // called while loading is progressing ( progress ) => console.log( 'Loading model...', 100.0 * ( progress.loaded / progress.total ), '%' ), // called when loading has errors ( error ) => console.error( error ) );
- Notable:
renderer.outputEncoding
should beTHREE.sRGBEncoding
- Notable: BlendShapeManager is renamed to ExpressionManager.
vrm.expressionManager
- There are a lot of changes based on the spec of VRM 1.0.
- Some of implementations are separated to individual packages
- You probably don't have to care about these packages since the build of
@pixiv/three-vrm
includes all of necessary dependencies.
- You probably don't have to care about these packages since the build of
v0.6.4
v0.6.3
π Bugfixes
- #649:
VRMHumanoid.resetPose
is now working properly - #650:
VRMHumanoid.getBones
now returns[]
instead ofundefined
when there are no bones bound to the specified HumanBone - #650:
VRMHumanoid.getBoneNodes
now returns[]
instead of emitting an internal error (π©) when there are no bones bound to the specified HumanBone
π» Refactors
- Trivial: #650
π§Ή Chores
- #292: Enable a eslint rule,
@typescript-eslint/no-unnecessary-type-assertion
π¦ Deps
- #657: Bump Three.js to r126
v0.6.2
v0.6.1
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