vladislavbelov

Please enable Feedback (it really helps us) on the bottom right in the main menu if possible

That also happens because those developers are paid, it means they don't work at that time. We're volunteers. And usually we have more free time during a weekend. So the point isn't so useful for us. That process might last for a week for some distros.

Via JS - yes, but mouse tracking isn't implemented.

Camera related code is C++. Only interfaces to switch modes are JS.

Yep, it might be added there. Thanks for the help!

Which FAQ do you mean? Thanks for the testing.

If something needs a change in 0 A.D. it has to be reviewed. That means time, though it's less than creating a patch. But a bigger patch more time to review (and dependence isn't linear). For that we have Trac: https://trac.wildfiregames.com/report.

It might be, but no promises. Because we have limited time and few active people to fix everything.

There is a new borderless.fullscreen option in A26, you could try to set it to false. If it doesn't help then highly likely it's not the game issue (maybe SDL).

If you don't render both meshes at the same time (frame) then it's ok. Especially if you use the same material for them.

Answered. In short: we don't decompress data.

I've also added borderless.fullscreen and borderless.window options to the config file. You could try some if it changes something.

Is that screenshot made via F2 in the game? Could you try to switch to OpenGL backend? I also found the following quote from https://docs.microsoft.com/en-us/gaming/game-bar/known-issues: So it might mean that the game bar might not work correctly on some drivers.

A26 profile.txt is also with high shadows, right? A25 profile.txt says that it has everything faster, not particularly graphics (and pretty stable magnitude for mostly everything). There were no graphics or engine related commit after that one. So it seems more related to AppImage itself (maybe some optimizations are missed in the build). Could you attach system_info/hwreport for A25 too?

Could you get profiler.txt for that setup as well?

I see you have set Anisotropic filtering to x16 (which is x2 by default, like it was in A25). Could you switch it to x2 and compare the performance?

Which fix do you mean? There might be multiple reasons (including driver updates). Could you run the game, get 25FPS and press Shift + F11? There will appear a profile.txt file in logs folder, could you attach it here. Also do you have installed A25 to compare?

Stack:

That should be pretty old bug. Magenta happens when you have XML for the terrain type, but not the DDS/PNG texture. It crashes when PMP refers to a not existing XML file for terrain IIRC.

It looks ok. That's strange why the text is encrypted. Seems like XMessage reinterprets it as Unicode or vice versa. Yes, it's solved in r27067 and in the upcoming release as well.

You might find paths to them here: https://trac.wildfiregames.com/wiki/GameDataPaths#VistaWindows10.

Do you know which locale does your OS use?

Could you make a screenshot via F2? Does it contain black bars? Also could you attach your system_info and hwreport (you might find them by paths from https://trac.wildfiregames.com/wiki/GameDataPaths#VistaWindows10)? Is freezing reproducible?

Hi! In the upcoming A26 release will appear an option to decrease texture quality and disable anisotropic filtering. Plus disabling variation randomization might help a bit.

I have some ideas to fix the heightmap import to allow 16-bits grayscale images.