Adam Morris

@lilleyse Yeah, my plan at the moment is to use an API schema. I want to lock it down to only Xforms and I need to figure out how to...

@lexaknyazev How do you envision us representing this data point in the Project Explorer? I think there's a lot of value in indicating if a loader can support loading large...

In January 2025, during the [Metaverse Standards Forum Town Hall](https://youtu.be/0xdPpKSkO3I?feature=shared), the community expressed positive interest in standardizing, compressing, and optimizing Gaussian Splats, with direct interest from Niantic to integrate SPZ...

@keyboardspecialist, @lilleyse, and I have been brainstorming what bringing SPZ into glTF may look like. Using the Draco extension for inspiration, we think that it should be straightforward to make...

A little earlier today I opened https://github.com/KhronosGroup/glTF/pull/2490 containing draft proposal for an extension we are calling `KHR_spz_gaussian_splats_compression`. This is the extension my colleagues @keyboardspecialist and @RenaudKeriven have talked about in...

Thank you for sharing that paper @JMLX42. Definitely worth mentioning. I took a brief look at the prepub, and it seems to have a similar issue to some other methods...

Thanks, @javagl. Our currently opened PR https://github.com/KhronosGroup/glTF/pull/2490 is the most recent proposed extension for handling compressed 3D Gaussian splats in within glTF. The `KHR_gaussian_splatting` extension is our original take at...

> Is it necessary to specify a version or other unique identifier to ensure that the desired algorithm and calling sequence is used? Good question. The SPZ library packs along...

This is an excellent point, @javagl. As of this moment, the SPZ library's `loadSpz` function returns a `GaussianCloud` type which does not contain the version information, but that information could...

> The [accessors](https://github.com/CesiumGS/glTF/tree/draft-spz-splat-compression/extensions/2.0/Khronos/KHR_spz_gaussian_splats_compression#accessors) section currently says that the position accessor should contain max: [1, 1, 1], min: [-1, -1, -1 ] I don't think our intention was to state that...