- Feb 19, 2021
- 951
- 2,503
- Thread starter N7
- Start date
-
- Tags
- 3dcg anal sex animated big ass big tits cheating combat creampie dating sim exhibitionism female domination female protagonist footjob graphic violence groping group sex handjob humiliation humor interracial lesbian male protagonist management masturbation milf multiple protagonist oral sex point & click prostitution puzzle romance sandbox sex toys spanking strategy stripping teasing titfuck turn based combat vaginal sex virgin voyeurism
- Aug 9, 2017
- 1,124
- 2,986
Ex-prostitute, maybe. My son, your girlfriend looks a bit dead to me. She's got maggots in her mouth for Christ's sake! Get that corpse off my lawn!
Oh yeah Jade! Let's see if your girlfriend enjoys anal like her mother!
You (and all the others) should use the SEARCH function before asking about updates. It is there for a purpose.
- Jan 20, 2022
- 844
- 22,840
You 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
- Some scenes still miss SFX & Music, and I want to expand the song selections in some areas after playing the episode.
- 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
- 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
- Dec 14, 2019
- 1,400
- 1,517
To be fair, the search function is horrible. You get 50 pages of every time the word "update" was mentioned during the last 5 years, in random order. Unless you're well familiar with how to tweak it, you'll be pulling your hair using it.
- Sep 27, 2020
- 2,240
- 6,052
- Apr 5, 2017
- 328
- 3,453
61 animations left...
Good God, how I hate being right, this update won't come out before early March.
Good God, how I hate being right, this update won't come out before early March.
- Feb 16, 2024
- 1,343
- 2,232
Basically, release will be two weeks after the animations finish rendering.You 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
Wow ok. looks like we were all wrong. reading that I'm thinking mid January release? err on the side of caution and say 24th
- Sep 26, 2023
- 1,173
- 6,512
New sexual conquests confirmed
- Nov 24, 2021
- 262
- 445
- Aug 9, 2017
- 1,124
- 2,986
That's true. I take for granted that people do the same as me: I always set order "by Date" in the preferences in every forum I use.
- Dec 14, 2019
- 1,400
- 1,517
Looks like he could start polishing a week early. That good.You 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
Let's hope the polishing and beta testing goes well.
- Feb 16, 2024
- 1,343
- 2,232
- May 28, 2019
- 1,030
- 2,586
I see how it is, gonna take 23-24 off to setup cool release announcement for 31st December which he will take off to celebrate game realease with us all I can't waitYou 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
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
- Aug 31, 2024
- 410
- 2,419
Last week, there were 308 renders and 66 animations in the queue. Now there are 99 statics and 61 animations. That is 5 animations and 209 statics rendered in a week.
Bad speed, but probably after he's done with the statics he thinks the speed will increase.
It's hard to make predictions, but I'm still thinking about a release in February.
61 animations is 7 weeks of rendering. That is, the rendering will be completed on February 7. If rendering is completed in February, the game will be released in March. If rendering is completed in January, the game will be released in February.
- Aug 31, 2024
- 410
- 2,419
I think this episode will have the first cheating scenes that will show up in the stats.New sexual conquests confirmed
Otherwise, making stats only for one branch of the Others....
Either there will be 2 or 3 threesome scenes in this episode.
- Aug 9, 2017
- 1,124
- 2,986
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
He did not made "unnecessary high quality animations", he made animations with the same quality as before, only at 60fps instead of 30fps. That's just more fps, longer rendering time, not higher artistic quality.
He has planned everything and aims to achieve certain goals. Releasing updates in shorter times is not a priority for him but not because he is a dreaming artist, but because he has carefully weighed the pros and cons.
I agree he really works hard and he works fast compared to most (maybe all) his competitors, but the fact is that almost all his hardware is always occupied only for one task, animations, so the development time with the same output of gameplay has been quite stable since the first episode. This despite having got two major upgrades in his workstations. For what he produces, he's been very efficient as a developer, since the beginning. I don't see it as a matter of workflow efficiency. It's just he chose to produce a lot of content, a lot of extra features (minigames, cutscenes, 60fps animations...) that need extra time to be done.
- Nov 21, 2022
- 241
- 411
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.