- Jun 30, 2018
- 3,380
- 9,133
- 728
i love it whenever people being reasonable - appreciate it, sir.Yes, I'm looking at manually dumping animations from memory. Most animations get preloaded and dumped in code between the day sections already.
This is the first time I heard about someone unable to play due to RAM issues, and it is from an older machine. If it's his hardware slowly kicking the bucket, then I might be chasing ghosts.
The licking requirement got patched out already, I just forgot it was a thing in this version. You need to finger her x times before getting to the beach event, also, so it's not an unprecedented progression in the game. I'll likely patch that out in a future progression overhaul. This isn't a kinetic or even a branching AVN, so the game having progression hurdles being a negative thing isn't really feedback I can work with. There's an Easy mode now as well, so progression is very easy if you want it, save for the few things I'm patching out, like the licking/fingering requirement.
I didn't even expect "sudden changes", i just wanted to voice my personal view of things - but as it seems, my thoughts were not only mine XD.
About the memory usage: it happened to us too. We didn't even know that RenPy internally converts all images into RGBA bitmaps
I man: who could even guess that a 300 kb render could end up with 8 MB in RAM? Normally, that's still no issue, if you use 1 render to show, maybe 2 on screen (1 as overlay). But as soon as you work with sprites, or if you use different assets on different parts of the screen at once, it might easy end into a RAM-mess.
It still can have different other reason, but if i would have to bet on one of them, this one would be my choice #1