ฝัง
- เผยแพร่เมื่อ 27 ก.ย. 2024
- TF2 isn't normal, and this brick wall shows us how. 🧱
Paper on SSBump: cdn.cloudflare...
Chris Green on Twitter / X: / chrisgr93091552
▶ Everything wrong with Dustbowl: • Everything Wrong with ...
▶ Stick to walls: • [TF2] How to Stick to ...
▶ Damage through walls: • Which TF2 items can Sh...
▶ My other TF2 stuff: • TF2
▶ My TF2 shorts: • TF2 #shorts
Credits:
Bobby Parker: bobby-parker.c...
DefendTheHouse: • [4K RTX] The Beauty of...
Pluralsight: • CG101: What is a Bump ...
👉 Get 25% OFF your first server: shockbyte.com/...
▶ My Socials: linktr.ee/LEDs_YT
💬 Discord: / discord
#tf2 #teamfortress2
9:08 there's actually a single dynamic light source in TF2 (that I know of)! The Dragon's Fury fireball
The Dragon's Fury is very sexy and cool
@@vinnyandlin8510 as a spy
Yes
@cuenta007 and as a pyro it's more fun to fight spies with it. Praying and spraying till you catch one by accident is funny but like random shits after a while I just feel bad about it and also want a bit more of a challenge than holding m1 and doing some housekeeping
@@vinnyandlin8510 tf is a random shit
@@cuenta007 Random crit
"I was studying walls"
Yea that's a normal person thing to say.
LED's a mapper, though? not only are they not normal, but they logically would study maps to know how to make theirs better and to understand what's going on, no?
@@zzyxxyzz5442 its not that deep
architects disagree
"I watched a video about someone studying walls" isn't exactly a normal person thing to say, either.
@@zzyxxyzz5442 it's just a joke that plays on how it sounds out of context. it sounds like some random person fascinated by walls, which most people very much aren't and could also imply long periods of time staring at walls, which would be even more strange
So that's why TF2 walls look so good.
Wait somebody thinks tf2 IS normal?
Insane
Somehow yes
How tf explain@@DustEatingMan
@@vhammermdl built different or alien
*tf2 maps*
That's why the walls look so bumpy I wanna eat them
you know you want to eat the dustbowl crunchy dirt
Same
ssbump is in essence pre-baked shadows information, not a real bump map. It was abandoned because it only works properly on static geometry.
thanks for summarizing. dude in the video wouldn't stop YAPPING when it can be summarized in like a paragraph
And because it's not industry standard. And ain't nobody got time for dat.
@@notnullptryeah the video went on for so long, like I know all this already I just wanna know what the ssbumpmap does man.
Probably good if you don't know about any of the other stuff beforehand tho
You can actually use these with real-time lighting, but i've only ever seen that done with sun-shadows since they're pretty global.
Thanks bro, I know the community is dead after 7 years without updates but 10 minutes about a premade bump map is NOT a good use of my time
"I was studying walls."
-LED and his fans looking for the pressable brick in the wall leading to a secret passage to a secretsociety (we are schizophrenic.)
It leads to Team Fortress 3
@@TungstenCubeGaming SOURCE 2!?!?!?!
Me rubbing my face on every wall to find out if there isn't a secret room with machine gun behind it
Fascinating topic, but there are two things I'd note about this video:
- Explanation of bump maps here is incorrect, bright areas on the bump map don't reflect more light back to you per-se, and you can see that in the video demonstration too. Bump maps have the same meaning as height maps, bright means higher "ground", dark means lower. And for bump-mapped lighting you don't really care how high or low the texel is, you just care about the slope. Flat white area will reflect the same amount of light in the same way as a flat black area. What you need to do is to sample the neighborhood too and compute those slopes, and get the normal, and then you light the pixel from there. That's why bump maps are pretty much completely phased out, normal maps just give that end result directly from a single sample. You can technically save some memory since bump map is a 1D value (so you can use just a single channel), and normal vector is 3D (so you have to use three channels, i.e. RGB (or possibly two with more math)), but it isn't worth it these days, we can afford normal maps memory-wise and it's just simpler and quicker overall to deal with them.
- Not completely wrong, but the file size comparison near the end is not the most relevant one. When they're saying their technique isn't requiring more memory, they mostly mean they're not using additional textures or additional channels, it's still RGB, so in GPU memory, where they'd either be uncompressed or compressed with fixed bitrate, they would be of exactly the same size. PNG isn't a GPU format, and is very content-sensitive. There is something to be said about hard drive memory too, but that's usually not the focal point in such graphics papers.
same i was like whar? when i heard the bump explanation
and woah you really went into details regarding bump maps, nice
i understand this is a fairly short video but just saying "represents height" sounds both accurate and intuitive
I kinda get what your saying about bumpmaps, rather than reduce the light that bounces off a texture, it skews the light away from the direction of the normal based on the brightness value?
And yeah, it's less to do with normals being full RBG and more to do with normals requiring more math to calculate.
@@Nilon241 In the end, lighting calculation is the same in both cases. You'll use the surface normal, and that can be the "real" polygonal one, or one modified in some way by textures and algorithms to produce the illusion of a "rough", more detailed surface. And that modified one will end up being the ~same for both the bump maps and normal maps. You're interested in the angle, and you can't know the angle with just the height info at a single point, you need to sample the neighboring points too, see if they are taller or shorter, in which direction, to figure out which way the surface is tilted. With normal maps, that normal/angle is directly what's written in the texture, you just read once per pixel and you're good to go. If A + B = C, with bump maps you have read A and read B, and then add them up yourself. With normal maps, you just read C, it's already there just the way you need it.
TLDR: They're both about "skewing the light", difference is just how you get to that skewing angle. One takes less memory, but requires more steps to reach that result, the other takes more memory but gives you ready-made result.
Actually, (tangent space) bump maps are pretty much 2D because scaling the tangent Z is quite weird
You can actually quantize normal map by loosing precision you would unlikely ever notice but it's not worth it due to how much vram modern gpus have and it adds a couple extra instructions.
Don’t worry! I’ll fix it!
*proceeds to 3D model every brick and detail in precise polygons*
And it will run in 60 flames per second
@@_GhostMinerhey it worked for ID software
vtf textures aren't just jpegs like. Apart of texture images for each mip level, they contain reflectance value and various flags that indicate how Source engine must interpret them. vtf can also have different compression method.
tf2 fans are starting to become insane considering how much they've toughed it out without an update for years and it just began to show. worrying.
Indeed it it strange, unique even, unusual to some
This is definitely a vintage technique
@@RedGoldDolfin-ez9iy and their report was quite genuine
I am genuinely astonished
collector
Even Valve is surprised
TF2 players are so starved for content that they've started studying walls.
“TF2 is not normal”
*Well I gathered as much*
Blend modulate texture is used to indicate how to alter texture transition on map displacements. This allows keeping small details between transition, like for ex. rocks between sand and stone.
Fun fact regarding 9:25 ; On Rotunda, the blend texture used for the oil shader in mid caused a ton of issues just before release due to the fact that the oil was shiny, had a $blendmodulate, and used SSbump. This wasnt an issue for most players, but DX8 and players playing without reflections enabled broke the shader completely. We had to make some fallback materials, brand new normal maps, and a lot of slamming our heads against a wall to fix it just before release.
Wow
1:50 Source 1 uses VTFs while Source 2 uses vtex. Its the same thing, its just that Source 2 gives you an editor to make these automatically rather than manually. Source 1 has a community tool called VMTEditor which is really useful for creating materials and I've never written a vmt by hand in ages.
It's nowhere close to the same thing. Source 2's material editor allows you to preview different shader types with a super helpful and intuitive UI that (I didn't mention this) supports .tga file formats, which is convenient for making quick edits. There are also various sliders and check boxes that allow you to make real-time adjustments to the texture maps.
All textures in Source 1 and Source 2 have to be compiled into a new format for the engine to use them. Both vtf and vtex contain some meta data + the actual image, usually with some form of DXT compression applied. He is saying that vtf and vtex are basically the same because vtex does for source 2 what vtf did for source 1.
The editor thing doesn't really relate to this. For source there simply wasn't a public official material editor that did the conversion from image + meta data to vtf and for source 2 there is. However the community made their own tools like VTF editor and VMT editor that would happily convert .pngs, .tgas etc to vtf for you.
Being able to use those file formats isn't special to source 2 nor does either engine work with non valve texture files. Its just now we have a nice material editor built right into the public tools ;-)
@@LEDs VTFEdit uses TGA
@@Apple-vk3fi If you save as instead of export, you can save as vttf
“TF2 isn’t normal”
We never fucking were and I’m proud of it
this is what happens when a fanbase has been starving for years
"we typically use things ike PNGs or JPG"
Well, no. That's only input format to engine. (And JPG shouldn't be EVER used in gamedev, and using JPG should be treated as crime.)
Game engines internally use rather GPU compatible compression format like DDS. VAT and Source2's VTEX are also DDS alike format.
And by DDS alike i mean literally DDS/DXT with extras like metadata
I remember messing around with ssbumps when I was working as a level designer for Pirates, Vikings and Knights 2 source mod. They worked well on organic textures like cliff, sand and weathered down bricks, but wouldn't work on a flat texture that had well defined elements on it, like a clean metal surface with rivets for example. In this case the self shadowing would only look good if the light came from one of the three specific directions that align with the direction of the shadows in ssbump texture. Otherwise it would just make a messy blend between the main shadow positions resulting in an extremely unnatural surface.
SSbumpmaps are also used a lot in L4D and L4D2, it looks good when lit with a flashlight, they are good for nature stuff like terrain, rocks and the like, not so good for small details or repetitive patters, the main problem they have is that instead of having light information in 4 directions like normal normal maps they have 3 using the rgb values, and they divide it using the 0 to 128 for the shadows, so half the range of detail, it also makes the texture look darker and the shadows also can overlap on parts where you need detail if illuminated by other angle.
Ssbump maps are fantastic, they compute faster and are smaller than having three images for AO, Bump, and Normal maps.
Maybe that’s what Chris meant when he was referring to smaller file size
Hampter
Strength of both SSbumps and Normal maps can be adjusted so not only can you make the curvature more pronounced for SSbumps, you can retain the AO.
I remember learning about ssbump layers from scruffy's pikmin model trivia video. You are my second youtuber to touch on the topic :D
I like walls
That's not what a bump map is. A bump map is just a height map as you later said. It's a texture where white pixels represent high points and black pixels represent low points and the game engine internally generates a normal map based off this information. The white and black pixels do not represent pointing "towards" or "away" from anything. It's just height information.
The way the game generates normals from this height info is as follows; if you have a single while pixel on an otherwise black height map, the game will see that white pixel as a hill and on the generated normal map it will generate normals pointing north on the pixel north of the white dot, south on the pixel south of the white dot, east to the east, and west to the west, making it so the surface where that white dot would be would appear to have a single small bump on it.
If you use an all black height map or an all white bump map they will both look identically lit and perfectly flat. This is because the game doesn't care about the objective colors of the pixels on these maps. It just cares about the difference between neighboring pixels and assumes a slope between high and low points..
Edit: To be honest your description of what a bump map is and this video you linked both seem unclear to me so I actually don't know if we're talking about the same thing or not. Here is what I understand a bump map to be: th-cam.com/video/nfaOP27GZ5U/w-d-xo.html
You were talking about skewing normals towards and away from "you" where I assume "you" is the camera and I don't understand bump maps to be doing this.
“This is done by skewing the normals towards and away from you”
I'm not really sure what that would mean. If normals are being skewed away from the camera, what direction are they being skewed in? Maybe we're talking about completely different effects, I'm not sure. You'll have to watch my short video and tell me cause I could just be wrong. I don't know how bump maps work in source or if they're different from other engines.
Also I can't reply for some reason.
It is what a bump map is, how do you think "height" works in the technical sense? By skewing surface normals that influence the way light reflects back to you. Watch here: th-cam.com/video/D7uK4WWW-Rk/w-d-xo.htmlsi=2iaHwhKCnhqCmtVy
@@LEDsI edited my original comment. I can't seem to send you a reply for some reason. God TH-cam is buggy...
This is one of the greatest things about TH-cam (ignoring all the terrible stuff about TH-cam), which is finding hyper specific and detailed breakdowns on essentially any topic that could hold any amount of examination or objective critique.
Has to be my favorite genre of creator.
I was not expecting the topic of this video to be what it was but I'm all for it
When the document referred to "texture storage space" it was likely referring to its data in VRAM, which in the case of Source is the DXT format due to its use of DirectX. Regardless of the actual texture *file*, the GPU needs to store that data in a way that it can use, and this is where storage really matters. If you make a file that's 4096x4096 but all one color and save it as a PNG, that file is going to be way smaller than the memory usage because in PNG we can afford to have some amount of time to load the image out of a compressed state, whereas in a GPU it needs to be ready in less than a millisecond to render potentially dozens of materials at once each using more than one texture. This storage technique is also why textures have a resolution that is a power of two (64, 128, 256, 512, ...)
"I was studying TF2's walls the other day,"
Yeah, apparently the players aren't normal either.
Honestly, I've always hated those brick walls because you can clearly see the DXT compression artifacts in the bumpmap. I don't know why they did that; most normal maps even in Source games are uncompressed, for that exact reason.
Whats up with this comment section? Did any of you guys actually watch the video???
The usual children and manchildren of the tf2 community. Just like in game, they try so hard to be funny 24/7 while completely failing at it. Absolutely love how a whole quarter of the comments are the same exact lame ass joke.
Most TF2 players don't have experience with gamedev texturing nor are they mature enough to comment or learn on it
which types of comments are you referring to?
last time i had heard of ssbumps was 11 years ago, never understood how they work and forgot about them, now it finally makes sense!
"i was studying walls"
What 6 years of no updates does to a game
“I discovered something weird”
Yeah some weirdo is staring at a wall, that’s what’s weird
Valve always pushed, created and generally developed new technology. This is one of the (if not the) company you want to go, when you look for a genuin creative think tank, who makes the bleeding edge of technology and actually turns it into a healthy, usefull and just good product for people.
I love this mans channel, keep it up!
I believe the ssbump was discontinued due to the fact how pbr works with AO, and secondly using ssbump the engine had to calculate the cross product of X and Y that is the RB channel, which is not that huge but again it saves gpu an extra step
Sorry for bombarding comments on your videos your videos are interesting :)
Read the title, saw the thumbnail and I knew you are gonna talk about textures.
What no updates does to a community
You're only realising it now?
I knew that ssbump had existed, but I didn’t know anything about it
@@LEDsthey are referring to the video's title 👍
TF2 is not normal, but it's also not normal.
"TF2 isn't normal"
The entire game depends on a cow cutout to function
I thought that was a hoax
Wasnt it a coconut?
@@KungFuGangsta the coconut is the hoax
Whether it was intentional or not, this title is a fantastic pun.
You know it 😉
Took me half the video but I see what you did there with "TF2 isn't *normal*"
ssbump does have one major downside. It doesn't support alpha masks, so reflective surfaces can't use it.
“tf2 isn’r normal”
You’re telling me that wall DOESN’T have a normalmap?
correct
This is what happens when a game doesn’t get updated for 7 years. I love this
"I was studying walls the other day"
Valve has abandoned this game so long ago hour long videos about the shortstop and.. this is our standard of content.
Tick-tock
Heavy like a brinks truck
Looking like I'm tip-top
Shining like a wristwatch
Time will grab your wrist
Lock it down till the thing pop
Can you stick around for a minute till the ring stop?
Please, God
Tick-tock
Heavy like a brinks truck
Looking like I'm tip-top
Shining like a wristwatch
Time will grab your wrist
Lock it down till the thing pop
Can you stick around for a minute till the ring stop?
Please, God
As time keeps slipping away (slipping away)
Girl, don't start feeling a way (feeling a way)
You and I, we are one in the same
Loving in pain, loving in (loving in pain)
As time keeps slipping away (slipping away)
Girl, don't start feeling a way (feeling a way)
You and I, we are one in the same
Loving in pain, loving in
Tick-tock
Gimme, gimme big bucks
That is all I do, girl
I just hit the jackpot
I wish you were here with me now so I could feel some
I wish you were here to hold me down like a real one, real one
Live long
Wanna be a big shot
Should've stayed away
But always had a weak spot
I've been on the road, and I'm sorry for the mix-up
If you still love me, can you see me during liftoff? (liftoff)
As time keeps slipping away (slipping away)
Girl, don't start feeling a way (feeling a way)
You and I, we are one in the same
Loving in pain, loving in (loving in pain)
As time keeps slipping away (slipping away)
Girl, don't start feeling a way (feeling a way)
You and I, we are one in the same
Loving in pain, loving in
With my hands in the ocean
With my hands in the ocean
With my hands in the ocean, I pay
I pray, oh, I pray
Little correction about bump maps: they represent the height of a pixel relative to the surface of the mesh. Pure gray is 0, white is out and black is in. The program then interpret that data to show how light and shadows interact with the object
"Height" means nothing without the context of surface normals. You can't just tell the engine "this is higher than that" using a value between 0 and 1. Bump maps work by perturbing the surface normals by a factor between 0 and 1. That's the most important part of the entire explanation.
@@LEDs usually software has a way to say "in this case 1 (white) equals 1 meter away from the surface and 0 (black) 1 meter inside the surface", it could be called something like "distance" or "strenght" or "scale" or something similar depending on the software. The surface normal thing is derived from that but it's not directly controlled by the bump map. Normal maps on the other end directly tell the software in what direction should the surface normal be pointed for that pixel
Cool vid! Does Source 2 use bent normals by any chance? SSbumps were designed to get a similar result in Source, they're mentioned briefly in the SIGGRAPH paper you show in the video. I'm wondering if they just started using those since modern software suites easily bake them, they're actively supported and used in UE at the least.
One note, to my understanding ''bump map'' became the umbrella term for height maps, normals, and possibly some other stuff like displacement maps (not entirely sure on that) etc when height maps were no longer the only type.
Somewhat similar to how normal maps are a colloquialism for tangent space normals because its a mouthful, bump map is sort of still a colloquialism for height map even though its not incorrect to say e.g ''normal bump'' on a technical level (3ds Max uses this to specify normal maps) but its definitely a bit confusing to work with and understand old Valve stuff since some terminology is, while not incorrect, a bit outdated. In TF2 as an example phong and exponent being used in place of specular and gloss which can be unfamiliar and throw some people off.
You can mark individual edges on any mesh as "sharp," "default," and "smooth" which changes the surface normals. You can check out my Pool Day video for a demonstration.
“Tf2 isn’t normal”
“Every 60 seconds a minute in Africa passes”
You're telling me ssbump doesn't stand for "Super Smash Brothers Ultimate Mario Party"?
This is present in Source 2, you can easily create a self shadowing normal, special texture shaders are not a difficult thing to add in Source 2.
It is not.
@@LEDs Custom shaders is absolutely a thing, it's compiled under the material format. You can see it under the material editor page.
I was expecting this video to be about the community and got a really interesting technical explanation instead. You've earned my sub
What 7 years without update does to a man.
I like to think ssbump map just stands for source spaghetti bump map
good pun
valve should sign this man in
they knew what they doing
this game really needs an update dog bro is out here studying the damn walls
🤓 what 6 years with no updates does to a community
you know the game needs content when were talking about walls
yeah i would say it is quite, unusual
0:00 When you're still procrastinating your life away after 10k hours of TF2.
In a game where suicide is the running gag of every joke, what did you expect?
You got bored on tf2 one day that you went out of your way to study the walls?
Interesting... There is another way to do this, materials from Quixel Megascans have Roughness, Occlusion and Displacement on one texture each occupying its separate color channel
Those are for PBR materials which are not supported in Source 1. You can only have "basetexture" and "bump" maps. There is no option for roughness, metalic, ambient occlusion, etc. and especially not displacement (not even Source 2 fully embraces displacement maps). There are some extra ones for adding details or blending two textures together, but that's a separate thing.
The normal map being more intense than the ssbump is more likely to be a result of artistic intent rather than due to the formats. In all the 3D software I've worked with, there has been some way to multiply the normal intensity which allows the artist to fine tune the look of the material, and by having the default normal intensity be really intense, it allows for less information to be lost when multiplying.
Also this is the first time I've heard someone call a height map a bump map, though I also don't use hammer.
The title of this video could be talking about literally anything in the game
No one: what are you studying?
Someone: Math
No one: what are you studying?
LED: w a l l
Video title "TF2 Had a New Bump Mapping Teqnique in it" wasn't catchy enough
That would've been awful
One of my favorite TF2 TH-camrs right now :)
led talked to a brick wall for 10 minutes straight. literally.
9:15 Small thing, but the size of the PNG files does not matter due to source using DXT/BC/S3 compression for its textures (most of the time), why this matters is because of the format being a fixed size, meaning even a single color across a 512x512 area will be identical to any other 512x512 texture of the same format, I'd explain but I'd end up butchering the explaination sooo en.wikipedia.org/wiki/S3_Texture_Compression
TLDR: no matter the PNG size, they would be identical down to the last bit in actual size in the game files and memory usage.
brickwall001_height-ssbump.vtf is actually 682.91kb in size, it is stored as a DXT1 texture with mipmaps, a DXT5 image of the same size would be 1.33mb, without mipmaps the DTX1 image is 512mb... god this comment feels 🤓
Yeah, I saw that the vtfs were all the same size, so I didn’t know what Chris meant in his paper when he he mentioned file size. That’s why I looked at the PNG files
I was studying tf2s walls...
aka what 0 meaningful updates does to mf....
strange unusual team fortress
level 5 game
+50% fun
wearer is vulnerable to bots
"the most fun you can have online."
Man figures out how gamedev work
always fun when artists get called out for saying very typical sentences like "studying the wall"
i promise guys, i am actually extracting important information please dont make fun of me
Well if this technically partially use normal maps would that mean that tf2 is normal?
It’s semi-normal
2:30 For some reason that reminded me of Arnold Schwarzenegger
I’m actually curious how to set up using normal textures in tf2 since I use a lot of custom textures from other games when making maps and a lot of the time they come with normals
Make a height map. Lighter is higher, darker is lower. Use heightmap to normal converter.
check the valve developer wiki page for VMT's I would assume
There's a tool for creating ssbump maps, haven't used it though: steamcommunity.com/sharedfiles/filedetails/?id=2877119600
Great video as always. I don't think their is a youtuber who talks about the stuff you do!
As a mapper, SSbump vs normal mapping is very trivial. You wouldn't be able to tell unless you were told which is which. And every mapper uses normal maps because they're far easier to create, as it's an industry standard. And normal maps do work in conjunction with blend and detail textures, despite what the paper says.
Also, the file size of the texture is incorrect, once converted to a VTF, as long as the textures share the same compression format, they will always be the same file size, no matter what the texture looks like.
I know, that’s why I compared the size of the uncompressed files
Its amazing to me how the content deprived community of tf2 can find so many different random ways to entertain themselves, and can find so many different things to make content on
Tf2 fans are staring at walls for content now
1:07 wait what? I thought vertexlit generic only used the model's root vertex for lighting, seeing as baked lights cause the whole model to either fall into shadow or be lit.
That’s caused by something else. I talked about it in my video “Everything wrong with Dustbowl”
Mapper is free to choose prop lighting either from arbitrary light origin (model origin or own pointed location) or use per vertex lighting. The second option doesn't work for models with bump map materials. And there's shadow texture option, but it's ass as it uses model's UV and requires the UV not overlap with each other, and increased bsp size.
@@LEDs huh. I recently watched that and didn't notice it. Can you give me an idea of where this is mentioned in the video?
I was thinking maybe my understanding of model lighting only applied to dynamic objects like players, not props baked into the map.
Damn, I really like the SS now !
i forget TF2 has bricks since i using flat textures
what no updates does to a mf 💀
soon they gonna review every pixel in a texture cuz of boredom
If you shine a light at a wall directly and get ambient occlussion in the crevices this is NOT realistic.
True, but when would you sine a light directly at a wall?
@@LEDs with a torch.
4:32
So what is it?
in a nutshell
you take a test and write down an answer, but you did it a slightly different way.
you get a 0 anyways because the teacher didn't recognize what you did.
You write code to make it segment an operation on multiple sequential pieces of data.
you look inside the compiled code and the compiler fed you slow code
"why?" cuz nuh uh, vectorization failed, no questions asked, explode.
That's SUPER interesting!
The title is a pun isn't it
ya
7:25, so im not sure if you are aware of this, but ambient occlusion is not a real thing that light does. It is a mimicry of real lighting where less light reaches certain areas, and game engines take advantage of this by feigning that same effect for a cheaper cost than ray tracing, however as shown in your example of the lighting it is actually quite clear that the normal map provides much more realistic lighting since if you are the source of the light you shouldn't be able to see shadows. Just wanted to clear things up a bit since you claimed the ssbump map was more realistic, when in reality I would call it more stylised in allowing you to see the shadows at all times even while in direct light.
ssbump clearly has its uses for a certain style of visuals, but it by no means is more realistic.
I’m aware of ambient occlusion not being realistic. When I was researching it while making the video, I came across a cool thread that explained why ambient occlusion is included in Blender’s Eevee but not Cycles. So, regarding realism, you’re right that normal maps are more realistic
The wall update
Normally at the top of the screen it shows you what class all your team are but it isn't there for me is there way to fix this
Never has been.