So does that mean we cannot get to the megascans material blender?
Hello @KomalOffice,
first of all the standard download button still doesn’t work for me even after I just updated it to version 2025.0. Only the download button in the thumbnail works and once downloaded I can luckily export to 3DsMax (Vray) as usual. I don’t know why that download button is broken but it looks like reinstalling Bridge or updating it doesn’t fix it.
As for my account type. I’ve had my account for a very long time. I was never a subscriber but I paid a lot of money to buy many points for assets. When the switch to FAB was announced I successfully converted my 2000+ remaining points to the FAB wallet. Since then it says that my Bridge account has 10 points left but I do see 18k+ assets listed as purchased because I claimed them. Sadly though when I visit the FAB page and click on My Library only a small number of assets is listed. Which is strange because when I find any of the claimed assets in FAB it says that it’s in my library already.
I just looked at the road map you linked to. I don’t see that feature on there yet but we desperately need the same ability to easily export assets right into our 3D app such as 3DsMax (+Vray setup), Cinemda4d etc. This was/is the no.1 killer feature that people like me need in an asset client. Overall the Vray materials that Bridge automatically sets up for textures and even assets is superb and a huge time saver. Having this very same feature in FAB will be VERY important (alongside with the ability to select the LOD).
Furhermore I see that there will be the ability to search for Quixel IDs. That in itself is really helpful but once Bridge stops working entirely we won’t even be able to browse the quixel library comfortably to find that ID. Ideally we need a simple filter we can use for all Quixel related assets that we claimed without having to browse in a dying app to find it by hand in the new one.
I have been a long term fan of Bridge and Quixel/Megascans. As a generalist 3D artist it has been super useful tool for which I was willing to invest a good amount of money. As things stand now I feel like that investment is at risk because the assets or more so the way to comfortably browse and import them effectively is being taken away. Don’t get me wrong I very much appreciate that we were able to claim that many assets for free but the real beauty of Bridge is HOW we can find and use what we actually need.
1 Like
@amass3d Thank you for taking the time to share detailed feedback and for being a long-time supporter of Quixel Bridge. We hear you!
Download issue
The download button not working in the right panel on Quixel Bridge is a known bug and added to our list of fixes. Sorry about the inconvenience.
Assets not appearing in Fab library
If you clicked on Claim All on Fab, you should see a Browse Quixel Megascans card in your Fab library. Clicking on this will take you the Quixel profile on Fab from where you can access all of your claimed assets. You’re right that assets don’t appear in the Fab library currently, which we’re aware of.
Asset export feature
We completely understand how critical the direct export feature is to your workflow. Streamlined asset exports and material setups is something our team is actively considering for FAB. The ability to select LODs though is not currently on the list. Instead of LODs and texture resolutions, Megascans on Fab now feature quality tiers that target specific hardware limitations (read here).
Search for Quixel IDs
If you’re using the Quixel ID to make sure that the asset that you’ve claimed on Quixel is also claimed on Fab, there are a few things you can keep in mind to put you at ease:
- If you clicked on Claim All on Quixel, but didn’t click on Claim All on Fab we do plan to grant you access to those Megascans on Fab.
- If you’ve claimed all on Fab, then you have nothing to worry about already.
However,
- Some assets on Quixel will not be coming over to Fab. These have been deprecated.
- Some assets on Quixel have not yet made it to Fab, but we do plan on bringing them over in the coming months.
Let me know if there are other reasons that you’re using the Quixel IDs for.
Good to hear the Download button not working in Bridge is a known issue.
As workaround, is there a quick way to import downloaded Fab megasacans assets to Bridge? Currently manually editing the json file of each asset so it shows in bridge (after extracting to the appropriate location in Bridge’s downloads folder), which is not ideal!
What are you editing in the json in order for Bridge to recognize the asset?
@RichardI46 there isn’t any officially supported workflow or feature for importing Megascans downloaded from Fab into Bridge.
Is there a method where you could get Bridge to recognize assets downloaded from Fab? It seems like the files are the same, but the folders and naming is slightly different.
If possible, could we get a folder that contains all of the json files from the old Quixel assets? That would make it easier to get Fab assets to work in Bridge.