UV transforms not implemented per-texture
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/mrdoob/three.js/issues/9457. Texture offset/repeat/scale are located in threejs as properties on the texture object, but all textures using UV1 share the same transform - so it’s really like the repeat affects the whole material. Textures using UV2 (AO, lightmap) cannot be transformed at all. Until that is fixed in threejs we should consider deprecating all of the texture transform options except for the ‘map’ base color texture.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked three.js issue 9457 and tracing how texture offset, repeat, and scale are handled for UV1 and UV2. Clarify whether the work belongs in A-Frame or upstream, and define done as a documented decision on per-texture transforms or which transform options should be deprecated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- ar-vr-xr
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100