Contact Info / Websites
Every now and then I see another game that makes me want to shake the developer and scream. I'm sick and tired of people posting these games with highly-polished graphics and gameplay that just break and fall apart the moment you play them for more than five minutes in a sitting. Sometimes I'll rant about programming best-practices in the review itself, give the programmers some terms to Google, but by then it's always too late. Everyone knew this shit back in 2004. What happened? These bugs are inherent to Flash itself. If you don't know how to work around them by now, you need to educate yourself.
So here. Here's an image showing exactly what happens when you develop something the quick-and-easy way in Flash and then just trust Flash not to fuck it up when the game's been running for a while. Also, a general overview of how to fix. These are the mistakes I keep seeing so-called professionals make over and over again here on Newgrounds. They make your game break, slow down, freeze or just plain start behaving strangely beyond some point. They are show-stoppers. They are mission-critical points-of-failure. You will not anticipate them, because they are caused by weird shit internal to Flash. You can only stress-test for them, or engineer around them by coding things the hard way.
To learn how to fix, Google all of the following search terms and read, read, read:
- AS3 bitmap display programming
- AS3 delta timing
- AS3 object pooling
- AS3 performance optimization
- AS3 garbage collection problems