Event 1 & 2 was combined because he decided to add animation during the production of that event due to comments about his game being compared to being a DIK, which you can search this forum for details about. This also caused the delay for this release because his "animator" couldn't meet his dates; you can search the forum for details.
Event 2.1 is part of v0.160 because he was working on this version until the v0.155 animation was complete, which v0.155 (animation) was finished while working on v0.160, so he had to split and combine v0.160 with v0.155 to finish it and release it since v0.160 wasn't completed.
Event 5 (Sophia/Sam) was supposed to be a small event because of his concept that if something "hot" happens with Sophia on the previous day with one character, there is supposed to be a "cooldown" period on the follow-up. Well, he reversed course on that concept for this event after the Sophia/Sam event on PD 12 and turned (Sophia/Sam) into a major event.
Events 7 and 8 (Sophia/Dylan Part I and II) Part II was supposed to be half the size with animation, but he decided to remove the animation plan and increase the render count.
So, if you look, he is doing that right now. Which is to keep minor events low on the render count, and major events will have a high render count. The problem is planning and organization. There are events that he states are minor events, and then, during production, they become major events, which he ends up adding more renders and possibly animations.
But of course there will be still bit updates which will have way more, like for example the farm journey on Sunday.
It's the same concept he implemented when he announced event releases on 11.23.21. Minor events will have around 200+ renders and will only take a few months to produce. Major events will have whatever he thinks is necessary, plus animations, if needed, with a more extended production period. So this statement isn't new.
In the table you provided, there was an average of 400 renderings, except for version 0.170.
Additionally, the content before the developer's response was that the amount of rendering was too much for one developer to handle, and the developer's response to that was, "i wanna reduce the renders per update for the next playable day."
Additionally: (Resources I tried to find before but couldn't)
“12 playable days are done and 18 remain. The current update is the end of Part 1 of the game.” The developer said that when Part 1 was finished, PD12 was finished and PD18 was left.
PD12 is the 19th day in the game and includes the deleted week.
I previously said that the game was initially planned to last 30 days and that the developers later added 7 days.
This developer changed the schedule from 30 days to 31 days, and then again to 37 days.
“Which means they will be smaller of course but come out quicker.”
This is what the developer said before when fans asked for a shorter period between updates.
I've previously said that this developer said a month, but i failed to find evidence.
However, for a while after starting Part 2, this developer updated on average within 1 or 2 months.
But the last update took the developer four months.
- Thank you for providing the information.
- This post was not written because you, so I hope there are no misunderstandings.
I cancel the "30-day date" because I misunderstood it or I cannot prove it.
However, I would like to reveal that I saw a post where the date of this game was changed from the 30th to the 31st, and then changed again to the 37th. But I'm not sure I didn't confuse "PD" and "in game day".
In the table you provided, there was an average of 400 renderings, except for version 0.170.
Additionally, the content before the developer's response was that the amount of rendering was too much for one developer to handle, and the developer's response to that was, "i wanna reduce the renders per update for the next playable day."
It's about 346 renders on average between using events 1 through 8. If you combine v0.150, 0.160, and 0.161 and divide them by 2, that's about 334 renders between v0.150, 0.160 (0.161). But if you look at that list, you can see that he created 200 and 300 renders in 40+ days, but he had one 300 that exceeded 70+ days due to "personal" issues, which we found out on the back end of production.
The comment that he wants to reduce the amount of renders is a contradiction in terms with him. Because of this comment...
He's saying he doesn't know how many renders he needs to make a scene because it's a byproduct of produce quality. So he may create a scene with quality that has ten renders or a scene with quality with 1000 renders, which is still in play today.
Additionally: (Resources I tried to find before but couldn't)
“12 playable days are done and 18 remain. The current update is the end of Part 1 of the game.”
The developer said that when Part 1 was finished, PD12 was finished and PD18 was left.
PD12 is the 19th day in the game and includes the deleted week.
I previously said that the game was initially planned to last 30 days and that the developers later added 7 days.
This developer changed the schedule from 30 days to 31 days, and then again to 37 days.
“Which means they will be smaller of course but come out quicker.”
This is what the developer said before when fans asked for a shorter period between updates.
I've previously said that this developer said a month, but i failed to find evidence.
However, for a while after starting Part 2, this developer updated on average within 1 or 2 months.
But the last update took the developer four months.
- Thank you for providing the information.
- This post was not written because you, so I hope there are no misunderstandings.
I previously said that the game was initially planned to last 30 days and that the developers later added 7 days.
This developer changed the schedule from 30 days to 31 days, and then again to 37 days.
It's still 30 PDs; the 37 days are game days because of the one-week time skip at the beginning of the game. It jumps from gameday 4 (PD 4) to gameday 11 (PD 4.5).
It's about 346 renders on average between using events 1 through 8. If you combine v0.150, 0.160, and 0.161 and divide them by 2, that's about 334 renders between v0.150, 0.160 (0.161). But if you look at that list, you can see that he created 200 and 300 renders in 40+ days, but he had one 300 that exceeded 70+ days due to "personal" issues, which we found out on the back end of production.
The comment that he wants to reduce the amount of renders is a contradiction in terms with him. Because of this comment...
He's saying he doesn't know how many renders he needs to make a scene because it's a byproduct of produce quality. So he may create a scene with quality that has ten renders or a scene with quality with 1000 renders, which is still in play today.
What I'm talking about is not the production period.
What this developer said is also not the production period.
What this developer was talking about is the number of renderings per update.
It doesn't matter whether this developer can plan the number of renderings per update or not.
It also doesn't matter whether this developer can do the number of renderings per update as planned or not.
What matters is the number of renderings per update.
And this developer said he wanted to reduce the number of renderings per update.
I previously said that the game was initially planned to last 30 days and that the developers later added 7 days.
This developer changed the schedule from 30 days to 31 days, and then again to 37 days.
It's still 30 PDs; the 37 days are game days because of the one-week time skip at the beginning of the game. It jumps from gameday 4 (PD 4) to gameday 11 (PD 4.5).
I cancel the "30-day date" because I misunderstood it or I cannot prove it.
However, I would like to reveal that I saw a post where the date of this game was changed from the 30th to the 31st, and then changed again to the 37th.
But I'm not sure I didn't confuse "PD" and "in game day".
What I'm talking about is not the production period.
What this developer said is also not the production period.
What this developer was talking about is the number of renderings per update.
It doesn't matter whether this developer can plan the number of renderings per update or not.
It also doesn't matter whether this developer can do the number of renderings per update as planned or not.
What matters is the number of renderings per update.
And this developer said he wanted to reduce the number of renderings per update.
What matters is the number of renderings per update.
And this developer said he wanted to reduce the number of renderings per update.
You're not getting it. He can't reduce the number of renders because the render count comes from the quality. He is very OCD about this concept. He doesn't have a render limit, so he said he wants to lower the render count instead of saying he will lower it because if he feels it will mess with the quality, he won't do it. Everything is based on quality, not quantity. Quality is the driving force behind the amount of renders.
What matters is the number of renderings per update.
And this developer said he wanted to reduce the number of renderings per update.
You're not getting it. He can't reduce the number of renders because the render count comes from the quality. He is very OCD about this concept. He doesn't have a render limit, so he said he wants to lower the render count instead of saying he will lower it because if he feels it will mess with the quality, he won't do it. Everything is based on quality, not quantity. Quality is the driving force behind the amount of renders.
There is no way for us to know how many times or even thousands of times this developer repeatedly performs rendering to improve image quality.
You will never know how often he returns and re-edits a render multiple times unless he tells you, and yes, most people here use renders and printed output as interchangeable words.
Also, he has to make unique renders for DOL, so he is doing double the work.
“The quantity is just a byproduct which emerges by the amount of renders I need to tell a scene!”
You've been using "rendering" for a different meaning from the beginning (you're right), and you knew that some people here, including developers, were using it differently.
There is no way for us to know how many times or even thousands of times this developer repeatedly performs rendering to improve image quality.
You will never know how often he returns and re-edits a render multiple times unless he tells you, and yes, most people here use renders and printed output as interchangeable words.
Also, he has to make unique renders for DOL, so he is doing double the work.
There is no way for us to know how many times or even thousands of times this developer repeatedly performs rendering to improve image quality.
You will never know how often he returns and re-edits a render multiple times unless he tells you, and yes, most people here use renders and printed output as interchangeable words.
Also, he has to make unique renders for DOL, so he is doing double the work.
He acts like this game is a force of nature that he has no control over. The Scope and scale of updates is entirely in his control, yet he acts like the updates are handed to him and he must comply without question. Like, if the upcoming horse/farm event is too big then make changes.
