Alex probably can't add them into the game, because they fuck over old animations and he has 0 idea how to fix it. People were making new models for him before and he didn't add them either.
Yes, people compared her to Bloodrayne/Ruby Rose from RWBY or some Cassie from another game I can't remember.
Oh, that's as tragic and hilarious as his attempts at playing "real big boy game developer". Sadly, no videos were saved from that time, since he streamed on Mogulus, later renamed into livestream.com. Damn, and I thought hitbox was old.
Maybe its just me, but I thought right away these weren't 3D models and in fact was just blurred out drawn concept art. I think its super obvious too. This is concept that never got anywhere because the only "model" in the files thats been shown (by him and kgon) looks like none of these.
I think, you are right, since there are clearly two sets of images. I doubt, Alex would add two sets of models.
In the beginning, 2009-2011, but if you manage to find anything entertaining from his pre-YandereDev days i.e. before 2014, I will gladly add that.
Does anyone know what he means about using spreadsheets instead of a state machine? Is he actually using a spreadsheets to keep track of all of his if/else statements so they don’t interact with each other? I’ve never heard of this
I guess so. That would explain why Student_Script is such a mess - the game checks ALL the conditions. For every student. Each frame. I also remember that instead of making "dead" into a separate state, he made it as just a property, so you could encounter a bug, where stabbed student lays on the ground, but still reacts to your actions.
We know progress of the game has been slow and that it's had more than its fair share of bugs when compared to other games. We can speculate as to whether those problems are fueled by his programming style, I would say a likely contributor, but we can only speculate. If Alex feels his code is written best to suit his preferences then so be it.
1. You're a retard. There is absolutely an objectively best way to write something. You're describing Minimum Viable Product, which isn't even "getting the job done".
I don't like that the "10 paragraphs" wasn't an exaggeration.
Wrong. CPUs are fast, but they arent fast enough to do 64million operations in 16ms. That would require a speed of 3.84 Gigahertz, and that only if every pixel requires only 1 instruction. Thats why GPUs exist.
Yeah it can try. But like the saying goes "you can't polish a turd". Badly written code will execute slowly and buggy, no matter what the compiler does.
That is what that skullgirl-guy meant by "spreadsheet". The games configuration should be in a spreadsheet and not in code. YanSim actually does that to a limited extend, with students.json. It defines every students routine and attributes.
Yeah the performance benchmark videos others have done proof this. Maybe his game isnt bottlenecked by his code, but the development (*cough* 6 years *cough*) is.
This reminds me of when moviebob tried to say there was no right way to code, and compared it to how the Beatles couldn’t read sheet music.Honestly, discussing Alex's code is such a circle jerk. Since, there isn't an objective standard to judge someones code by.
Most people, myself included, consider Alex's style of coding unorthodox/bad but many legendary programmers like Jon Blow and John Carmack write in unorthodox styles. In the end, I don't see the point in sperging about coding style """if""" it gets the job done.
Many people express performance concerns when evaluating Alex's code. However they commonly backup their performance concerns with stylistic critiques. Such as, the infamous if-else sperging. The thing is, and what people don't realize is, the computer doesn't execute the code Alex writes. The compiler has to translate his C# code to machine code -- code that a cpu can run. During the translation, many optimizations are made, such as, long if-else chains can be replaced with faster performing jump tables. At the end of the day, a computer program is a long list of instructions a cpu must execute. No matter how many functions or files you split your code into, it still get smashed into one executable as a long list of instructions to be executed. Both Blow and Carmack advocate for longer functions and large files, arguing it makes programming easier and actually increases performance.
Now does that mean you can write any old program and have the compiler make it run fast? Of course not! The compiler can only try and find faster ways to compute what it was asked to compute. Thus, spawned the "computer-science" field of "data-structures and algorithms". As as side note, a lot of bullshit comes out of this field, but it has a few good core concepts, unfortunately some people hopped up on their own farts ran way to far with those concepts. I digress. If you need to increase performance beyond what the compiler can do, there are some simple ways to achieve that.
A list that is likely to simplistic to be of practical use day to day but a programmer can look through their code trying to find things they're accidentally calculating that aren't needed or things that can be cached and reused. Certainly there are more ways to optimize code for example; multi-threading, use of modern processors' features, rewriting in a faster programming language or not using a shit engine, haha. Going back to the simplistic list and what I said about compilers, I hope you can see, at the most basic level a programmer decides what needs to be calculated and the compiler finds faster ways to calculate those things. Further, I hope you can see, coding style has little to do with choosing what work needs to be done and therefore programming style has little to do with performance.
- Don't do unnecessary work - If something is expensive to calculate and you don't need it, don't calculate it.
- Cache results - If something is expensive to calculate, save the result and use the saved result multiple times instead of calculating it multiple times.
- Alternate algorithms - Find a different way to achieve the same or a similar result that requires less work.
So the obvious question becomes "Ignoring Alex's programming style, is his code efficient in choosing what work to be done" and the answer is: it doesn't matter!
Let me ask you this, what monitor resolution are you read this on right now? Likely 1920x1080, because that is the most common resolution in 2021. A 1920x1080 monitor has over two million pixels -- wow! If you are watching a 1080p video at 60 fps, your cpu must perform over 64 million pixel operations per second. Whatever work must be done per pixel, it had better be fast. Now going back to Alex, yansim has around 100 students and teachers when combined. Even if he has some atrocious update function that is called every frame... well guess what, those 2 million pixel operations also have to happen every frame. The thing is computers are fast, like really fast. And anything that is operating at even a thousand times a frame is happening at the engine level. Things like collision checks where each moving object has to check which of potentially thousands of triangles it has collided with. Those engine level operation are supposedly optimized by the professionals working at Unity and we can expect those things to be very performant, haha. Seriously though, you can write some pretty dumb code in unity and still have good performance. Simply because, the engine is multi-threaded, auto caches calculations behind your back and uses other advanced optimization techniques. Further, the code you write will only be executing for a fraction of the time the core engine's code will be executing so doubling the performance of your code will only marginally decrease total time taken to run a frame. Therefore, I don't think if you cleaned up the student script it would offer much performance gains.
Now, another concern with his programming style relates to his ability to work with it. Writing bad code can be hard to read, hard to change, hard to update and hard to bug fix. I'm not making any statements to support those claims just trust me.
I'm not convinced the performance issues with yansim aren't largely if not entirely due to unity itself. Don't get me wrong, the rig needed to get 60 fps is absurd. However, meshes don't have proper LODs and are made by voleneers who don't optimize them very well. It's reasonable to expect poor performance when in development, at most studios they develop games on rigs with quadruple the sepecs of their launch target. Because, until all the optimizations are done, at the end of development, the game will be slow.
However, If the performance issues are the fault of Alex's code, then I believe it's because he's not using the engine correctly -- and trying to using the engine properly is dumb! At least at one point in time, moving UI elements in Unity was so atrocious it was better to move the whole world instead. Eg. if Mario moves 10px to the right, instead of moving Mario, the camera, and the UI 10px to the right, you would move the whole world 10px to the left. Nobody writes a game like that, you would need code executing on every object in the world moving it based on player input and need to keep all those object moving in sync. Yeah, Unity is a beast I don't think anyone can tame.
Overall, I would love to get my hands on his project, try to optimize it and see what the real performance issues are. I'd even do it for free! Until then, all I can do is speculate. All anyone can do is speculate, and holy shit, speculating about Alex's code really brings out the autism in people.
If you want to include a part about Alex's code in your documenting, I'd suggest just documenting all the common critiques and all the well backed critiques. Then, let the readers decide for themselves which critiques are valid and if Alex's code is bad or not and what makes it bad or not.
It's hard to have one, when he didn't try to move past 'if/else" operators. I am not joking.
I feel like I've seen this argument before. I'm pretty sure all of these arguments were once in a Youtube video, but it turns out that the creator was a YanDev simp. I'm sure someone else can find the video I'm thinking of because it eludes me. Either way, this is retarded. Yes, the compiler translates code and makes optimizations, but you cannot rely on the optimizations the compiler makes. If you write shitty code, you cannot be surprised if the computer polishes your turd and it runs like shit or doesn't operate as expected.
OK but you're wrong. There is an objective standard to judge someone's code by. I'm not going to pretend to be an expert, but literally one of the big things hammered down people's throats when they learn computer programming is about the code standards because it's super important. Every coding language under the sun follows coding conventions because it's just simply retarded not to. Coding standards ensure that code is consistent, which makes it easier to read and debug. It literally doesn't matter if Alex is making code that only he will see because he has thrown around multiple times that he wants a professional to help him. A professional might be able to read whatever bullshit he writes, but at the end of the day, his shit is confusing and hard to read and it's going to take someone special to understand what the fuck he's doing. Other than the fact that Alex is really lazy, he clearly has trouble with his own code, having to constantly patch problems his shitty code produces. He has made the problems worse for him than he had to.
