I've been using Quixel Suite with no problem....until now. It's in beta, so I understand. I was hoping maybe someone else has run into this problem and figured out how to fix it. I am currently building pieces for my map I'm trying to build for my portfolio and the last piece has to cause an issue.
This is what it looks like for my color map and when it asks me to define the colors. I only have four that I need to use. The black is the background of the image, I ignore that one.
After I load the maps I need and start the project, this happens with the one area, no matter the color I change it to through 3ds Max.
I thought it was an error with a mask, changed it, not the problem. Tried adding materials in hopes it was a glitch and it'll fix itself. I'm at a loss for right now. I'm posting now and gonna reboot my PC, maybe that'll do the trick. If not, ideas?
I've re-exported the mesh, normal and AO maps, anything I can think of that might be causing the issue. Nothing so far.
Replies
The colour IDs layer needs to be absolutely precise because it separates the material layers out based on specific colour value of each pixel. If some pixels are out by even a little, as they would become due to artefacts, Quixel will probably no longer detect them as being the same material, which is why you're getting such strange, messy outlines. Save the colour IDs as PNGs or TGAs.
All your other maps will be okay to save with lossy compression (though it's not recommended, since the effects of compression are cumulative and the more you use JPG and such, the higher the likelihood stuff will get recompressed over and over and deteriorate over time - best practice tends to be to use TGAs or PNGs for everything and only do DXT compression for your textures in the end, when you package them into the game, keeping those separate from your source files).
Unfortunately, there isn't a swatch file for the SUITE yet.