I think if Quixel could give us all the json’s from the assets when they came from Quixel (not Fab), it would make it much easier for us to get our assets from Fab to work with Bridge’s workflow efficiencies. The json’s are big files, so a folder containing all of them wouldn’t be too big.
If I understand it correctly, the json contains information used to export the asset to the program of our choice (for me it’s 3ds Max). The json’s from Fab are formatted differently than they were from Quixel.
Any thoughts on this Quixel team?
@Frank.Gehry you’re absolutely right about how the json works.
Curious to know why do you need the json for Quixel assets as you should be able to use the export feature in for any assets in your Purchased/Acquired tab on Quixel Bridge?
To answer your question, we don’t plan on distributing the json files but are actively exploring ways to support the export functionality for assets on Fab.
I believe having the ‘old’ json’s would allow for elements downloaded from Fab to be recognized by Bridge and exported like they were before Fab came along. My assets downloaded before Fab export from Bridge no problem, but newer assets from Fab aren’t recognized by Bridge. All I would need to do is change the naming and folder structure to whatever Bridge and the json expect it to be. It would still be so so so much easier than doing everything manually.