vladislavbelov

It's irrelevant to 0 A.D. We don't use mesh shaders and don't plan to in the near future.

Could you try to add the following line to your user.cfg then? smoothlos = "false"

Could you try to add the following lines to your user.cfg (path to the configuration file you might find here: https://trac.wildfiregames.com/wiki/GameDataPaths)? renderer.backend.debugcontext = "true" renderer.backend.debuglabels = "true" renderer.backend.debugmessages = "true" renderer.backend.debugscopedlabels = "true" Also is the issue reproducible for both OpenGL backend and OpenGL ARB backend (it's an option inside the advanced graphics tab)?

I need a full log to fix them.

Thanks! Yeah, that's intentional else the mod would be ~5 times bigger.

Could you post the full message (with all missed defines)?

These errors should be fixed in the new version: 0.27.16.

It should be fixed in the next build (there was a fix for that kind of glitch: rP27511).

Could you try the new 0.27.15 version?

It's the mod version (to keep tracking changes) not the SPIR-V version. Currently we're targeting SPIR-V 1.3.

SDL loads it (inside it might search for different paths).

Thanks! I'll check it.

@cantfind @Graham1 I've came up with another random idea: https://trac.wildfiregames.com/ticket/6649#comment:7, but it needs to compile the game.

You need to update the 0ad-spirv mod to the last version.

Thank you for reporting and testing!

That's expected. There is a new build that might fix the problem: https://code.wildfiregames.com/rP27519

Thank you for the feedback! I think I found a possible reason. I'll add a fix to the code.

Did you pass --large-address-aware to update-workspaces.bat?

Do you use autobuild or build by yourself?

-2 is VK_ERROR_OUT_OF_DEVICE_MEMORY.

Build is ready: https://code.wildfiregames.com/rP27514

Thanks! I'll add more information to logs (currently it's not enough information to figure out the reason) and ping you when an autobuild will be ready.

Hi! Could you attach your mainlog.html after running the game with Vulkan selected? Paths to logs you might find here: https://trac.wildfiregames.com/wiki/GameDataPaths

It's not the hardest part. The most time consuming part is to make the lights be accounted during rendering. PBR isn't for details but for rendering consistency. With PBR an object will look well in all light conditions. Currently we have over-brighten or over-darken colors on some maps.

Currently we have at least two major problems: many different materials (different only by uniform value aren't different) and many draw calls (because of complex variations). I also plan to release Technical Art Guide but not sure when I'll have time to finish it. No, I mean industry standard PBR approaches.