Function call failed after selecting random map filter - 0.25.10 about community-maps-2

[andy5995]

@N0mi5 Thanks for the report. Which OS are you using? And 0ad version?

I can't reproduce this on Manjaro, 0ad a25. Anyone else?

[N0mi5]

OS: Arch Linux
0ad: 25 build from 17.12.2021

[andy5995]

Did you install the package from the AUR or from the 0ad mod center? Did you have any trouble with the 0.25.9 version?

The only thing I can suggest so far is deleting your 0ad cache (~/.cache/0ad), or renaming it temporarily if you'd rather not delete it. Then restarting 0ad and trying again.

And be sure to have 0ad closed when doing the delete or rename.

If that doesn't work, and If you did NOT install the mod from the AUR, then exit 0ad and try removing ~/.local/share/0ad/mods/community-maps-2 and reinstalling the mod.

[N0mi5]

Mod was downloaded from Github and installed via console (.pyromod file).
Unfortunately none of the above solutions did fix the problem.
Version 0.25.9 however is running absolutely smooth.

[andy5995]

Ok, I can reproduce this when I select the Povorotnaya random map. I'll do a fix and release today. Thanks @N0mi5

[StanleySweet]

Just for the record the Povorotnaya had dimensions that are not a power of two, which might or might not be supported by GPUs. Happened with at least two 0 A.D. alphas, forcing a re-release.

[andy5995]

Thanks for the extra info @StanleySweet .

@na-Itms asked me to open a trac ticket for this, which I did. 6436

[StanleySweet]

Would you be so kind as to expand on what you would expect to happen when faced with such a bad texture?

[andy5995]

Ah.. no I don't think that would be a very efficient use of my time in this case. I'm sure the 0ad development team would be able to decide on the desired result, as you (and they) are much more familiar with how the program should behave.

[andy5995]

@StanleySweet Although I could participate in that discussion and possibly offer useful feedback.

[na-Itms]

Would you be so kind as to expand on what you would expect to happen when faced with such a bad texture?

We should display an error message and we should not load the texture, but the engine shouldn't crash.