@pixiv/three-vrm 3.0.0-beta.1 → 3.0.0-beta.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -34,8 +34,8 @@ Code like this:
34
34
  <script type="importmap">
35
35
  {
36
36
  "imports": {
37
- "three": "https://cdn.jsdelivr.net/npm/three@0.164.1/build/three.module.js",
38
- "three/addons/": "https://cdn.jsdelivr.net/npm/three@0.164.1/examples/jsm/",
37
+ "three": "https://cdn.jsdelivr.net/npm/three@0.167.0/build/three.module.js",
38
+ "three/addons/": "https://cdn.jsdelivr.net/npm/three@0.167.0/examples/jsm/",
39
39
  "@pixiv/three-vrm": "three-vrm.module.js"
40
40
  }
41
41
  }
@@ -133,7 +133,7 @@ loader.load(
133
133
  Starting from v3, we provide [WebGPURenderer](https://github.com/mrdoob/three.js/blob/master/examples/jsm/renderers/webgpu/WebGPURenderer.js) compatibility.
134
134
  To use three-vrm with WebGPURenderer, specify the WebGPU-compatible `MToonNodeMaterial` for the `materialType` option of `MToonMaterialLoaderPlugin`.
135
135
 
136
- `MToonNodeMaterial` only supports Three.js r161 or later.
136
+ `MToonNodeMaterial` only supports Three.js r167 or later.
137
137
  The NodeMaterial system of Three.js is still under development, so we may break compatibility with older versions of Three.js more frequently than other parts of three-vrm.
138
138
 
139
139
  ```js