The repository KhronosGroup/glTF-Generator-Repository hosts a registry.json file containing a list of tools that author glTF files. The list hasn't really been updated since 2018 and is likely out of date compared to this repository. One useful thing it does include, not present here, is a repository of asset.generator strings allowing tools to take a given glTF asset, identify the tool that produced it, and find the documentation and bug report URLs (if available) for that tool. My viewer (https://gltf-viewer.donmccurdy.com/) uses this data to tell users where to report issues, when possible.
Since we probably don't want to be maintaining — or asking the community to maintain — two separate lists, perhaps it's worth adding generator strings and similar fields to the JSON records in this repository, and archiving the glTF-Generator-Registry repository?
The repository KhronosGroup/glTF-Generator-Repository hosts a
registry.jsonfile containing a list of tools that author glTF files. The list hasn't really been updated since 2018 and is likely out of date compared to this repository. One useful thing it does include, not present here, is a repository ofasset.generatorstrings allowing tools to take a given glTF asset, identify the tool that produced it, and find the documentation and bug report URLs (if available) for that tool. My viewer (https://gltf-viewer.donmccurdy.com/) uses this data to tell users where to report issues, when possible.Since we probably don't want to be maintaining — or asking the community to maintain — two separate lists, perhaps it's worth adding
generatorstrings and similar fields to the JSON records in this repository, and archiving the glTF-Generator-Registry repository?