January 28th, 2007 by Sharky

kick it on GameDevKicks.com 

I’ve just uploaded a new build of “Air Legends”.

The only change in this release is that I’ve incorporated the improved collision detection that I’ve been blogging about so much lately. If you’ve played the previous versions I’m sure you’ll notice it’s a lot better now.

You should be able to survive much closer flybys now than before.  More of your bullets will miss now. For obvious reasons really – the collision zones are much tighter and more realistic than before.  But also, and this one was slightly unexpected,  some bullets will fly right over or behind a wing missing altogether.  This is not a fault.  Wings are narrow – bullets are small and could go either side of a wing depending on the planes roll.

You can get the new release from the Latest Builds page here.

Average Rating: 4.6 out of 5 based on 198 user reviews.

7 Responses to “”

  1. zygote Says:

    The latest build crashes upon load for me.

  2. Ultrahead Says:

    Runs ok here … the collision accuracy is great … maybe at the bottom side of the “playfield” you could add some terrain, and then when the plane fall and crash they crash against something so they explode …

  3. Sharky Says:


    Dang it. I’ll look into it.

  4. Sharky Says:

    Oh that’s a relief Ultrahead.
    I wonder what the problem could be for Zygote?

  5. Ultrahead Says:

    Maybe Zygote can give you more info on how it crashes.

    Did you change something in the settings file since your previous build?

  6. BlackICE Says:

    I also get an error on start, unfortunatly its rather indiscript.

    “Legends has encountered a problem and needs to close. We are sorry for the inconvience.”

    All I can tell you is that once you click close, you briefly see a full screen window which looks white and covered the entire screen, start menu and all.

  7. Sharky Says:


    Thanks BlackICE. Does this happen after the selecting from the Title/Menu screen? Or before ANY screen at all has shown?

    This is really very strange. The only thing I can think of that has changed is my new collision detection logic.

    But since this only happens on some peoples machines I’m thinking it has to be in some way hardware related. I don’t mean that there’s anything wrong with your hardware – just how my game might behaive with it.

    With that being the case the only change low-level enough to be that would be my class for rendering the spheres based on a Settings.xml setting.

    That will be switched off by default, so no sphere rendering would occur, but I think I may still initialize the class on startup.

    I’ll look into it folks.

Leave a Reply