It’s actually hard to talk about the maps without not referring to how they are used in rendering. And I think that’s why “bump” is no longer used as it makes things a bit ambiguous.
Bump mapping (as used by rendering engine) was an old technique for normal mapping (using just 1 8bit channel). I don’t remember now the exact computational algorithms, but it was called Blinn algorithm IIRC. The rough idea was that you actually tried to calculate a normal map just with height information. I remember implementing this algorithm in c++ while doing my msc in CS (and in my “previous” life I did have an episode that I taught entry level computer graphics at local Uni for CS students).
And to make things more confusing to Kartik I’ve used all kinds of maps in shaders to do things they weren’t intended to be used for. I even remember that I used base color map to drive displacement or roughness (after doing some transformation on them).
phew, all of that, went over my head, I really don’t understand any of those right now, basically confused with what each does. I should give more time to this topic. Thanks @Jaco_Pretorius for the that explanation about the difference, and @bOBaN for the links.
Popping up one more:
Making a gold material, the part I know is I have to make it 100% “metallic”, less “Roughness”, and a lil bit of “clearcoat”.
The part I don’t get is, what are “specular” and “sheen” doing?
Yes, the first link explains materials, the second - workflow. And textures and materials are kind of bound together (you make textures to feed into your materials).
It seems that it’s not crashing, but it just has terrible UI bug. When doing some heavy calculations in the background - it freezes the engine for a few minutes (5-10) and then works. Workaround: adjust all stuff with small texture size, and for final shot crank up their resolution. 1k resolution for working seems to have acceptable delays, but I’ll use 512x512 just in case (as I bet that the more I learn designer the more complex they will get).
Edit: another workaround:
Export textures directly to project folder somewhere and while exporting mark it as ‘auto update’ (even 4k is ok)
Setup material in unreal manually
Adjust parameters directly in designer
Strange that going through filesystem is quicker than using official plugin.
Ugh… finished brick material. Started with some old tutorial, which kind of worked, but didn’t produce great results. Tried to tweak it myself… The result is not bad, but somehow I don’t like it…
For my eye, the brickwork not being a proper bond, properly regular, hurts the eye, even before the underground public toilet glazed brick like smoothness of surface, even if the glaze is now matt.
I know it is only a test soft cube but how would the corners ever be built like that, given you can not get a proper corner even by moving the uvs or mapping sideways, because the bond pattern is not there.
If it is to be a distant effect then the surface will not matter. But the pattern might.
I also do not like the curvy ‘damage’? lines. May just be me but I can not recall ever seeing such effects, which does not mean they are not out there somewhere.
But on a more serious note, it’s not feasible in the long run (it’s not about those bricks only, but all the textures). I’m learning this with “making indie games” in mind. It will not be possible for me to spent couple of hours on each brick wall… and even if I had a team of artist at my disposal that doesn’t really scale. No wonder why 95% of game studios use substance (adobe’s claim, I have no data to back it up - but I don’t even recall a gdc talk about the art side of a game that substance wasn’t mentioned).
Edit: maybe with geometry nodes or houdini one could make workflow for bricks better
I will hide it Putting some columns or wooden beams or something. Real life bricks have similar problem
But that actually gave me idea for further work… First look at maps from scanned data, then try to replicate it as well. You know - having in the reference not only pictures of a surface I’m trying to replicate it, but also maps created while scanning similar surfaces (e.g., from megascans).