If we pay attention to the PRs, there is this little gem (since the devs seem to be too busy just to respond with anything either)
It will probably also lead to the ability to switch these textures via script, but right now it seems to be very Autodesk heavy, would like to have indirect support for Blender (or other suites) without having to purchase an Autodesk Subscription… I say indirect, because exporting from Cycles to fbx is a no go because it is a node based pbr. Thats why they are materials usually applied to the model within Unreal or Unity instead of read from the model.
Could be even just another entity property (for the texture) that is a jsonObject file where we define the list of materials (of the mesh object) which contain pointers to textures for normals, albeto, glossyness, metallicness, ao, etc. etc.
instead of the
texture-name : texture.jpg
that it currently is there that is not seemingly doing anything.
The some of us could create plugins into blender allowing these to be exported from cycles as “hifi materials”