CORRECTION: The sqrt instruction does not take 1 clock cycle. More like 20-60. It's still pretty fast though, and we don't have to check for distances often enough that this matters.

CORRECTION: Combining meshes does not necessarily reduce draw calls. I think Unity does it to improve load times.

SO WHY IS THE GAME SLOW? See: https://www.youtube.com/post/UgwqYKf598HtLsnKV314AaABCQ

I'm sorry for all the mic popping. :( Tried to fix it in post as much as possible, but we couldn't get all of it.
About drawcalls: Unfortunately, Unity's frame debugger does not work on linux. However, pointing the camera at all the students causes the game to render about 2 million triangles, and looking away makes the game render about 200k triangles. Don't need the frame debugger to deduce the problem here. Apparently there is a lot I don't know about graphics engineering. Sounds like a good topic for another video....
UPDATE:
I took a very brief look at the frame debugger on windows, and it pretty clearly explains why looking at students decreases the framerate so much. Here's a summary of what I found:
- Students are drawn twice, using 2 different shaders, one without the toon outline, and one with the toon outline.
- The student's irises have their own draw calls. Some irises have little shines in them, which are on another iris mesh, with their own draw call.
- Each modular part of each student has it's own draw call.

I've been working with Yandere Dev to optimize the game and bring the framerate up.

I find it hilarious that the biggest file in the game is a model of a toothbrush that he just bought from an asset store and never noticed that it has polygons for every individual bristle.

Me who doesn't know anything about coding: "Yeah, you're perfectly right."

"If he spent another hour on [this], it would have potentially saved him a couple years of grief."

That's it, that's the game in a nutshell.

Yandere's code can turn out to have educational value. His code should be on exams or homeworks and ask students to identify the problems

"Inconsistent use of tabs and spaces"
"F-ing pick one"

I felt that

'sort of implied that he didn't want me to do it'

'so I did it anyway'

You mad lad

You got me hooked in the first minute lol.

“But before we begin, I want to make it clear — because the last time it didn't get through your fucking skulls — NO BULLYING.”

"The compiler is smarter than you."

Completely valid statement.

My man be lookin like coraline's dad.

I never knew that this was what I've been missing in my life. I went fullscreen on this badboy, lay back in my chair and watched this shit like a nature documentary.

"a dark magic ritual known only to the compiler gods"
so like building any cmake project

Hitman 2 and Yansim having similar performance issues is the closest yandere dev has ever gotten to his cited design references

I don't understand 80% of what you're saying, but I deeply appreciate the polished visuals and editing, your natural charisma and calming voice, and how comprehensive I have to assume all of this is. I didn't even realize I had watched the entire thing until it was nearly done.

I was surprised he responded to your email but then I remembered that's what he does all day instead of coding

Finally a real analysis of the whole thing! Not just "IF-ELSE bad, SWITCH good!!!"

51:20 "The ritual used to pull this standard out of some poor engineer's ass" - Engineer dies in background
That must be the most obscure TF2 reference ever, even I barely noticed it and had to rewind.

“don’t decompile my code”

“Ok, I’ll do it while you don’t watch

Me as a non coder: Haha lines go 🅱︎🆁︎🆁︎🆁︎🆁︎🆁︎🆁︎

I can not stop laughing over the irony that one of the reasons people complain about framerate..... is that yanderedev implemented the framerate display so poorly that it displays lower frames than it actually has. (48:50)