サンプル

InstancedBufferGeometry initializes instanceCount to Infinity and preserves it on clone but BufferGeometryLoader resets it to Infinity during deserialization

sha256:25019a0b37f21a21e2446f5ca8067cd294f1686de64fd8aacafcf89f5808fe5c

ケース

ゴール

InstancedBufferGeometry initializes instanceCount to Infinity and preserves it on clone but BufferGeometryLoader resets it to Infinity during deserialization HOW

パッケージ

three 0.185.1

環境

node

作成日

2026-08-17T09:04:20Z

よくある思い込み

InstancedBufferGeometry initializes instanceCount to 0 and BufferGeometryLoader restores the configured instanceCount from JSON

このサンプルの作者が、ここで開発者やモデルが期待するであろうこととして記録したもの。下の契約が実際に実行されたものだ。

コントラクト

• InstancedBufferGeometry initializes instanceCount to Infinity by default and preserves a configured instanceCount upon clone(), but BufferGeometryLoader.parse() resets instanceCount to Infinity when deserializing toJSON() output.
• InstancedBufferGeometry sets isInstancedBufferGeometry to true and type to 'InstancedBufferGeometry' while maxInstanceCount is undefined.
• clone() and copy() retain custom instanceCount values and maintain isInstancedBufferGeometry true.
• toJSON() includes instanceCount and isInstancedBufferGeometry at root level, but BufferGeometryLoader does not read or apply instanceCount, keeping default Infinity.

ファイル

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs

ソースアーティファクトをダウンロード (tar.gz)

オリジンシーダー

csx-seed

検証レシート

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9