You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node: 0 has the references to node: 1 and node: 2 as LODs and node: 1 has the references to node: 3 and node: 4 as LODs. How should the LODs for node: 0 be?
Probably allowing the recursive LODs makes the engines complex so we may have two options.
glTF data including recursive LOD is invalid.
The engines should apply the top-level LOD specification and ignore the recursive LOD specifications.
Perhaps 2. is good? In the example below, processing node: 0 will ignore the LOD specification in node: 1 so node: 0 will be High-Middle-Low LODs. And processing node: 1 will apply the LOD specification in node: 1 so node: 1 will be Middle-Low LODs.
https://github.com/KhronosGroup/glTF/tree/master/extensions/2.0/Vendor/MSFT_lod
In
MSFT_lod
spec, it's unclear whether recursive LODs are allowed or not. For examplenode: 0
has the references tonode: 1
andnode: 2
as LODs andnode: 1
has the references tonode: 3
andnode: 4
as LODs. How should the LODs fornode: 0
be?Probably allowing the recursive LODs makes the engines complex so we may have two options.
Perhaps 2. is good? In the example below, processing
node: 0
will ignore the LOD specification innode: 1
sonode: 0
will be High-Middle-Low LODs. And processingnode: 1
will apply the LOD specification innode: 1
sonode: 1
will be Middle-Low LODs.The text was updated successfully, but these errors were encountered: