little Guest

Some people are also experiencing issue 2. Testing an old AMD's driver: 31.0.14057.5006 (Adrenalin 23.5.2). The result of issue 2 is in this thread: And interestingly, the situation for issue 1 is a bit different. OpenGL has the same problem when running in fullscreen mode as well.

The closest I found in AMD's driver is 31.0.14057.5006 (Adrenalin 23.5.2). The following are the results of my test. OpenGL + GPU skinning disabled + fullscreen mode: fine OpenGL + GPU skinning disabled + windowed mode: fine OpenGL + GPU skinning enabled + fullscreen mode: fine OpenGL + GPU skinning enabled + windowed mode: fine Vulkan + GPU skinning disabled + fullscreen mode: fine Vulkan + GPU skinning disabled + windowed mode: fine Vulkan + GPU skinning enabled + fullscreen mode: crash message, crash log, 1 error in Windows Event Viewer Vulkan + GPU skinning enabled + windowed mode: crash message, crash log, 1 error in Windows Event Viewer The crash message looks the same as the original poster's. (Adrenalin 23.5.2) crashlog.dmp (Adrenalin 23.5.2)crashlog.txt (Adrenalin 23.5.2)Windows Event Viewer.txt

So you mean that after updating the driver: Vulkan + GPU skinning disabled works fine in both fullscreen and windowed mode, Vulkan + GPU skinning enabled in both fullscreen and windowed mode runs, but the units look broken, is that correct? Besides, after changing the GPU skinning setting and saving it, did you restart 0 A.D.? Because on my side, if I change from Vulkan + GPU skinning disabled to Vulkan + GPU skinning enabled, save the setting and start a new game right away, the game runs without crashing — but I suspect GPU skinning isn’t actually active.

I suggest that after saving the settings, close and reopen the 0 A.D. program to ensure the game runs with the new settings. At least for rendering and GPU skinning.

What is your driver version? When I have time, I'll try to see if I can reproduce the same situation.

How does it work with GPU skinning disabled? I guess it might be the same issue as point 2 in this post, except for the driver version — I only know it's older than Adrenalin 24.9.1. By the way, could you test whether you’re experiencing the issue mentioned in point 1 of that post and reply there? Vega GPU users seem to be pretty rare. Thanks!

Among all users with a Vega GPU (or iGPU) and Windows OS, I'm wondering whether issues 1 and 2 are something only I experience or if they're common. Today I specifically brought my PC to a different location to test using an HDMI connection to a TV. The Alt + Tab issue still occurred. And it is fine if using openGL. To summarize, this occurs on a VGA (D-sub) monitor and an HDMI TV, but there is no issue when using HDMI to a USB video capture card connected to an old laptop. By the way, I saw that there's a new AMD driver: Adrenalin 25.5.1. However, after testing, I found that the result is still the same, and issue 1 and issue 2 are still present.

Thanks! I can run and test it when you're ready. btw, I wonder if anyone else with a Vega iGPU is also experiencing issue 1 and issue 2?

Strangely, I downloaded some games to test, and all of the Alt + Tab worked fine. The following is the list of games I tested. SuperTuxKart (Edit config.xml in configuration folder and change "gl" to "vulkan" for the "render_driver" setting.) Dota 2 Unturned (In Steam, enter "-force-vulkan" in the launch options under Unturned's properties.) Veloren War Thunder (In Steam, enter "-driver:vulkan" in the launch options under War Thunder's properties.) Yes. With OpenGL + GPU skinning, everything works fine. ChatGPT suggested that I check the Windows Event Viewer. After the crash, I found two errors there. I copied the contents of the two errors into the attached file below. (issue2)Event viewer.txt

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. It also occurs on a HDMI TV. (2025/5/8 update) 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