Dev Update - 2025/10/10
Hey everyone,
Oof, what a week. It was very busy with work of all kinds, even by my standards.
The day job is pretty exhausting at the moment due to a big project coming to an end, and I try not to let that influence the game development too much.
I have bad and good news.
As you might remember from last week (I didn't, I had to look it up), I've been working on a very long scene and said that I had roughly 100 or a bit more static renders to do for that scene.
Yeah... turned out that estimate was too low... who would've thought.
But again, even by my standards... boy, was I off.
So the bad news is that it was over 200 renders needed for the scene.
As of now, 202 to be precise.
I know that my estimations are on the low end most of the time because I always find new "ideas" for squeezing in additional renders.
But I think it was the first time I was THAT off.
Bummer, so what's the good news?
The good news is that both pc's are rendering the final images of that batch, which means I somehow managed to set up over 200 renders this week.
That's also a first.
My plan for this week was to get as close to the end of the scene as possible.
Except for the renders still in the queue and implementing all renders into the game build, I'm done.
At the start of this week, it seemed way too optimistic to hope to get that far.
So... Yay, I guess?
I plan to create the next internal test build this weekend when all renders are done and then run a few tests on that.
After that, I'll move on to the next scene, which will be the last one before the Chapter Finale.
The numbers for this week:
202 new static renders for a total of 1523
0 new animations
597 new lines in the script file for a total of 5343
That's it for today.
Have a nice weekend, guys.
Cheers,
Ceo
Comments (4)
I reckon that's a scene with Elea... You need to do even more renders. 😁
already 440 renders. That's enough, I think :-D
I remember when a project lead praised me for finishing the project on time.- "Well, it took a little more than my estimates" I said. - "Oh, that. Yeah, but I always multiply your estimates by the square root of 2, and according to that, we were right on time".
on the day job we multiply by 3 because there's always some smartass who tells you that your estimate is too high and it needs to be lower, no matter how high or low the estimate is. That way, we can be "generous" and go down to x2 of what the developer estimated and that's usually a good point :-D
