GLB Batch Inspecting and Processing

Questions
1

Hello friends,

Working with a large quantity of GLB files I found that often I need some info from all files, and it is not the best thing to open each and inspect. So I decided to improve GLB batch processing as possible.
Here is quick proof-of-concept (no data export yet).

multi_scr1
multi_scr11911×946 83 KB

Questions:

  1. What kind of data from GLBs you usually need most in order to analyze it, sort and compare?
  2. Which kind of data you would need to export from a such tool?
  3. What kind of possible optimization would you expect from a such tool (result => optimized GLBs)?
2 Likes
2
  1. glTF validator tests.
  2. Prettified Tree Hierarchy of the validation results IE asset properties, number of nodes and children, size (bytes) of nodes and animations etc.
  3. Info about embedded media, textures etc.
  4. Metadata analysis: property checker/collector across assets?
  5. SHA results? Could be good to have for a few reasons.

A pretty-structured JSON report array, so we can compare using a VCS’ diff.

  1. If you propose input settings, then texture resizing, encoding and compression.
  2. Ability to strip textures/media/animations/bones.
  3. Auto LOD generation? It may be a useful starter for devs to benchmark their games/assets.
  4. Identify potential duplicate/clashing data across assets such as same filenames. Ability to detach to separate files and update references.
  5. Texture optimisation tools: combining channels?
3

@j-te beat me to it lol. Great comments, very cool project, keep going!. Will this be open source and work outside of the wordpress environment? Following.

1 Like
4

Sure, currently this is just a draft, later I’ll make it public.
There is no Wordpress there, only Typescript :slight_smile:

1 Like
5

Thanks for the comment, great list!
Hope to fulfil most from it :slight_smile:

1 Like
6

For our internal tools, we’re creating an Asset Library (GLB format will be the primary). I would be happy to help/contribute where possible, if you’re open to PRs. :slight_smile:

1 Like
7

At the moment I am implementing the latest GLTF validator. But the biggest challenge is to create good UI to work with all this data. Will publish when will be satisfied :slight_smile:

It is definitely possible. Quite simple if export several GLBs, but I don’t know how to combine there into one GLB with the MSFT_lod extension.

That would be great! I hope I’ll publish the initial version in December.

1 Like
8

Don’t let it be a big challenge, chicken and egg scenario with UI and UX. I’ll pitch-in once we’re happy with the whole scope of the tool and purpose, we can revisit the UI :slight_smile:. I’ve recently created a tool with similar intentions but it audits and generates other files (not BJS related). Paginated/responsive/large data sets with split UI.

It is sounding promising! Are we going to follow a similar code architecture as the inspector, for consistency? It would be good to have the viewer compatible plus inspector, for testing each asset.