hyperion

Why would you mind the unverified label for flatpack? Also what does native mean? After all the exe is a native x86 binary and flatpack isn't a native distribution package. Using wine gets you a 0-day trusted binary path at basically no cost for wfg. The cost for a release I'd argue is already in the unhealthy territory. I fully understand that this might not be the most favorite solution for a small set of users but my standpoint is providing the sources is good enough and beyond that is adding bells and whistles.

Few years ago I tried and hwdetect triggered an error due to numa not being implemented in wine, the error dialog offered a continue button and so I continued and from there the game ran just fine. If this is still the case just dropping numa detection which we don't make use of in the the first place would allow us to have a viable alternative to offer a "trusted" binary for the impatient beside the just build it yourself (tm). While it is true that a distro might lag a lot, those listed as the most popular were all reasonably fast to offer the latest version in the past as far as I remember.

Have you ever tried running the Windows version available on play0ad in wine?

No, that is really only a mirror. @Vantha just ask an admin to manually activate the phab account. Spam bots are just to common this days and the hurdles placed for them might occasionally affect legitimate attempts at registering.

Created a pull request

We don't strictly need 8 names, I mean I can play against 3 or maybe 4 before I get badly beaten. So in most games a single name per civ would be already enough. Using made up names would undermine the point made by @Stan` which I quite like. So requiring 8 names doesn't sound that great.

Adding more names is an option, removing names ending in a roman number is an option. Not generation an endless list I consider a regression (the engine already supports more than 8 players), tho changing how the list is generated might make a lot of sense. What do you have in mind for how it should work, replace roman numbers with a suffix like (2)?

They are undocumented at https://trac.wildfiregames.com/wiki/ParticleFormat. I just tried to do so but after trying to pass the the captcha about 20 times without success I give up

You might have a much easier time using blender python api, there is also an importer for pyrogenesis https://github.com/stanleysweet/blender_pyrogenesis_importer If you want to write an app based on pyrogenesis I'd say dig into premake and study the ActorEditor for being a lot simpler than Atlas/ScenarioEditor

You can also ask a moderator to split this thread or even submit a patch to phab if you think you have better implementation.

The code needs to generate an endless list of names, could be bot1, bot2 and so on. The improved names here are only for role-playing purpose. If you don't provide an endless list you might break mods or add another thing that breaks should you increase max players. Tweaking the generator is an option but discussing this I consider off-topic (like most in this thread) so I stop here.

As you are a single-player you can just delete the map if you dislike it that much. Or not that hard either, create a mod with an empty file maps/random/pompeii.json.DELETED

Auto queue is just a hook to add stuff to the queue should it be empty, what is shown is basically just the pattern used for adding, not units already in the queue. Filling the queue based on the pattern binds the resources. The AI has already decided to spend the resources this way so binding doesn't matter either. You can also just calculate each round what the AI should do with their res and only queue a single batch if currently empty. In essence you would just run the same calculations over and over as the result wouldn't change. Sure you can mod the AI to be smarter but the autoqueue feature is pretty much useless for anybody but humans.

If the name itself was "Themistocles II" ... Anyway not a bug a as you can't reasonably require sufficient names for any case.

What you show as bot auto queue is just a regular queue. Basically the same you get if you queue up 6 batches a 2 manually. Auto queue for humans only makes sense because we forget sometimes to queue units but that is an issue the AI doesn't have. In light of that your question doesn't seem to make sense to me. Could you elaborate a bit more on what exactly you want.

That's about page size (continuous blocks of memory similar to blocksize for hard disks), paging (or swapping in unix speak) moves pages between ram and hdd. Page size is about efficiency, to small means to much overhead and to large means waste of space. I can't find good docs either, but an article talking about it would be https://www.tomshardware.com/news/how-to-manage-virtual-memory-pagefile-windows-10,36929.html Unfortunately, the use of the term virtual memory in that article is again different than what virtual memory is about (see https://en.wikipedia.org/wiki/Virtual_memory for a somewhat decent introduction) and the statements about minimum and maximum size are almost certainly not true either but alas ...

But only on a 64bit Windows. The 4GB are also referring to virtual memory and not ram per se. Using my numbers from before only 1.5GB would have to "live" in physical ram. After an arduous journey of convincing the search engine (tm) that I don't want to backup files I found it's called paging on Windows and the "swapfile" is called pagefile.sys and hidden and managed for you by default. While Linux just pretends the extra 5.5GB memory exists until it's used (true overcommit) Windows should be able to "page" it according to my understanding. Ofc the 32bit Windows build doesn't use 7GB virtual memory but it's pretty safe to assume that maximum of 4GB is just barely enough.

Was based on svn before A26, closer to A25 I believe. The binary I deleted in the meantime but could be rebuilt, though might have to work around a certain python - sm issue. From my limited knowledge of Windows memory model, it allows sort of overcommit if backed by hdd, maybe sort of dynamic swap is a better term. For me 0ad typically takes about 7 GB of virtual memory on Linux 64bit and some 1.5 GB residential memory. Therefore I think it's very reasonable to assume that a 32bit builds will have trouble with the limited address space but a 64 bit build would work reasonably well with 4GB physical ram even on Windows. So I have no doubt that 32bit is an issue which people might run into occasionally, was just wondering if the last community mod might have moved the tipping point based on recent noise but according to @chrstgtr that doesn't seem to be the case. I think the last notable rise in requirements was with A24 and earlier version should be much less likely to run into this.

There were quite a few threads beside this one and even bug reports recently. Sure this doesn't mean there must be a correlation. Once the game is at max pop there shouldn't be much of additional memory be needed based on game length tho unless there is a leak, so I wouldn't dismiss the possibility. Windows user are rare in my environment so I have not personally experienced this issue at all and hence I can't make any sensible statement of whether it having changed or not other than the frequency of reports.

You can't reasonably do this with pure javascript. If you really need that feature CGUIText class is a reasonable starting point for digging into.

Reports seems to have increased a lot since last community mod release, maybe try without. What should help a lot is reduced map size, less players or lower pop cap.

That stage runs pyrogenesis which is only possible if pyrogenesis is built.

You'd replace build/jenkins/dockerfiles/gcc7-docs.Dockerfile Pipeline to rebuild docker images but missing this one (maybe manually created): build/jenkins/pipelines/docker-reset.Jenkinsfile Pipeline generating docs: build/jenkins/pipelines/docker-docs.Jenkinsfile The ones in svn and running on the CI might not be fully in sync, @Stan` would know

The example set aka the code demo set: binaries/data/mods/public/art/textures/skins/structural/kart_struct.dds binaries/data/mods/public/art/textures/skins/structural/kart_struct_1.dds binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged_heavy.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged_heavy_norm.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged_med.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged_med_norm.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_damaged_norm.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_norm.png binaries/data/mods/public/art/textures/skins/structural/kart_struct_spec.png As you can see there is one for each of no, light, medium, heavy damage.

We still only have damage textures for cart after all those years