Stan`

How do you find out which one is slowing the game ?

They are text files so in theory you can.

Seems either the file isn't the one that happened during the crash (it's overriden each time you start the game) or that it doesn't even have time to log the error. If you want to use AO you need two UVMaps on your mesh

Could you share the path, maybe it could be added to https://gitea.wildfiregames.com/0ad/0ad/wiki/GameDataPaths.md

Hey @Jackerino I would need to see the mainlog.html. Or at least see the actor file. The only things I know that might crash badly atlas would be - Using AO with one set of UVMap - Using AO with animated meshes - Something else, but I need the mainlog for that.

What seems to be the problem?

That's right.

Mmh then maybe the installer doesn't install it anymore (or never has cc @Itms) You can grab the exe from here https://trac.wildfiregames.com/browser/ps/trunk/binaries/system

It only uses VisibleClasses and Classes IIRC.

Don't forget to run 0ad/source/tools/spirv/get-nightly-shaders.sh if you want to use Vulkan.

What should they build? The AI uses the building classes to know what to build next.

Depends, on what your OS is. It's usually next to your pyrogenesis executable.

GPU skinning requires restart IIRC. And that's definitely the symptoms for it.

Yeah.

For rigged meshes prop points should be added to the armature unlike normal meshes.

That's just Atlas and the actor editor. @trompetin17 is rewriting it using the engine GUI.

No threads are dispatched on other cores by your os. That's the point Maybe but that's a very hard thing to split since there are a lot of relations to take into account and the thing you want is interaction. You need to find a way to isolate systems like the pathfinding calculations which are gathered then dispatched on multiple threads.

Js isn't threaded but the pathfinders and other systems are you can see what the threads are doing using the web page profiler 2

What OS are you on ?

Hey, Thanks for the suggestion, however the handling of available payments is not handled by us but rather by SPI, which currently does not accept that way of payment as far as I know. Maybe they negotiated with them since they are patroned by them as well, or maybe they have another account.

There are some issues with building from sources though, mainly the sheer size of the repo, and since the assets are not cached, it will take another 2 extra GB of space. But other than this you should be good. Regarding the flatpak it's maintained by us, so if it's the content rather than the technology itself that's the issue, you are safe with it.

The general structure of the civs make them generally playable by the IA. Unlike say, Hyrule civs, which needed their own IA.

Due to the nature of the game, the Android app would have to compute the game, which means you should technically still be able to play it. There was an android build in the past, but it's unmaintained.

I've reached out to him. We'll see.

Gpu skinning is broken on some GPUs. Will hopefully be fixed when A27.1 comes out