Sometimes the object name in the MCX list of friendly names with GUIDs is actually descriptive enough to give us a clue about an object to warrant clicking on it so we can 'jump' to it, and have it display in 3D preview ...without advancing forward using the arrows (which is what I am in the bad habit of doing).
Other times 3D object names are too obscure or abbreviated into an arbitrary spelling, but we might get additional clues from the original mapped texture Material names.
I wonder if there might be a way when a 3D model library BGL is loaded, to first only extract a report with GUID following friendly object name, and an option to display a subsequent list of mapped texture Materials in a drop-down 'sub-report' dialog (...and all of such report elements can optionally be saved to disk).
Perhaps the 3D model library report dialog might also have a search feature to look for specific object or texture Material names, and to save a report and/or index out to disk.
I was recently looking at MSFS 3D object visual guide pictorial PDFs by flyboyrez1 at
flightsim.to in order to familiarize myself with some more of MSFS' objects, and as good as they were, I wished there was a quicker way to access that info differently before seeking out a visual preview of objects.
Perhaps the MCX feature under consideration here might evolve into a way to "query" such BGLs and create offline indexes / databases for ease of use ?
[
EDITED]
If MCX' report form pre-indexes that BGL's 3D model object friendly names, GUIDs, texture names, can MCX 'quick-fill' the query field with
existing strings ?
For Example, MCX tentatively 'quick-fills' submissions the query input field 'could' use ...with indexed strings actually within a BGL, as we type:
GUID 1st section of 8-characters, Hangar, Light, Beacon, Brick, Rock, Stone, Boulder, Cement, Concrete, Wood, Pier, Dock, Marina, Boat, Truck, Car, Fuel.
If a MCX query field tentative 'quick-fill' submission is what we want, we press <enter> or click to 'tag' that object and add it to a group for processing.
And, of course, it would be a bonus if the on-disk output of MCX BGL 'pre-scans' could be used as indexes for general queries looking for specific objects without actually re-loading the original BGLS.
MCX could be used to pre-index BGLs in folders and/or entire folder chains, include the BGL file name in its index info, and we could do meta-searches for objects when looking for specific 3D models by GUID, friendly name, texture Material name etc. by using MCX as our quintessential 3D model info manager.
Could this inspire a MCX Pro payware ? ;-)
[
END_EDIT]
GaryGB