Search

1. Re: Answered: Unity Export - Metallic, Legacy not including correct textures

   

   Reply by Belome · Sep 2018 · Home› Quixel Megascans

   Thanks! That new script compiles correctly. But when importing from Bridge with this script, the importer now links the Masks texture to the AO input, but the Masks texture does not have the proper AO data like the actual AO texture. Anyways, if this is hard to fix, I can just add the AO textures myself, since I was doing…

2. Re: Answered: Unity Export - Metallic, Legacy not including correct textures

   

   Reply by Belome · Sep 2018 · Home› Quixel Megascans

   Thanks so much for your help! When I download that script, it seems to be incomplete and cuts off at: for (int j = 0; j < g.transform.childCount; ++j) { Renderer[] r = new Renderer[1]; r[0] = g.transform.GetChild(j)....

3. Re: Answered: Unity Export - Metallic, Legacy not including correct textures

   

   Reply by Synaesthesia · Oct 2018 · Home› Quixel Megascans

   I just heard back from our Unity dev: The importer links the Masks texture to the AO input because AO is packed inside the Masks texture. In regards to NormalBump maps, we're looking into that. It appears that the script (and Unity itself) should be using the Normal LOD textures instead.

4. Re: Answered: Unity Export - Metallic, Legacy not including correct textures

   

   Reply by Synaesthesia · Sep 2018 · Home› Quixel Megascans

   http://www.filedropper.com/megascansimporter Try this file - our Unity dev just wrote it up for you as a fix for this issue. "Now the user needs to go to Assets>Quixel>Scripts>BridgeImporter> and delete the MegascansImporter.cs file and copy this one into that folder.What is it doing?Well it is essentially checking if it…