That's a very good point.
we did, but when you count how many renders/animations were in each episode, they're getting bigget and bigger. For ep.10 there will be more than 5k renders, there is no other game that have that big updates.
It is certainly not a case of the "Female Agent" developer who seems to breed for months over a few lines of text. DPC DOES a lot of work.
.
Okay guys I'll see you in December then.You must be registered to see the links
Grab a cup of something and take a break. A large chunk of text without a tldr incoming.
First off... Boom! The 5000 render milestone was reached this week. Now episode 10 has more renders than episode 9 - the previously biggest episode in the game. And because I reached this milestone, I had to try and estimate how much is left in terms of development.
I have been working on art and coding all week. I started by completing two smaller scenes and one free-roam event. The better part of the week was spent on creating the last free-roam event of the episode. Since it's a new environment, there was environmental design to carry out first, and also preparation of the characters for it.
The dialogue for this free-roam event was written months ago, so it's a matter of creating the art and coding the events and buttons. It's a labor-intensive yet easy free-roam event to create, so I should be able to maintain a good speed without any speed bumps.
After the recent weeks of playing and polishing the game, my flowchart has been updated, and the following checklist is what the current state is like.
As I develop these episodes, I always ask you to take numbers with a grain of salt because the scene/render/animation count will change until the last few weeks of development. This is why it's always hard for me to give accurate estimates.
As you will notice below, the scene count is larger than I reported earlier because of the addition of some scenes that were needed to make some branches feel whole.
Checklist Episode 10
This is the current checklist of what's left to do before beta testing can begin.
Scenes
Three lewd scenes - One is written. Neither scene has any art.
Three free-roam events - One is almost complete, another has a few scenes left, and I'm ~70% through the last one. All writing is done. All need a different degree of testing and additional phone content.
Three normal scenes - One is written, one has partial writing, and one is planned. Neither scene has any art.
Art
Based on the scenes above, I estimate I must pose an additional ~600 static renders and 70-100 animations.
Current static render count: 4892 produced. 220 posed renders in the render queue. 5112 renders total.
Current animation count: 237 produced. 28 posed animations in the render queue. 265 animations total.
Code
Pack Quest - In the planning phase.
Vault - Ensure that numbers are placed and work as intended.
Rewards/2D art - 70% completed. The rest will be placed in free-roam events, story scenes, and the Vault. Testing and possibly correction of code are needed.
Gallery - The lewd gallery has been coded but can't be tested until all lewd scenes have been made. Some art remains for miniature images.
Phone content - There's some work left with the Rooster and Chat apps. Also, the new phone gallery will get additional planned content. The music app needs updated code to include new songs.
Bios - I always leave bios for the last part of the development.
Episode end screen and report - In the planning phase.
Credits - I haven't added new patrons to the credit section yet.
Sound
SFX work has been done as I play-tested parts of the episode; I estimate it's ~80-90% done.
For music, it's the same as with SFX. Most of the scenes that are complete have songs in place. 25 new songs have been added so far.
Testing
I haven't played the episode from start to finish yet because of gaps in the episode and missing content near the end.
My personal tests and polishing remain. How long they take usually depends on how much I have played the episode during development and whether new features are involved.
Episode 10 is packed with new things for the game, meaning testing might take some extra time to ensure high quality.
My thoughts on the checklist.
The animations will be the most demanding part, but cannot be skipped or trimmed as the scenes are essential for the episode.
The static render estimation can change in either direction but is likely lower than stated.
The code tasks are all fast tasks to complete. I estimate that I could get all of them done within 1-2 days of work, but they depend on the art content I need to produce first.
The remaining work on SFX and Music won't take too long, 1-2 days here as well.
Testing is another demanding part. I have lots of new features to test this time around. And we are talking about the five main branches on top of some very ambitious branching within them.
As always, there will be waiting time for animations near the end of the development, and this is when I plan to perform my personal tests and polishing.
Hopefully, I have covered all aspects of the checklist, but I may have missed something minor - all big tasks are accounted for.
My plan going forward.
I plan to work with art until I need to write the last scenes. Animations will be posed intermittently.
I plan to be done with my testing as the final animation frames are produced, thus minimizing the time between the PCs being idle and the start of beta testing/proofreading. As usual, at least two weeks will be allotted for private beta testing and proofreading before the episode can be released on Patreon.
Next up for me is to continue with art on the free-roam I'm working on and hopefully be able to move on to other scenes later next week.
Have a nice weekend, and thanks for reading
Dr PinkCake
DPC try's like a fat guy wanting to lose weight but goes to a buffet and wonders how he gain 10 pounds
I think he gave up on that. Apart from the fact that the wait times between episodes will be longer, I personally don't mind, as it means that the story will continue to be rich and varied, honoring players choice. With all the branching, keeping episodes smaller means that DPC would have to ignore players' choices, implement branching at only a very superficial level, or make it so that each branch becomes smaller and smaller with each episode. Players would ultimately become frustrated and disappointed with the game overall, then. Frustration over wait times is preferrable, I would think. Certainly I wouldn't mind if DPC dropped the pack quests, the 2D art, and the like, but I love it that the episodes are big and meaty. With more branching there's more replayability, too, which is a plus, considering how few other titles are worth even one playthrough.
I think now few people would be outraged if DPC didn't give players false hopes that "episodes will be smaller." He should honestly say that with all this branching and non-linear structure, it is impossible to make them smaller without cutting out a significant part of the plot. Instead, DPC kept feeding the audience with blue pills and now we have what we have.
I think he's hinting here at the mechanics of cheating and how it will affect gameplay. About being able to dump your girlfriend and start dating someone else.
It's a really complex animation because DAZ doesn't have a normal fluid simulation. I have no idea how he did it. He probably animated the splashes separately and then edited them into AE. But overall I agree. There is no point in creating in DAZ any animations more complicated than sex because DAZ is not capable of that.
About Blender, how easy is it to port all daz kits to Blender? I've heard that Blender is much better for serious animations and faster, but would it be easy to port the entire huge library that BaDIK is?
I don't think people here realise how game development or any other development in creative media works if you strive for something of high quality.
Well, this is a bad sign.You must be registered to see the links
Grab a cup of something and take a break. A large chunk of text without a tldr incoming.
First off... Boom! The 5000 render milestone was reached this week. Now episode 10 has more renders than episode 9 - the previously biggest episode in the game. And because I reached this milestone, I had to try and estimate how much is left in terms of development.
I have been working on art and coding all week. I started by completing two smaller scenes and one free-roam event. The better part of the week was spent on creating the last free-roam event of the episode. Since it's a new environment, there was environmental design to carry out first, and also preparation of the characters for it.
The dialogue for this free-roam event was written months ago, so it's a matter of creating the art and coding the events and buttons. It's a labor-intensive yet easy free-roam event to create, so I should be able to maintain a good speed without any speed bumps.
After the recent weeks of playing and polishing the game, my flowchart has been updated, and the following checklist is what the current state is like.
As I develop these episodes, I always ask you to take numbers with a grain of salt because the scene/render/animation count will change until the last few weeks of development. This is why it's always hard for me to give accurate estimates.
As you will notice below, the scene count is larger than I reported earlier because of the addition of some scenes that were needed to make some branches feel whole.
Checklist Episode 10
This is the current checklist of what's left to do before beta testing can begin.
Scenes
Three lewd scenes - One is written. Neither scene has any art.
Three free-roam events - One is almost complete, another has a few scenes left, and I'm ~70% through the last one. All writing is done. All need a different degree of testing and additional phone content.
Three normal scenes - One is written, one has partial writing, and one is planned. Neither scene has any art.
Art
Based on the scenes above, I estimate I must pose an additional ~600 static renders and 70-100 animations.
Current static render count: 4892 produced. 220 posed renders in the render queue. 5112 renders total.
Current animation count: 237 produced. 28 posed animations in the render queue. 265 animations total.
Code
Pack Quest - In the planning phase.
Vault - Ensure that numbers are placed and work as intended.
Rewards/2D art - 70% completed. The rest will be placed in free-roam events, story scenes, and the Vault. Testing and possibly correction of code are needed.
Gallery - The lewd gallery has been coded but can't be tested until all lewd scenes have been made. Some art remains for miniature images.
Phone content - There's some work left with the Rooster and Chat apps. Also, the new phone gallery will get additional planned content. The music app needs updated code to include new songs.
Bios - I always leave bios for the last part of the development.
Episode end screen and report - In the planning phase.
Credits - I haven't added new patrons to the credit section yet.
Sound
SFX work has been done as I play-tested parts of the episode; I estimate it's ~80-90% done.
For music, it's the same as with SFX. Most of the scenes that are complete have songs in place. 25 new songs have been added so far.
Testing
I haven't played the episode from start to finish yet because of gaps in the episode and missing content near the end.
My personal tests and polishing remain. How long they take usually depends on how much I have played the episode during development and whether new features are involved.
Episode 10 is packed with new things for the game, meaning testing might take some extra time to ensure high quality.
My thoughts on the checklist.
The animations will be the most demanding part, but cannot be skipped or trimmed as the scenes are essential for the episode.
The static render estimation can change in either direction but is likely lower than stated.
The code tasks are all fast tasks to complete. I estimate that I could get all of them done within 1-2 days of work, but they depend on the art content I need to produce first.
The remaining work on SFX and Music won't take too long, 1-2 days here as well.
Testing is another demanding part. I have lots of new features to test this time around. And we are talking about the five main branches on top of some very ambitious branching within them.
As always, there will be waiting time for animations near the end of the development, and this is when I plan to perform my personal tests and polishing.
Hopefully, I have covered all aspects of the checklist, but I may have missed something minor - all big tasks are accounted for.
My plan going forward.
I plan to work with art until I need to write the last scenes. Animations will be posed intermittently.
I plan to be done with my testing as the final animation frames are produced, thus minimizing the time between the PCs being idle and the start of beta testing/proofreading. As usual, at least two weeks will be allotted for private beta testing and proofreading before the episode can be released on Patreon.
Next up for me is to continue with art on the free-roam I'm working on and hopefully be able to move on to other scenes later next week.
Have a nice weekend, and thanks for reading
Dr PinkCake
If he was doing animations in Blender we would have noticed it right away. The rendering engines and lighting principles in Blender and DAZ are different (for example, look at the Mist game made entirely in Blender). Also, in Blender you can really get water/liquid physics, cloth/hair simulation, etc, which is impossible in DAZ. I don't know how porting from DAZ to Blender works now, but the last time I used custom bridge, it still didn't work perfectly, there were performance sags. Blender is not a very powerful program, it works well up to 2-3 million polygons, then it starts to lag. That's why I prefer Maya, which is the standard for producing cartoons and video game animations. But the bridge in Maya works very poorly, you could say it doesn't exist.
