Katarina Alves Animations (Pixiv Fanbox)

gofile - https://gofile.io/d/9fblQN

porn3dx - https://porn3dx.com/post/50176

Second to last release before spooky month. This time of Katarina, who has been on the poll twice and lost catastrophically twice. I've had a few people ask me to do her since she lost, and I did want to give her a chance since she lost so much. When I was in my motivated phase, I was trying to think of characters to animate before October, and she just kind of naturally fit in as being someone I planned to do and the timing just worked out. Unfortunately, by the time I got to her, I was losing steam and the result is that I'm not too fond of these. I only ended up doing five instead of the (somewhat new)normal six. I just couldn't think of what else to do with her. Sorry for that. That said, it's for the best. While I didn't know it at the time of making them, rendering these turned out to be an ordeal. Not a major one, but it was a frustrating evening and may have been why I felt so poor this past weekend. Hard to say. Regardless, what happened was... these would not render. I hit the render animation, the first frame would pop up, then immediate crash. While I occasionally get a crash here or there with Blender, the program has come a long way since I first started animating with it and I don't have nearly as many crashes as I used to.

My first thought was "oh, I didn't pre-render the textures and it got overloaded and crashed". It's not super common, but I've had some blend scenes crash on me when I switch to shadered viewport and I tab out while letting the textures load in the background. Because I'm not letting my computer allocate all the resources to Blender, it doesn't get the adequate resources and shuts itself down. It happens. Not super common, but I had this recently with the Ada Wong animations I did because there were a lot of 4K textures being loaded. Whatever, it's fine. I went ahead and preloaded all the stuff by using the shadered viewport and hit render. Immediate crash.

"What the fuck" I say, and my immediate reaction is now "okay, must be something with the scene". This is my first time using this scene, and it's one I got off open3dlab that is an actual Tekken stage. Something must be causing issues that I'm not aware of. I did have to disable a bunch of rigid body simulations for something in the background when I was trying to watch my animations in the viewport, so maybe something like that is breaking it. I disable the environment and it starts rendering fine. Okay, I solved it. Now how do I get the environment to render? I just tried re-enabling it, and bam... it worked. Huh. Okay. Not a big deal, but a little annoying.

Cut to the third animation, and all of a sudden this trick doesn't work. It crashed even without the environment. Oh hell, what's the deal. I tried disabling various things like clothes and what not and that was still causing problems. Then, I decided to the exact same thing I had been doing and it worked, and then the environments worked. Okay, whatever. Computers are like that. I've been using them pretty much all my life, I'm used to this. Some people might complain about how "why is it that when I do the exact same thing, I don't always get the exact same result? They're computers, they should be do the same thing every time." And to them, I say, "it's complicated". Like, really, really complicated. You can't always replicate those things, because... well, computers are not perfect. They have hiccups now and then. Sometimes things happen because... I don't know, these things work on nanoscopic levels man. They've got trillions of transistors going "yes" and "no" at light speed with tiny electrical impulses. Maybe some program in the background(because god knows Windows has too many programs in the background) decided to do something at the exact wrong time and drew that tiny voltage going to that one "yes" a nanometer away to cross the voltage threshold and all of a sudden that yes became a no and then you've got the memory stored in the wrong byte and oops you've got a blue screen. I don't know if that's how it works, but I've worked with computers enough to know that shit happens. You ever just get a random twitch in one of your fingers? That's your brain firing an electrical response through your nervous system for no reason other than it got something wrong. If our own bodies can't get it right, how can you expect a computer that was designed by a human to be perfect? Cut the computer some slack.

Anyway, the fourth animation was kind of similar, but then comes the fifth. Now literally nothing I did worked. Couldn't even get a still image. And I struggled for a while. A good half an hour was spent trying to get this damn thing to render. It was the sideways animation, for the one person wondering. It just DID NOT WORK. Not even unloading characters or deleting the environment and what not worked. I banged my head against the wall and the wall did not budge. In my desperation, I used a different version of Blender. See, I had just recently updated to Blender 3.6 for a new feature that I had wanted for a while. The ability to turn any mesh into a volumetric with geometry nodes, keeping the shape of the mesh and what not. Not super useful, but there have been times I've wanted such an option for atmospheric purposes. I did not use any of these things for these animations, but this is the newest version of Blender. It's even their LTS version, which stands for Long-Time Support, which means they'll be updating it for a couple of years. It should be more stable than the 3.5 beta I have been using for the past year or so.

Well, no. That beta rendered it fine without having to do any tricks. Just hit the render button and bam. It worked. Maybe it's because I had used that to animate them. Could be a thing. But I animated the Lianshi animations in that version too, and they rendered no problems or issues at all. It was just these Katarina animations that crashed. I've had no other issues with 3.6 at all. I don't know why they were crashing. I really, really don't. Computers.