Closed vis-prime closed 1 year ago
The warning comes from https://github.com/KhronosGroup/glTF-Validator. The issue here is that the aoMap says it needs the second UV set, while the file only contains one UV set. Viewers might happen to handle that fine, but it's technically invalid, and could break elsewhere.
One fix might be to assign aoMap.channel = 0
before exporting from three.js. I'm surprised three.js works without that actually, now that three.js supports arbitrary UV set assignments.
Related fix in r152 –
aoMap.channel = 0
is the default value right?
That's the default for a new texture, yes. If you're loading a new model from a file the loader might change it.
Getting this aoMap/uv related validator error
from a glb created with r153 and the mesh with the occlusion texture is invisible in the viewer
the gltf is still valid right? it work's on https://github.khronos.org/glTF-Sample-Viewer-Release/