Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSFT_lod: Clarify the behavior of the case where node level and material level LODs are specified #1952

Open
takahirox opened this issue Mar 16, 2021 · 1 comment

Comments

@takahirox
Copy link
Contributor

takahirox commented Mar 16, 2021

From Khronos Slack

The expected behavior of a case where both node level and material level LODs are specified is a bit unclear in MSFT_lod extension spec.

https://github.com/KhronosGroup/glTF/tree/master/extensions/2.0/Vendor/MSFT_lod

If both node level and material level LODs are specified then the material level LODs only apply to the specific node LOD that they were defined for.

I would like to suggest to clarify the behavior especially it would be good if the spec explains with example.

And, do we really need a capability that the both are specified? In general lower LOD nodes have references to lower quality meshes and lower quality meshes can refer to lower quality materials. In this case, material LOD specification may not be needed because node LOD can cover it.

@takahirox takahirox changed the title MSFT_lod: Clarify the behavior if both node level and material level LODs are specified MSFT_lod: Clarify the behavior of the case where node level and material level LODs are specified Mar 16, 2021
@bghgary
Copy link
Contributor

bghgary commented Mar 17, 2021

@najadojo What happens for glTF-Toolkit and Windows Mixed Reality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants