Jump to content

Itms

0 A.D. Project Leader
  • Content Count

    2,151
  • Joined

  • Last visited

  • Days Won

    95

Itms last won the day on March 27

Itms had the most liked content!

Community Reputation

2,382 Excellent

About Itms

  • Rank
    Natural Philosopher

Previous Fields

  • First Name
    Nicolas
  • Last Name
    Auvray

Profile Information

  • Gender
    Male
  • Location
    France

Recent Profile Visitors

3,669 profile views
  1. I don't know how was the support for arm64 for SM38. Our version never worked there, but maybe it could be patched (it's too late for us though). We can help to find patches to bugs if they exist, but that will need some tinkering from Dansasbu. But this is a good opportunity to improve our arm support for A24! Updating SVN is not needed to test the patch.
  2. Here is a patch: https://code.wildfiregames.com/D2244 To apply it, you should use arcanist. If you are on Debian buster or later, just install it from the repository. Else follow these instructions: quick start. Then, you can create an account on Phabricator (that will allow you to comment directly on the patch, to be pinged if we need some information, etc). Then, in your terminal: arc install-certificate in order to use arcanist with your account, and then arc patch D2244 in order to apply the patch. You can then build with ./update-workspaces.sh --with-system-nvtt cd gcc make And please report here or on the patch directly if you discover other bugs Thanks for the report, and in advance for testing and playing!
  3. Hi! You seem to have hit this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1266366 What is needed is to patch spidermonkey with it, and when it's committed, then you will be able to build SVN like you tried to do, with Ideally we would have downloaded the latest bundle from the esr branch, instead of the release candidate from the SpiderMonkey devs, but they are not available anymore for SM45. So it would be better if you could test the patch that I will make, in case we need to patch more bugs. Are you comfortable with using our patch review platform? Else I'll provide the patch here and will give you instructions to test it. Thanks for the report
  4. I received the money on the 20th of June and sent the money to all the other participants today.
  5. @gameboy Check all the boxes like in the screenshot and click OK, then update your copy and rebuild.
  6. Hi gameboy, the Windows autobuild is stopped for a few days for an upgrade. You can build the game if you want to get the fix! Sorry for the inconvenience
  7. Hi, yes, the autobuild is down for some days, we'd like to build with VS2015 on it. Happy to see it is that useful for you, we'll try to make the downtime as short as possible
  8. Looks like a very nice tool indeed. Don't hesitate to add it on the wiki! The bottom of the EngineProfiling page is probably the best place for it.
  9. Done! Thanks @Alex from Intel for the work and the write-up! We'll let you know about improvements to these parts of the code
  10. Dear members of the treasury committee, With some delay, please find attached the details of expenses engaged for FOSDEM 2019 in February. Five members of WFG were able to attend and to spread the word about the game. Just like last year, I propose to have SPI send the money to me, which I will immediately forward to the attendees, in order to minimize the number of transactions. We are looking forward to reading your reply and we are happy to answer any additional question you might have. Itms, on behalf of the attendees. FOSDEM-2019.pdf
  11. If it's the TLS bug, we'd be happy to have a backtrace, because currently it only happens on macOS (fixed in the development version) and on recent Fedora (not yet fixed, so every bit of extra information is welcome).
  12. He used an old promotional video from WFG instead of trying the game
  13. Common Mistakes: name/label confusion in mod.json - for instance https://0ad.mod.io/ja-lang "name" should be a lowercase identifier, it usually matches the URL of your mod on mod.io: for instance "ja-lang" "label" is a human-readable name, it usually matches the title of the mod on mod.io: for instance "Japanese Language Pack" top-level extra directory. Your zip should contain directly mod.json and the rest of the files, it should not contain a sub-directory with the files. The best way to avoid the issue is to use the archive builder. In order to test whether you made the mistake, try opening the mod with 0 A.D. If you land on the mod selection page and your mod was added to the list (appearing in green), things are good.
  14. Welcome! @Doktoreus is still active and looking into some parts of the documentation, but we will never have enough contributors in this area, so feel free to start proposing content and an application. I second elexis in pointing out that we'd like to know which part of the documentation you are interested in (the technical one, or one aimed at players).
  15. Follow the steps in this guide: https://trac.wildfiregames.com/wiki/BuildInstructions to get the development version of the game. No need to build anything. Then, locate the translation files (everything starting with your language code) under binaries/data/mods/public/l10n/. There are a few strings translated using files in binaries/data/mods/mod/l10n/ and binaries/data/l10n/. Put them in your "user" mod (locate it using https://trac.wildfiregames.com/wiki/GameDataPaths), in a folder /path/to/your/mods/user/l10n. Yeah, we could easily package a mod with the incomplete translations on each release.
×
×
  • Create New...