Pär Winzell

Hey all, just starting to take a closer look at this very interesting project. Came across this issue and wanted to drop in a comment on the fundamental usefulness of...

Likely naive question: If this feature is implemented as suggested above, would it be reasonably easy for a user to fish out (hypothetical example) `root.others["KHR_texture_transform"]` and, if non-empty, perform a...

This is one of two plausible ways we brainstormed to provide information sufficient to reconstruct a quad / ngon tessellation from a vanilla-compatible triangulation. The virtue of this proposal is...

Indeed; I described the limitation in this PR as "It's obvious that this can be done for convex polygons, e.g. quads, but the true constraint is a bit less strict."...

To reiterate with further clarity: we (FB) consider this extension worthwhile mostly as a formalisation of our own internal client/server asset markup. These models are not intended to leak into...

> What's preventing this quad support from becoming an accepted extension exactly? Yeah, at this point I'd propose the PR be merged as-is, a vendor extension. Its limitations are spelled...

I hadn't understood about corner/crease sharpness before. We could also skip this extension entirely, **if we have something else more or less ready to go**. I just worry that we're...

Apologies for the delay; I hope to make the changes shortly. I quite agree with Don's general summary. Let's make certain there's no confusion – merging this vendor extension does...

@xissburg My sense is that there's too many use cases, too different from one another, for easy agreement to emerge on a simple extension... and banging out a more sophisticated...

Wow. I can't decide if I should fear or long for the day when @lexaknyazev does code review on anything I wrote. 🥇