Bernard Kwok

House cleaning update: I have migrated my personal branch found in this [PR](https://github.com/kwokcb/MaterialX/pull/16) to the Khronos fork [here](https://github.com/KhronosGroup/MaterialX/tree/gltf_materialx_interop). @jstone-lucasfilm, I have some fixes for the geometry loader to migrate back...

Based on specification discussion, the h/w logic should be updated to follow this heuristic: ``` hint (string): A hint to help code generators understand how input may be used. The...

Think dreams should be sent to @dbsmythe -- and best to raise this as a new "tangential" issue :) The point about optimization based on "hint" is interesting but is...

Hi Christopher, I think you're running into an issue that has been fixed with this check-in https://github.com/materialx/MaterialX/pull/807

@ix-dcourtois , @niklasharrysson PR for review. Thanks. Note: @jstone-lucasfilm this is a proposed addition as a result of Slack discussion on being able to track application inputs used such as...

Hey @niklasharrysson , Thanks for looking this over -- there was no rush. @ix-dcourtois, let me know if you have anything to add to this as you looked at this...

Hi @ix-dcourtois. Again no problems. I just wanted to do a sanity check. ( @jstone-lucasfilm, I leave the final review up to you :). ) Thanks.

A patch identifier was considered before so maybe something like this could work (?): 1. If there is any non-backwards compatible change or a data representation change then the patch...

@jstone-lucasfilm, @ix-dcourtois I didn't read carefully enough that your looking for the lowest level for pushing out "non-breaking" changes. Perhaps I'm thinking more of file-format bumps where everything breaking must...

Hi @solid-angle (Steve), `ImageSamplingProperties` should be parsing the resulting inputs after code generation and does not perform any evaluation logic so it should not be the root cause. From your...