One image. Two sampling policies.
Three.js separates source data from texture configuration. Two texture owners can share one source while keeping their own wrapping, filtering, and UV policy—and the JSON image table can preserve that relationship.
- source ownership
- —
- texture UUIDs
- —
- versions
- —
- sampler policy
- —
- JSON tables
- —
- backend
- —
- frames
- 0
- timing
- NOT RUN
Two texture wrappers should point at one Source while the fork owns another.
Source bytes and upload version are separate from each texture's sampler policy.
Texture records should reference one shared image record.
All texture owners, materials, geometry, controls, and renderer are application-owned.
READYNo probes yet.
The third preview is a forked source. It keeps the same initial bytes,
but shared-source updates should change only the first two previews.
Current-dev TextureSource behavior is source-reviewed, not
executed through the pinned package.
Sources: Source · Texture · DataTexture · TextureNode · ObjectLoader · texture filtering example