/3/ - 3DCG

>>576845
look at the Steam Greenlight issue and tell me you can't see why this is a thing. It's a very real market full of phenomenal idiots looking to make a quick buck by buying utter garbage.

>>576755
I've barely started the texturing, so things are kind of a mess.
Also, Quixel uses masks to handle texture layering. I'd be surprised you'd be texturing without masks if you'd ask that question.

trying to do most of my mask work by hand rather than let Quixel do it all this time. not sure I'm 100% on the results but it's getting there.

>>576446
Ah, nothing like that. it was an issue of it not liking that my low-poly was in fbx format. I exported it to obj and used that instead and everything was smooth sailing.

using Substance did the trick, though it did act a little funny. trying to figure out why it baked part of the normalmap wrong, but it's probably nothing that can't be fixed

I'll give that a shot when I get home from work then, thanks!

well, wait, I suppose Xnormal doesn't understand IDs, does it? It often makes a huge fuss about fbx files with lots of objects. I guess I could just start doing bakes in Substance if it's really that much of a difference.

>>576339
So i just need to make sure sectioned parts are named in the fbx and it'll handle it? That shouldn't be difficult to do if that's the case.

>>576338
it's not a padding issue, more an issue that comes up on overlapping/intersecting high poly geometry. my padding is at 40 for this, so seams on UV hulls look fine.

for reference, here's the same thing with the colormap and AO applied. while it looks better, it's still kinda ugly looking in those areas.

A thought occured to me while working: is there a sane way to avoid awful pixelation when baking multiple layered objects? I know IN GENERAL these things aren't super noticeable after texturing but it still consistently bothers me how UGLY it looks.