Interpenetration is when you stick an element of an object through another. In some cases it can be handy, but it isn't always the best idea.
In the early days of 3D, interpenetrating geo saved us a lot of polygons. But engines worked differently then... polygons where expensive.
In this example, if I welded the beam into the block, it would increase the polycount by whopping... wait for it... 6 whole triangles.
But the rules are different now, 3d cards use a whole new set of rules.
The texture takes up more memory than the mesh you save, so if you bake like this, some of the texture will be wasted.
Either way, the saving isn't as big as it used to be.
Now lets say we bake a high poly model onto this, the bake will have artefacts. You have two polys with vastly different normals- so the bake draws the stud details from two angles.
Now look at this bake. Mmmm... looks nice. This is an example of the different between interpenetrating geo and cut in.
By cutting in here, I have four vertices with normals at the point where the beam meets the stone. That changes the bakes normal, resulting in a bake that appears to be organic. That extra geo pays its rent.
Even when you have an object that needs to stick in like this, I will still slice the sticking through part close to touching the face. This puts the vertices in a place I can use them. You can often bend the normals to help blend the object into the other.
I cover this and all the other techniques from decades of polygon and pixel witchery in my forth coming book.
A video game that simulates #ADHD. The mission objective changes at random every few minutes and whenever you walk into a new room, your inventory shuffles one item and sometimes it becomes invisible for a few minutes.
You auto steer into table corners.
Whenever you get more than one sidequest there is a chance you go into overwhelm and your controller will pretend it is unplugged.
The corners of the level starts filling up with laundry.
You put down an item and it vanishes when you look away.
You have timed missions but during loading screens that can dramatically shorten by an hour or five.
In Life Is Strange Before The Storm, one truth Rachel Amber tells Chloe during "two truths and a lie" that she is a Leo.
The brilliant thing is later if you pay attention, her birthday is the day after Leo ends. But her starchart has her on a cusp.
This is brilliant.
The series has a few moments of absolutely brilliant subtle clues in it that add layers of meaning, but you have to be sharp to spot them.
But if you miss those, there are still blatant clues around the place that give some level of depth.
The main mysteries of the game aren't hard at all, probably to a fault, but on replay there are far more little ones.
A technique I highly recommend to #gamedev artists is to look at actual shipped game assets.
There are various ways to get hold of them, such as programs like Ninja Ripper, Utiny ripper or via archives.
And I must stress this is for learning purposes ONLY. NEVER use them.
Being able to look at models from a wide range of titles, see how they are rigged, how their Uvs are layed out, the triangle count and modularity... it all helps you understand the ACTUAL end result you are aiming for.
I think it is really important that students bridge the gap between where they are at, and what the end products are at.
You may think "oh, the models in X game are super high end, high tech stuff" but when you actually crack it open and examine it in your DCC...
There is no future for humanity in a world where all human endeavour is stolen and boiled down to something that replaces humans.
What do humans do in a world where humans are not employed to create?
Is that a world you want to live in?
If you take away the creative process of human artists into pool, the zeitgeist becomes entirely manufactured from an ever decreasing pool of looping cannibalism.
Pop literally eating itself.
Endless product without exploration. Product feeding on product.
No art movements, no re-evaluations of our place and relationship to the world.
Draw calls are responsible for a good 50 percent of the chugging issues I have helped games with.
A draw call is "okay now draw me an apple, and come back when you are done for the next instruction."
Then you ask for another apple. Then when they return you ask for another...
So the GPU is running back and forth to the CPU when it could just do that once and "draw me a pile of apples".
Rendering an apple, in this example, takes a tiny amount of what a core on the GPU can render. So by welding all the apples into one bigger mesh, it can be done faster in one draw call than all the fucking around to draw them one by one.