示例

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

sha256:25019a0b37f21a21e2446f5ca8067cd294f1686de64fd8aacafcf89f5808fe5c

PUBLISHED L3_CONTRACT_PASS MIT-0

执行证据

分开显示声明环境和签名验证运行，明确样本的证明范围。

证据依据签名契约通过

验证回执1

验证级别L3_CONTRACT_PASS

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17

目标: 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.

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