December 15, 2010

SuperTuxKart 0.7 release candidate 2 released

We have just uploaded a second release candidate. Major changes include :

  • Asian fonts are now included in the package.
  • Several memory leaks have been fixed (which had caused problems with music and sound effects)
  • Some tracks were improved to disable unintentional shortcuts and incorrect rescues.
  • Some minor bug fixes.

We also updated the translations, but not all translations are complete yet. We encourage all translators to complete their translations, as the strings are now frozen.

Testing and feedback welcome!

Cheers, Joerg and Auria
Well you know what to do: test it and comment on it like if it was the real deal - 0.7 is coming really soon now, possibly within the next week or so! And we need your help to find the odd little bits here and there that needs to be fixed. Please report your findings in STK´s bug tracker, and mark them as high priority if it´s a crash or similar show-stoppers. This way, our dear developers will ensure that it gets prioritized and hopefully fixed before 0.7. Keep in mind that they need as many details as possible, so please include in your report system info, where it happened, if it´s reproducible, and backtrace if you have one.

Let´s help make 0.7 rock solid! :)


  1. I'm having problem with my xbox360 gamepad

    digital pad are TOO sensitive and in menu move twice position at time.

    more serious:
    I can't use RT and LT (analog button) to respectively accelerate and brake. When I set it happen someting like I'm keep pressing the up botton (sometimes) in the menu.
    an in the game the kart accelerate without pressing any button.

    I would like to help, tell me what I can do.


  2. Hi Fabio,

    you didn't tell your operating system. I would suggest you run STK from the terminal like this :

    supertuxkart --gamepad-debug

    (This is for Linux; it will be slightly different on Windows or OSX.)
    Then play until you see the problem, then quit and send us the terminal output, this will help us debug what happens.

    Also, ideally, bug reports should go on the forum or on the mailing list, the blog isn't too appropriate for that