Leaderboard

I'm opening a topic at last for an issue that we discovered a long time ago and that might finally be resolved (opening it to remember to check that it's actually fixed). The issue is that our old collada armatures don't load up nicely in Blender. A change in 2.68 should have fixed this, however now 2.68 can't load those old armatures. A ticket for that has been opened on the Blender Bug Report. Latest update is that it's been closed after a report that "I was getting the same crash with 2.68 on linux64 (whichever revision was packaged with Fedora 19), but the same model imported fine with the latest nightly build. So this issue has probably already been fixed." Ticket is here. I recommend we try again with Blender 2.69 to see if: A- our armatures load up B- they load up nicely.

I decided to start working on image internationalization and localization. This is mostly important for those languages that translate game names, however, any image might need to be somehow modified for a certain locale. The approach I plan to follow is that of The Battle for Wesnoth. In The Battle for Wesnoth, any image can be translated. When the game loads an image, it first checks if within the folder where the image is there is a localization folder with a localized version of that image for the current locale. For example, if the current locale is "gl", and you have a file in "folder/image.png" and a localized version in "folder/localization/gl/image.png", when the game is required to load "folder/image.png" it first checks if "folder/localization/gl/image.png" exists, and since it does exist, it loads "folder/localization/gl/image.png" instead of "folder/image.png". Simple To help translators to keep images up to date, they have a system which basically generates checksums of translated and original images, and if developers update an original image, translators can check in a file that the original image was modified after they localized it the last time, so they know they might need to update the localized image. Another important part of the image localization is explaining to translators how to localize specific types of images. It is important to supply translator with either source versions (for example, in Gimp format) of images, or with detailed steps to generate certain images from scratch. Here is where there is not much I can do, and I need your help. Can anyone point me to an editable version of "public/art/textures/ui/pregame/shell/logo/0ad_logo.png", "public/art/textures/ui/pregame/shell/logo/fundraiserlogo.png" and "public/art/textures/ui/pregame/shell/logo/product.dds" if there is one? What font are we using for "A.D." in "0 A.D." or for "Empires Ascendant"? How are DDS images compressed? (if I save a version modified with Gimp uncompressed it takes 3 times as much space as the original one).

When i took a closer look at pureon's mocks I noticed that the gold i was using was way too yellow, I adjusted the colors to use shades of gold from pureon:

Oh, you are right! I'm looking at the alpha reease but this has been fixed as per http://trac.wildfiregames.com/ticket/2110 Thank you, sorry about the noise.

Those are pretty nice! I especially like the scrollbar. Might you be able to post the svg files so I could take a closer look?

It's on our list of features we'd really like to have, so it doesn't have to go through Project Governance, but it's also not high on our priority list. There are many other important features/improvements that take priority, such as optimization (1st priority), and other missing gameplay features (Auras, Capturing, AI, Naval, etc.)

Hi Michael and Team, I finished the draft of the suggested sounds. Please note that I have create the sounds for five. You can hear the whole package following the link below https://drive.google.com/folderview?id=0BxjQhhuNIo6UcGxhQ2FUdFpoV3c&usp=sharing The ending '_start' means "building selected" The ending '_done' means "building completed" Look forward for your feedback. Matias