Suggestion: auto uv2
See original GitHub issueDescription of the problem
If I’m right, aoMap
and lightMap
require uv2
and users need to be aware of that and manually define it unless model has built-in uv2
.
So, I’m wondering if it’d be useful that Three.js (WebGLRenderer
?) automatically detects non-defined uv2
and uses uv
as uv2
(or copies uv
to uv2
).
What do you folks think?
Three.js version
- Dev
- r85
- …
Browser
- All of them
- Chrome
- Firefox
- Internet Explorer
OS
- All of them
- Windows
- macOS
- Linux
- Android
- iOS
Hardware Requirements (graphics card, VR Device, …)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Copy UV1 to UV2 - Feature Requests - ProCore Forum
Not exactly a request, but a suggestion to deal with the auto uv ... the the UV1 pane that copies what you've done...
Read more >FTTS Utility Vehicle UV2 Concept Review - DTIC
FTTS UV2 Support Variant ... including suggestions for reducing this burden, to Washington ... FTTS UTILITY VEHICLE UV2 CONCEPT REVIEW.
Read more >Why do AO and LightMap need a second set of UVs?
Issue: Suggestion: auto uv2. opened by takahirox on 2017-07-03. Description of the problem If I'm right, aoMap and lightMap require uv2 and users...
Read more >UmorAiro Gift for Women UV2 Hand Held Vacuum Cordless, 2 ...
This cordless car vacuum cleaner can also clean spilled coffee or milk, a real wet and dry use.
Read more >Important information regarding Mesh UV channels
It's just that the mesh property names are uv, uv2, uv3 & uv4, ... this property will be converted by the API auto...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I do no think we should be modifying the user’s model, but a console warning may be nice.
Also, the 2nd set of UVs do not honor offset/repeat, so silently setting UVs behind the back of the user may lead to more confusion.
At some point, I hope we will be providing additional flexibility in this regard, so this problem will go away.
We already highlight in the docs that
aoMap
andlightMap
require a second set of UVs. I think this is sufficient. Voting to close the issue.