This topic has already been touched upon ([1](https://forum.corona-renderer.com/ Quixel Briged #msg187933), [2](https://forum.corona-renderer.com/ Quixel Megascan #msg182604)), but it seems nothing has changed.
In Cinema 4D Quixel Bridge supports other render engines, but not Corona.
I do not know who should take the first step to integrate, you or Quixel, but it would be nice if this disadvantage was solved 
+1 for this please.
+1
+1
Hi, I was wondering if anyone has tried this texture manager from Great Summit and if its a good solution for the time being as Quixel doesn’t work with Corona render. Also does it work with Corona 7?
Hello,
as far as I know, this is not supported at the moment. I’ve added this as a feature request and we’ll discuss it with the team.
Thanks,
Jan
+1
It works fine with my C4D S24 and Corona 7 Hotfix 2 but it is a rather simple material manager which can assign standard maps (with appropriate naming) well enough but has difficulties with metal materials and complex settings. In those cases it cannot generate a proper preview for example.
As you cannot tweak material setting in the TGS material manager you have to touch all settings in the corona material created from the maps. TGS always uses standard bump and IOR-values for the material creation, so those values often do not correspond to the right material settings.
To sum up: it helps to quickly assign maps to the right/standard texture slots of basic Corona materials but it is far from offering a complete PBR-solution for C4D.
I am waiting for the Connector (Design Connected) to offer a better PBR-solution but DC-support told me, that this is a project they plan for 2022.
Thanks for the info. Sounds like its not quite what I’m after as I was hoping it works with the new physical material. The Design Connected one sounds interesting, I’ll check that out. Thanks.
Sorry, no it does not create physical materials but only standard/legacy materials with the maps assigned to the texture slots of those materials. Hopefully TGS offers an update for those physical materials and more complex settings soon.
Any news about that? =)
It wpuld already be better if Bridge would just export C4D standard materials when in C4D Coronarender is set as renderer. Now I have to switch back and forth to standard and corona whenever I export megascans to C4D. If C4D is set as corona the export from Bridge fails
Hello,
not at the moment, we are fully focusing on v8 features and bugfixes. This will probably be shifted to a later release.
Thanks,
Jan
What a disappointment… Another year waiting then?
Just started using Corona, but I was very surprised to see that it does not support Quixel Bridge like other renderers. This would be such a useful feature to implement.
+1. Megascans are almost ubiquitous these days.
+1
+1
up
Thanks for the request, we have it logged.
(Internal ID=890771003)
+++++++++++++1
Few month ago i ask them. No Plan for corona support.
The boring thing is Corona Render profil active does not import from bridge. We must change to Standart
Aberation