UPDATE: If you still experience this problem after downloading version 1.03, please let me know.
It’s the bane of any coder, an error that occurs without consistently and without cause. One that can’t be recreated and know conditions can be identified. I can’t tell you how disheartening it is.
I’ve been struggling with out-of-memory exceptions during development, trying to understand the pattern PSM uses memory and the conditions that cause it to run out. See PSM runs on a virtual machine, an emulator which runs on the operating system. I believe this to be the reason for much of the randomness to it. I wasn’t able to establish a consistent pattern so I instead reduced the use of memory by a significant amount. This kept the game from crashing for me for several play-throughs. I fixed it… or so I thought.
Now my old friend out-of-memory exception is back and is making this game a frustrating experience for some users. Of course it doesn’t matter how unfairly random it is for me. It’s my job to fix it. People paid for a product and it’s ridiculous that it doesn’t work. If I was on the other end of this I would be furious at the developer. But I’m the developer and I can only beg for mercy!
I’m looking into the matter now and will find a way to address it by the next update (not the next update which fixes the slowdown issue but the one after that). If no solution is found, then I have a backup plan – gut Swellsville. Reduce the town size so that it is less likely to cause an out-of-memory exception. That’s how I fixed it before but perhaps I did not go far enough. Of course, I’d hate have to change a significant part of the game like that, so I hope there is an alternative solution. Since I have to wait for the next update cycle before I can submit a new build, I have time to find one.
Did your game crash in Swellsville? Please let me know if it did or did not.