I think this episode will have the first cheating scenes that will show up in the stats.New sexual conquests confirmed
I don't see anything "artistic" or erratic in DPC's behaviours. He's so far from having an artist's mindset. Instead, he is actually very focused on his goals. Otherwise he couldn't work with this method and consistency for such long periods, with a rather meticulous management of projects and never left to the random inspiration of the moment. I would like to know where this thing of considering him an artist with his head in the clouds comes from.No but seriously, whenever it comes out it comes out and it really does look like it will be great episode. Maybe dev is more ambitious at times or doesn't do everything with best efficiency (mainly trying to make unnecessary high quality animations), but it feels like he works hard and more importantly with a lot of skill. I mean some of the things mentioned in these devlogs, that actually progress and change with each devlog, some other devs would justify 6months work time for (an not just because of hardware limiting rendering, purely coding and writing and branching and stuff).
He's an artist and artists are often difficult persons. But that's what it takes to create these masterpieces. So I give respect where it's deserved and leave the petty grievances for other more outburst posters
To be fair, you can alter it that it goes chronologically. But I had to learn that as well
There were 308 renders plus 150 to pose. Now there are 99 left, and that's it. So in the last week they rendered 259 statics and 5 animation files of unknown length.
Who else would thought that the animations would be a set-back of dev time...Late March update WTFYou must be registered to see the links
I completed posing all scenes this week, and after that, it felt like a whole new world of steps in development opened up, which means I've reached the polishing stage.
I have coding tasks left here and there, but all the scenes (story + lewd + branches) have been posed and written, so I can finally start playing the episode for real and polish the rough areas.
Before playing, I quality-tested the special renders and lewd scenes. I ensured I could reach 100% collectibles on a mini-game playthrough and unlocked all lewd scenes. I then tested that all rewards and lewd scenes were viewable and playable - this step usually results in many bugs, and it was a bit buggy this time, too.
After finishing with that, I started playing Jill's branch. Most of the static renders in the render queue are in other branches or late game, so there weren't a lot of missing content areas.
I reached a part of the episode I knew wasn't coded properly - a big free roam - and fixed all the code to make it playable and work as intended.
While playing, I found issues here and there, be it renders that need to be touched up or re-rendered, code that needs to be fixed, or dialogue that can be trimmed/altered. I don't stop to fix that while playing, as I don't want to lose immersion. Instead, I keep playing and make notes in the code for all these spots. Once I reach the end of the episode, I fix all the issues immediately before playing another playthrough. Rinse repeat.
I just finished my first full playthrough of Jill's branch, and I overall think it was a long and eventful episode. I have made over 100 notes on issues to fix, and I'm currently fixing them before I continue playing.
I also worked some on Episode 12 planning to ensure that I had all the story I needed in Episode 11 in preparation for the season finale. Checking the plan ahead of schedule is a great way to ensure all planned content is considered. And from my plan, I could tell that I don't need more story content in episode 11, which is great.
99 static renders and 61 animations are currently in the queue. It will mostly deplete from now on, except for any renders/animations that need to be re-rendered.
This is how my days will look like from now on until beta testing. I will play, make notes, and fix issues. I have the following tasks left to complete:
SFX & Music
Coding & Other tasks
- Some scenes still miss SFX & Music, and I want to expand the song selections in some areas after playing the episode.
Polishing
- Rooster needs 1-2 more clucks.
- The phone gallery most likely needs a few more images for some branches.
- Phone chats are near completion, but I don't want to remove this bullet point until I've played all branches.
- Add Bios to the entire episode. It's a couple of hours worth of work.
- Add girls and their lewd events to the Stats app. It's less than an hour's worth of work.
- The end of the episode report needs to be written.
- The "Previously on Being a DIK" section needs to be written. It's in the planning stages and will take a couple of hours to complete.
- Discord rich presence functionality needs to be quality tested before being considered complete.
Play through all branches and all conceivable variations to quality test the episode.
Play the episode with a focus on
Fix all issues encountered during playtesting.
- Overall story
- Continuity
- Spelling/grammar/words/dialogue
- Inspecting images and animations
- Music & SFX analysis
- Checking that phone apps/stats update accordingly
- Mini-games (winning/losing)
- Mini-games disabled mode
Add any content that I feel is missing.
My thoughts on all this
Now it's time to cross the t's and dot the i's and ensure that the hard work pays off for me and you. I hope you understand what I'll be doing daily from now on, and I'll try my best to report this process throughout. Polishing the episode will require time, as will the 61 animations in the queue. Once all static renders have been rendered, all my systems will work on animations, and the speed should see an uptick.
This year, I'll be taking December 23-24 and 31 off and work as normal as possible other than that.
Merry Christmas and Happy Holidays to you!
Love
Dr PinkCake
It depends on how complex the animations are. The last month he usually renders 45-50 animation (at least he has the last 2 years).
Almost there sounds like might be long polishing phase but least there lightYou must be registered to see the links
I completed posing all scenes this week, and after that, it felt like a whole new world of steps in development opened up, which means I've reached the polishing stage.
I have coding tasks left here and there, but all the scenes (story + lewd + branches) have been posed and written, so I can finally start playing the episode for real and polish the rough areas.
Before playing, I quality-tested the special renders and lewd scenes. I ensured I could reach 100% collectibles on a mini-game playthrough and unlocked all lewd scenes. I then tested that all rewards and lewd scenes were viewable and playable - this step usually results in many bugs, and it was a bit buggy this time, too.
After finishing with that, I started playing Jill's branch. Most of the static renders in the render queue are in other branches or late game, so there weren't a lot of missing content areas.
I reached a part of the episode I knew wasn't coded properly - a big free roam - and fixed all the code to make it playable and work as intended.
While playing, I found issues here and there, be it renders that need to be touched up or re-rendered, code that needs to be fixed, or dialogue that can be trimmed/altered. I don't stop to fix that while playing, as I don't want to lose immersion. Instead, I keep playing and make notes in the code for all these spots. Once I reach the end of the episode, I fix all the issues immediately before playing another playthrough. Rinse repeat.
I just finished my first full playthrough of Jill's branch, and I overall think it was a long and eventful episode. I have made over 100 notes on issues to fix, and I'm currently fixing them before I continue playing.
I also worked some on Episode 12 planning to ensure that I had all the story I needed in Episode 11 in preparation for the season finale. Checking the plan ahead of schedule is a great way to ensure all planned content is considered. And from my plan, I could tell that I don't need more story content in episode 11, which is great.
99 static renders and 61 animations are currently in the queue. It will mostly deplete from now on, except for any renders/animations that need to be re-rendered.
This is how my days will look like from now on until beta testing. I will play, make notes, and fix issues. I have the following tasks left to complete:
SFX & Music
Coding & Other tasks
- Some scenes still miss SFX & Music, and I want to expand the song selections in some areas after playing the episode.
Polishing
- Rooster needs 1-2 more clucks.
- The phone gallery most likely needs a few more images for some branches.
- Phone chats are near completion, but I don't want to remove this bullet point until I've played all branches.
- Add Bios to the entire episode. It's a couple of hours worth of work.
- Add girls and their lewd events to the Stats app. It's less than an hour's worth of work.
- The end of the episode report needs to be written.
- The "Previously on Being a DIK" section needs to be written. It's in the planning stages and will take a couple of hours to complete.
- Discord rich presence functionality needs to be quality tested before being considered complete.
Play through all branches and all conceivable variations to quality test the episode.
Play the episode with a focus on
Fix all issues encountered during playtesting.
- Overall story
- Continuity
- Spelling/grammar/words/dialogue
- Inspecting images and animations
- Music & SFX analysis
- Checking that phone apps/stats update accordingly
- Mini-games (winning/losing)
- Mini-games disabled mode
Add any content that I feel is missing.
My thoughts on all this
Now it's time to cross the t's and dot the i's and ensure that the hard work pays off for me and you. I hope you understand what I'll be doing daily from now on, and I'll try my best to report this process throughout. Polishing the episode will require time, as will the 61 animations in the queue. Once all static renders have been rendered, all my systems will work on animations, and the speed should see an uptick.
This year, I'll be taking December 23-24 and 31 off and work as normal as possible other than that.
Merry Christmas and Happy Holidays to you!
Love
Dr PinkCake
He also hade 2 scenes left to pose last week, meaning he might have added animation. So we don't know how many he finished.
He plan it for the animations to be finished in time for when his manual workload is done, because he hates the idea of the computers not doing anything while he works. It's a waste of time in his mind. So his schedule is calculated for the renders to be finished is time for when the polishing is done.
There is still hope for January 2025 release date albeit at last week of JanuaryYou must be registered to see the links
I completed posing all scenes this week, and after that, it felt like a whole new world of steps in development opened up, which means I've reached the polishing stage.
I have coding tasks left here and there, but all the scenes (story + lewd + branches) have been posed and written, so I can finally start playing the episode for real and polish the rough areas.
You can only react a certain amount of time in a day."Reaction limit"? WTF is this bullshit?!!!
There a way around it by deleting catch however if your like me and forgot your password don't try it"Reaction limit"? WTF is this bullshit?!!!
Speak for yourself, will you?
Macky009 right now
Each time I read DPC saying something like that, I can't help but think that DPC will waste more time with more minigames
It will interesting If DPC finally discloses the use of the cheating points, but I'm afraid many of us will have to play episodes 9 and 10 again to create "cheater paths" or "totally clean paths"
The first times I used the search function here I ended searching in google adding f95zone
(Until i found out the advanced options)
I understand your optimism and we all want the game to come out as soon as possible. But, unfortunately, ep11 will not be released in December (as indirectly confirmed by DPС himself today) or in January.
Episode 12 won't be released until 2026. We have a year and a half to make those runs.
Looks like that could end up being spot on, there will be a uptake in people hoping for a February release
Since he seems to have a little more time to polish/take notes of bugs/etc. before his animation queue runs out this time, there is a slight chance he'll only need 2 weeks for beta testing again. That's why I would still say late February/early March for release. It will all depend on how long the beta testing takes.
This is true, you CAN set it to filter by newest first but it's not an intuitive filter, you have to go into your profile settings to set it as your default.
