little Guest

Oh, I see! For Vulkan fullscreen mode, after the first Alt + Tab, the animations (e.g. side-to-side moving knight and horse in the main menu) stop. And the mouse behavior suggests that it did switch to the browser successfully. After the second Alt + Tab, it's back and the position of the knight and horse has changed. And then, they continue moving left and right. I tried it, and the result is the same. With Vulkan and GPU skinning disabled, everything works fine. With Vulkan and GPU skinning enabled, the log [(issue2)......] is actually already attached at the bottom of my first post.

The following link is a video that I tried to record using a video capture card. https://i.imgur.com/IbzBkIT.mp4 I hope this makes the description of issue 2 clearer.

I'm glad to see your reply. Yes. After the second Alt + Tab, it's back. I'm not sure what you mean by "So it just stays on top?" However, from the previously provided images, we can see that in "after Alt+Tab," the mouse cursor in both Vulkan fullscreen mode and Vulkan windowed mode is in the shape of a capital "I," which should indicate that the switch to the browser was successful. In the game. It is fine in the main menu. Yes. It is fine when GPU skinning is disable. Additional information: Attached are three screenshots showing the cases with control groups, after removing control groups, and selecting 300 units. It seems that the main difference lies in the gui sim update. The impact of control groups (control a large number of units) is more severe than selecting 300 units.

It seems that no one has mentioned these two Vulkan issues yet. With Vulkan in fullscreen, after pressing Alt + Tab, the screen remains stuck on the 0ad display. No issue with OpenGL, nor with Vulkan in windowed mode. This occurs on a VGA (D-sub) monitor, but there is no issue when using HDMI to a USB video capture card connected to an old laptop. With Vulkan and GPU skinning enabled, the screen jumps to the desktop and the program shuts down when loading the game. No crash report. Win 10, Vega igpu, driver: Adrenalin 24.9.1 (latest) By the way, is it a known issue that when multiple control groups control a large number of units (e.g., 632), moving the camera—even without selecting units—feels a bit choppy? (issue2)userreport_hwdetect.txt(issue2)system_info.txt(issue2)mainlog.html