vladislavbelov

Thanks! Could you add the following lines into your user.cfg file: forceglversion = "true" forceglprofile = "compatibility" forceglmajorversion = 2 forceglminorversion = 1

Hi! Which OS do you have? Also could you attach hwreport/systeminfo from the same folder after running A25?

Thank you! I'm able to reproduce now

Does it happen on each re-opening? Could you attach matchsettings.json then?

Thanks for the logs, but I need mainlog.html that contains mentioned errors, so it needs to be attached right after these errors are reproduced

Could you attach mainlog.html after the error appeared? Also which map did you play right before?

It's pretty hard to make any improvement without statistics. Could you retrieve Shift + F11 statistics (profiler.txt) for A25 and A26 for the same scene? And attach logs and hwreport as well, you might find paths to them here: https://trac.wildfiregames.com/wiki/GameDataPaths.

Could you share your logs (system_info.txt, userreport_hwdetect.txt, mainlog.html, interestinglog.html)? You might find paths to them here: https://trac.wildfiregames.com/wiki/GameDataPaths .

How did you measure the difference? Usually unit lag = frameTime (~16.6ms) + simulationTurnDuration (200ms).

It depends. If a mouse input happened during simulation or rendering phases then it won't be processed until a frame is done. So it's kind of correlated things.

Looks like the emblem from the Witcher.

There are another two parameters that didn't fit into the main options (you need to set them in user.cfg) but might help you to not disable icons at all: gui.session.minimap.icons.opacity - how transparent icons are (0.0 - 1.0, default: 1.0). gui.session.minimap.icons.sizescale - multiplies the icon size by that value (should be greater than zero, default: 1.0).

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.