New Look!

LostVectors.com now served with Blogability. LostVectors.com is constantly evolving. Recent site enhancements allow for better organization of news updates and devlog entries. It’s now even easier to maintain the site so you should expect to see more frequent news updates. New to this site is the ability to directly comment on news articles. Feel free to us know what you think. Continue reading

AS3 Memory Fail

I’ve been too busy to update the devlog recently but I have in fact posted new content to Bowmaster Winter Storm every Friday for the past few weeks. Go check it out if you haven’t taken a look lately.

www.lostvectors.com/winterstormbeta

I’ve had some recent major triumphs, some mini defeats and mini triumphs lately. In the not so distant past I had some issues with a memory leak in Winter Storm. After much investigation and some thrashing I decided it was time to do some much needed refactoring. At this time I still had no real idea where the cause of the leak was. Continue reading

Bowmaster Winter Storm Beta Update 0.1.0.2

www.lostvectors.com/winterstormbeta

There’s some cool new upgrades I added to help defend against those pesky elemental dragons. Introducing the fire and ice flak bomb upgrades. These work just like the regular flak bomb but now harness elemental damage which should prove useful against enemies weak to specific elemental attacks. Tip: Use fire flak bombs against ice dragons.

Continue reading

Tell Me Where It Hurts Part 3: Security Checkpoints

This memory testing is quite the bug hunt. I’ve been testing between two computers and two browsers. I’ve been patting down every game object for illegal memory stashes. Offending code blocks are stripped and searched and sometimes even completely exterminated. Progress is being made little by little as I debug and optimize while innocent code is made to suffer inconvenient slow performing test operations.

Continue reading

Tell Me Where It Hurts Part 2: Not (All) My Fault

So after doing some further tests I was able to pinpoint code that would result in memory leaks. The code itself looked harmless and functionally it worked.

I narrowed a leak to a “doSomething” function in my Util class. I knew it caused an error because when I turned the function into a no-op the leak went way. So I knew that something in that code was causing the leak. But just looking at it, it made no sense whatsoever why there was a leak.

Example original code:

Continue reading