Emmett Lalish

> This is very different from khr_displaymapping_pq and "the 3D Commerce usecase" where the whole purpose is to provide a 'neutral' mapping of content to the output. > > If...

> Compatibility and acceptance that defy the whole point of doing something in the first place is the hobgoblin of little minds. @sobotka I really appreciate the detail and examples...

I like the AR use-case, but this seems a little orthogonal to glTF. For instance, this extension would not apply to any actual 3D model, right? Since the UV coordinates...

Okay, but you still haven't answered my second question: how is this extension better or different than using a quad?

> I guess you are saying as a convention, if there is just a quad in the file, we can infer that this means it is its physical size? I...

> A fourth solution could be to put this information in a container type of file (manifest) that 'ties together' for instance multiple glTFs and additional data files (such as...

@jstone-lucasfilm So, the idea is that glTF specifies physically what the materials represent, and then implementations are free to approximate them to their choosing. Therefore energy conservation is required for...

I'd love to know more about what's going on here. Are you referring to merging nearby verts to e.g. make an STL manifold? Like most things, the simple cases are...

Yeah, this is why triangle soup like STL is such a problem - it's basically impossible to reliably retain manifoldness in general cases. This is why I helped develop the...

Fantastic, keep those bug reports coming! And certainly let me know if have any comments on the API.