3D R Comics
patreon
Chapters and Image Resolution
🕑 Added 2023-02-09 06:30:04 +0000 UTCI did really quick want to touch on a couple of things.
You may have noticed, most images referencing the game now say "Chapter One".
I did decide to 'end' chapter one with day 5, so day 6 is the start of chapter two.
This change is for a couple of reasons.
Primary is this way PC client "chapters" are synced with mobile client "Chapters", and mobile HAS to split at day 5 due to android size limit.
Secondary reason and I think, personally, a much better reason. Is Chapter 2 will be a 4k native client on PC. I am already doing 2k and 4k renders where I can in day 4 and 5 and using renpys scaling so it displays correctly, these renders do look better this way, but not as good as if it was a 4k client.
Now, when this game went up for sale, It was stated chapter one would last till day 10. So to not screw anyone over, anyone who purchased on itch, will get chapter 1 and 2 for that original purchase, and on steam release with completed chapter one, you will also get chapter 2.
and I will figure out pricing for chapters 3 through 6 when the time comes, but I think $10 for 10 days is a fair.
Also. Who the hell is the 8th primary LI? ;) ;)
Edit:
One last thing, I've discussed it on discord recently.
But I discovered an issue in renpy that I am not sure how to fix yet, and its about the timed sequences (Ava's sex scene). They aren't consistent across devices. I discovered it when trying to finish Ava's scene and noticed its no longer in sync on the new monitor. Nothing seems to be stated in renpy's docs about this. but going from a 60hz monitor to 120hz/144hz/165hz, each level causes the scene to play slightly faster then the setting before it causing it to be way out of time with the music, making the entire concept pointless.
Its not supposed to be this way, renpy's timing is supposed to be based on real world time and not fps, my only thought is the transitions run faster even though I am also giving them a specific time to follow, So no solution to this yet. still working on it.
