Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 593

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/btanks/htdocs/blog/wp-includes/classes.php on line 710

Strict Standards: Redefining already defined constructor for class wpdb in /home/project-web/btanks/htdocs/blog/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/btanks/htdocs/blog/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/project-web/btanks/htdocs/blog/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/btanks/htdocs/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/btanks/htdocs/blog/wp-includes/theme.php on line 576

Warning: Cannot modify header information - headers already sent by (output started at /home/project-web/btanks/htdocs/blog/wp-includes/classes.php:576) in /home/project-web/btanks/htdocs/blog/wp-content/plugins/LangSwitch/langswitch.php on line 587

Deprecated: Function eregi() is deprecated in /home/project-web/btanks/htdocs/blog/wp-content/plugins/captcha/captcha.php on line 1429

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /home/project-web/btanks/htdocs/blog/wp-includes/plugin.php on line 311
Battle Tanks » Blog Archive » BattleTanks-0.9 was just released!
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Captcha::css() should not be called statically in /home/project-web/btanks/htdocs/blog/wp-includes/plugin.php on line 311


Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 19

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 28

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 30

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 32

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 33

Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 19

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 28

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 30

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 32

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/btanks/htdocs/blog/wp-includes/functions.php on line 33

BattleTanks-0.9 was just released!

Have been long since last release, isn’t it? Today we’re releasing major engine update to Battle Tanks. This update comes with brand new server! Unfortunately we have not finished any new maps, it’s still work-in-progress. All volunteers are welcome!  If you’re feeling that you could help, do not hesitate to contact us – we’d provide any help you need. Also I’m starting to document everything, but enough plans. Here’s some notes about 0.9 release:

  • We prioritize internal network queue improving overall multiplayer experience.
  • New version of clunk library: MDCT, HRTF, SSE and other obscure words :)
  • Better compression - new release is about 30m!
  • Player profiles support.
  • No need for DirectX9 anymore. 3d-acceleration was ported to DX8.
  • Fixed ancient bug when boarding a vehicle could become very tricky without rolling - now it could be done very easily.
  • Lot of performance optimizations, better collision tracking.

Note for package maintainers: we have renamed libbt.so to libbtanks_engine.so due the conflict with BlackBox (whatever it is).

https://sourceforge.net/projects/btanks/files/

6585 Responses to “BattleTanks-0.9 was just released!”

  1. Sorex Says:

    А почему исходники только 30 Мб? 0.8 были 60 Мб!

    Не люблю поправлять но, “караван”, а не “корован” :) Или там коровы? :)

  2. whoozle Says:

    Корованы: http://lurkmore.ru/%D0%9A%D0%BE%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D1%8B#.D0.9F.D0.BE.D1.8F.D0.B2.D0.BB.D0.B5.D0.BD.D0.B8.D0.B5

    По поводу размера: мы оптимизировали графику и музыку.

  3. blackbox Says:

    http://en.wikipedia.org/wiki/Blackbox

  4. lezer Says:

    error
    http://i078.radikal.ru/1001/de/428be866e6fd.png

  5. whoozle Says:

    ээээ, а что такое D? раздел на винте? флешка?

Leave a Reply

You must be logged in to post a comment.