fabio

Add this to your local.cfg: vsync = trueEventually it could be made the default (less system load/heat/flicker).

I was playing a skirmish map on r14453 and got the following errors when enemy attached. commands.txt is attached. commands.txt.gz

Thanks, this is a bit unexpected, so 1.0 seems to be working fine for someone.

What we found is that the lobby appear to not be properly working when using gloox 1.0 (libgloox.so.8 - this is the standard version now in Debian/Ubuntu), while it works with 1.0.9 (libgloox.so.11 - this is in the Ubuntu 0ad PPA and possibly other distributions).

Another thing that I would like to see in alpha16 is enabling by default, when possible, advanced graphics settings. This will require user testing on different hw, fixing rendering bugs when found, blacklisting other hw that cannot support it. This should also be done in the early phase of a planned release.

Post the output of: dpkg -l | grep gloox So it's ok under fedora, the problem was on Ubuntu?

It would be nice if we can include the translation work, even better in this early alpha16 phase, so that translators can easily try it from SVN and update translations according to game testing (blind translation without game testing leads to poor results, and merging and compiling by self the translation branch is not for everyone).

I added a note about the new version on the wiki on the first post.

This looks strange. What Ubuntu alpha15 package did you use (the one from the PPA or something else)? How did you get it working when building from source? Can you post the output of: $ ldd /PATH/TO/pyrogenesis | grep glooxfor both the version built from source and the packaged one, specifying again for each version if the lobby works?

This will be in alpha15:http://trac.wildfiregames.com/ticket/1922 http://trac.wildfiregames.com/changeset/14286 You may want to update the planes .

Awesome!

There is a page on the wiki: GameplayFeatureStatus. However I think it is neither accurate and neither up to date .

Nice, I'll have a look if the extension get updated before 10.0.

A bit OT relating to Android, but mesa has a new extensions for querying features of the rendering devices: http://cgit.freedesktop.org/mesa/mesa/tree/docs/specs/MESA_query_renderer.spec http://www.phoronix.com/scan.php?page=news_item&px=MTUwNzc

It looks the lobby uses the port 5222 which may be closed in some environments (e.g. the one I am trying it now). Since the server is managed by WFG can another standard common port be used (80/443?)? Eventually 5222 could also be left open (especially if it is intended to be used by other xmpp clients other than the game itself), the game could try connecting to 5222 and, if it fails after a timeout or get a ICMP destination unreachable, try the other port.

0 A.D. is already available for arm since Ubuntu 13.10.

I agree that while the license compatibility in the game is respected, it is currently lacking precise information on attribution (where the data came from), not only text but also textures, audio and other datas. It was discussed already in the past (e.g. here and here).

I think most of what you need could be done, there are already two modern warfare games experimenting with the 0 A.D. engine: http://www.moddb.com/engines/pyrogenesis

I remember someone in the past wanted to do another experimental AI, using a database to collect and save enemies reactions so to be able to instruct the AI. It was discussed in the forum, but I cannot find the thread link.

Posting the links of the articles would be more useful than pasting all this huge amount of text . Also copy and pasting may be forbidden by the authors.

It looks released now: https://www.archlinux.org/packages/extra/i686/mesa/

Mesa 9.2.1 was just released: http://lists.freedesktop.org/archives/mesa-dev/2013-October/045755.html

9.2.1 will be released in days, so it's good news . Dunno however when Arch will include it.

Good, this is mesa bug tracker, so you may want to add that the game is 0 A.D.. Also you may add output of: glxinfo | grep OpenGL

If you have some time and want to contribute you may want to try a development version of mesa from git (eventually using prebuilt packages, e.g. for Ubuntu see my signature, but you are likely not on Ubuntu?) and / or report the bug here: https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa so that a developer may have a chanche to fix it.