Marco Hutter

Only a note: There are currently containment checks for geometry in bounding regions as part of https://github.com/CesiumGS/3d-tiles-validator/pull/347 . These generate a `BOUNDING_VOLUMES_INCONSISTENT`. (There is no better issue type for now)....

As part of https://github.com/CesiumGS/3d-tiles-validator/pull/347 and related PRs, a functionality was added for validating that certain points are contained in a bounding region. The cases of `box` and `sphere` are not...

One specific difference between 1.0 and 1.1 that affects the validator: - in version 1.0, the `tile.children` was allowed to be an empty array - in version 1.1, the `tile.children`...

As an addendum, related to https://github.com/CesiumGS/3d-tiles-validator/issues/260 : (EDIT: What _originally_ was written here did not make sense, because it referred to a case that was disallowed by the specification. But...

@lexaknyazev When things affect the core spec, then I'd hesitate to just review/merge anything without your approval (a similar case as in https://github.com/KhronosGroup/glTF/pull/2351 ). If you say that things like...

@lexaknyazev If you agree that things like - `this` - https://github.com/KhronosGroup/glTF/pull/2351 - https://github.com/KhronosGroup/glTF/pull/2246 can be merged at any point in time and by others than you, then this could help...

The task to open an issue was still on my TODO list (as of [a comment in the linked PR](https://github.com/CesiumGS/cesium/pull/12119#issuecomment-2363832337)). So this is done now 🙂 The PR contains some...

There is an [appendix in an (archived!) extension](https://github.com/KhronosGroup/glTF/tree/main/extensions/2.0/Archived/KHR_materials_pbrSpecularGlossiness#appendix) that might be helpful. It points to some utility functions that are supposed to do this conversion. (I won't be able to...

> Matrices other than 4x4 are trivially possible but adding them in advance would further increase required test/sample coverage so we'd like to have specific usecases first. Same with integer...

Is there a (reasonably up-to-date) machine-processable representation of this? (I.e. something like a schema or a "repository" of node structure descriptions)?