Itms

Hi @little Guest, for your "issue 2", did @vladislavbelov send you the modified test binary mentioned in the other thread? As far as I can see, Vlad went inactive before fixing this specific crash, so it is still an open issue. Thanks for the reports.

Hi Loic, this is not how it works. We release source packages of 0 A.D. that can be included by package managers (i.e. volunteers of the community of your Linux distribution), not by us, following processes and policies that vary from distribution to distribution. I assume the Linux VM on ChromeOS is Debian-based. Debian does not include new versions of 0 A.D. in their stable release. 0 A.D. is up-to-date in the "testing" and "unstable" versions, and the "testing" will be released rather soon. You can read https://www.debian.org/releases/proposed-updates for more information. Other distributions, less focused on stability, provide updated versions of the game much faster after we release them. There are alternatives for installing the game on Linux outside the distribution's package manager. You can try the Flatpak or the Snap. Of course, you can also build the game from the source we release.

The Release Candidates are available for Patch A27.1 You will find them at https://releases.wildfiregames.com/rc/ with the -rc1- infix. The list of fixes with respect to Alpha 27 are updated in the top post of the thread. The bug with flood maps is not being worked on, so it will not be fixed in A27.1, we do not wish to delay the patch release further. We may do a A27.2 for this issue depending on timing. The OOS experienced by ffm cannot be reproduced (after investigation in PM) and may have been caused by the local compilation environment. Let's keep eyes wide open for this one during the testing of RC1. Thanks for your help!

Bonjour damale, ce n'est pas un bug, la traduction française était incomplète au moment où nous avons sorti la version 27. La phrase que tu montres en anglais sur la capture d'écran n'a été traduite qu'en février par exemple. La traduction française est toujours complète d'habitude, mais nous avons découvert en décembre qu'un traducteur (peut-être un bot) avait juste copié-collé l'anglais dans les traductions en français pour énormément de contenu. L'équipe de traduction croyait donc que tout était traduit. Elle n'a malheureusement pas eu le temps de re-traduire tout ce qui manquait avant la sortie fin janvier. N'hésite pas à contribuer à la traduction sur Transifex si tu le souhaites: https://gitea.wildfiregames.com/0ad/0ad/wiki/Localization

Hi @Grautvornix, I have updated the mkensis executable on the builder for installers. I have generated a test installer for the upcoming 27.1 release. Could you try and see if this one starts? https://jenkins.wildfiregames.com/job/0ad-patch-bundles/13/artifact/0ad-0.27.1dev-win32.exe

Hi @ffm2, thank you very much for the steady test results. It will be far easier to analyze them without mods on your side, no worries about playing with others using mods. I had indeed missed #7635, I understand better now. I am going to take a closer look at your latest OOS report during the week and I'll get back to you.

Currently, the RangeOverlayManager is serialized, so a difference will create OOS. Take a look yourself at the difference between the two oos_dump.txt files.

Thanks for the report, but the dump difference shows that you have a behavior difference in GUIInterface enabling range visualizations (for attacks, auras, and healers). This is definitely caused by one of your mods (I suppose it's Ricci's "rangedoverlay" mod, but if you're the one OOS, it can be one of your mods). You folks should stop abusing the compatibility checks system, or at the very least test RCs without mods.

Is it already a known issue? If not, please open a ticket on Gitea, if yes we'll try and take a look.

In the bottom of the main menu, it should display (release-a27.1, 68d99) instead of (release-a27, 8c96b)

Hi everyone, We are preparing the first "patch release" of 0 A.D., now that our workflow allows us to do that. We need your help testing it! What is a patch release? A patch release is a minor release of 0 A.D., bringing a few selected fixes from the development version into the latest release of the game. All fixes of the patch release are already present in the development version (the future Release 28). There are two important aspects to a patch release: Patch releases are OOS-compatible with major releases. If your friend has not heard about the patch release, or cannot install it for whatever reason, they should still be able to play multiplayer with you. This limits the kind of fixes we can include in a patch release. Patch releases are prepared on the side, and do not take precedence over our work towards the next major release. We prepare and provide patch releases as our resources allow. This limits the scale of the fixes we can include in a patch release. What is the current status of A27.1? We have setup all the infrastructure for generating patch releases, and a first testable version is ready for you. In A27.1 are included: a fix for the large performance issue observed by some players on older hardware several small performance improvements in the calculation of simulation hashes (related to multiplayer stuttering) a fix for modifying your lobby password when you have an uppercase letter in your username a fix for the distorted 3D models with GPU Skinning fixes for crashes with Vulkan and/or with GPU Skinning a fix for changing player perspective in replays a fix for an out-of-memory crash in the JS engine when generating random maps a fix for the game crash on pressing Fn key a fix for a crash in Atlas when the map generation fails a fix for a memory leak in the renderer fixes for multiplayer port forwarding package fixes for Linux desktop environments various build fixes for Linux (some sent by package managers) A27.1 will not include: a fix for the Britons OOS on rejoin: unfortunately it would make A27.1 incompatible with A27 (against rule 1 above) any modification of simulation hashes: it could remove stuttering entirely, but it would make A27.1 incompatible with A27 (against rule 1 above) incremental simulation hashes: those improve stuttering as well, but are too complex to backport (against rule 2 above) How can I test it? You can download the release bundles of A27.1-RC0 at https://releases.wildfiregames.com/rc/ Please report below any crashes or new issues (that weren't already present in A27, unless they are listed as allegedly fixed above). Thanks for your help and support!

Hi @ffm2, getting back to you after taking a closer look - you have actually detected a real OOS which was also observed by @real_tabasco_sauce. This would be a correct way to test the branch (although you would lack translations and shaders), which shouldn't create an OOS in itself. Taking a closer look at a fix I had included in the branch, that fix is OOS-incompatible with 27.0. So I removed it from the branch. Your commands file was useful for me to assert that this specific fix was creating an OOS You can test the branch again if you wish, or you can wait a couple days before we distribute testable bundles of 27.1.

Those dumps are wildly different and are probably after the original divergence. The commands.txt from the host (not the rejoining player) would be needed. The 27.1 branch is still a work in progress and there is a large risk that you had some leftover files from the main branch or from the HEAD revision of the nightly build if you just switched branches and recompiled. I'll let you know when you can test 27.1 with correct instructions when it's ready, but as is, this report is probably a false positive.

I haven't looked into it indeed, but haven't abandoned the idea. There is something afoot here with the version of SpiderMonkey used in A27, which is supposed to work on Win7. That said, A28 will not support Win7. So all the discussion above is still relevant for the future