2/12/18 and Memory (Patreon)
Content
Another blog about on the pitfalls in game design today. So the other night, I was working on adding the talking animations for the various expressions. Things were working fine and as expected after the first test, so I started to make similar animations for the rest of the expressions. A few step in, I got a message from Construct saying that the game's memory is getting excessively high. That surprised me, considering I had only added a few animations of about 15 or so frames each. Long story short, the images I had used, even though they only had 100px wide images shown, were actually the same size as the full body portrait that was present in the last demo, with a huge amount of empty space. Intuitively I felt this wouldn't be an issue, but after looking into some documentation I found that even with the invisible pixels, memory is still used. So the game was running animations with large images every change of a text box, and it caused a huge usage of memory.
What I learned from this, is that I'll need to balance quality of images and memory usage better. I'm preparing to scale down the player portrait, and I've already taken steps to make the mouth-sprite object to only include the mouth area themselves.
The next update will be mostly an extension/correction of the last one, and I'll hopefully be able to get it out this week, before the weekend if I plan right. It'll include the talking/blinking animations along with possibly a new text box design.