vladislavbelov

You might take a look at old docs: https://trac.wildfiregames.com/wiki/AndroidPort and related files in the repo: https://trac.wildfiregames.com/browser/ps/trunk/build/android We should have no problem with the arch itself since we build the game for macOS ARM64. I think it might be possible (especially if it can be done in a fork to avoid support cost for us, at least for now).

Hi! It might mean outdated video drivers, could you update them? Also could you attach your logs (mainlog.html, you might find path to them here: https://trac.wildfiregames.com/wiki/GameDataPaths)?

Eh. We had experimental support of Android builds long time ago. In theory it should be possible to make it working again, but we have no people for that.

In the game or in the emulator?

Can you try Vulkan (it needs to use RC builds or SVN, SVN also requires 0ad-spirv mod to be installed)?

I'll remove such users.

That's strange, because the error literally says it can't find vulkan-1.dll. Make sure that you're running the game (pyrogenesis.exe) from the same directory with vulkan-1.dll.

Thank you! I'll try to reproduce.

Then it seems Vulkan RT wasn't installed properly.

Maybe do you have minimal amount of steps to reproduce the crash?

%LocalAppData%\0ad\logs (for example, C:\Users\JohnDoe\Documents\My Games\0ad\logs, https://trac.wildfiregames.com/wiki/GameDataPaths#WindowsVista1011)

Could you attach the crashlog.dmp file?

Usually it shouldn't affect Vulkan. That's interesting, as workaround you might check that file C:\Windows\System32\vulkan-1.dll exists. And if it does you could copy that file to the 0 A.D. binaries folder (near to pyrogenesis.exe): path/to/0ad/binaries/system/.

Unfortunately that option doesn't affect CPU cost of a pipeline state switches.

Yes, it's not a fast process. We're pretty limited in available developers but we're still moving forward. It looks similar to #6658, so it might be a template problem rather an out of memory. GDB is a debugger, it also allows to retrieve a stack information.

It's not entirely correct. OOM crashes highly depend on a map. I don't remember any local crash because of OOM during first few minutes on a random map. It's a complicated process and we're working on that: #2611 I successfully generated that map in a "Giant" size and it consumes 1.6 GB (there is a room before 3GB/4GB depending on a Windows version) on Windows when revealed and the whole map is visible. So a reason of your crash doesn't seem in a regular out of memory. Could you share you system info, crash files and run the game with GDB to retrieve a stack?

Yeah, download VulkanRT-1.3.261.1-Installer and run it. Were you able to find your card in the supported lists?

You need to make sure that your video card supports Vulkan. Here's a list for NVIDIA: https://developer.nvidia.com/vulkan-driver, here's a list for AMD: https://www.amd.com/en/technologies/vulkan (scroll to the bottom), here's a list for Intel: https://www.intel.com/content/www/us/en/support/articles/000005524/graphics.html. If you're able to find your video-card there but it doesn't work then you could try to install Vulkan run-time directly: https://vulkan.lunarg.com/sdk/home#windows

How long it takes to play before you get the first error?

Hi! Please take a look at this post:

Hi! That problem will be fixed in the next version of the game (Alpha 27): https://trac.wildfiregames.com/ticket/6629 What to do to fix the problem prior Alpha 27, possible choices: https://wildfiregames.com/forum/topic/95151-i-dont-know-what-to-do-can-someone-help-me-and-explain/#comment-523747 Download and install community-mod Try delete matchsettings.json

Generally yes, it's better to avoid many textures. Also it's possible to combine a single 2k texture from 4x 1k textures if it'll be reused for many actors with the same material.

We need to update only changed files. We already have scripts to detected outdated years and update years for affected files. But not everyone and not always uses them.

We use OpenAL library to play sounds. You could try other games with OpenAL (for example SuperTuxKart or Warzone 2100) and check how sound behaves there.

Forgotten year updates But yeah, periodically we change such old files: