little Guest

It seems that the result is the same. (0.29.0dev-win64 Adrenalin 26.5.2)crashlog.dmp (0.29.0dev-win64 Adrenalin 26.5.2)crashlog.txt

I forgot to mention, I use 64bits Release 28. It is fine in the main menu. When I start a new game, it crash after it is 100% loading. If you can provide a pre-built version, I can help test it. By the way, I test the latest AMD driver: Adrenalin 26.5.2 with 64bits Release 28. The results of Alt+Tab issue and crash issue are the same as Adrenalin 25.8.1. (Release 28 Adrenalin 26.5.2)crashlog.dmp (Release 28 Adrenalin 26.5.2)crashlog.txt

I try the new Release 28 with AMD driver: Adrenalin 25.8.1. The Alt+Tab issue (issue 1) is still the same, as expected. The crash issue (issue 2) is still the same, but now it shows a crash message and a crash log. I wonder whether the crash log is helpful? I was wondering recently: I have no issues using Vulkan in Dota 2. Does Dota 2 use GPU skinning? (Release 28 Adrenalin 25.8.1)crashlog.dmp (Release 28 Adrenalin 25.8.1)crashlog.txt

Today I see the new AMD driver: Adrenalin 25.8.1. The test results are the same as before — issue 1 and issue 2 still exist. The driver date shown in Device Manager is 2025/7/1.

If I follow your steps with Vulkan and GPU skinning enabled, then there is a crash issue similar to the one I posted before. I guess your insane graphics issue might be caused by the driver. At least on my Vega iGPU, updating the driver solved it.

Here is a Win10 system with a Vega iGPU. If I use the old driver (Adrenalin 22.6.1): OpenGL with GPU skinning disabled: works fine OpenGL with GPU skinning enabled: same issue occurs I followed your steps, and the issue is not fixed. (22.6.1OpenGL)system_info.txt (22.6.1OpenGL)userreport_hwdetect.txt

Yes. It is fixed now.

@ItmsA27.1-rc2 doesn't work on my old win7 laptop. And it works if I replace the two files called "mozjs115-release.dll" and "mozjs115-release.pdb" with those files in the following post.

I didn't receive vladislavbelov's modified version of the A27 pyrogenesis.exe. Besides, I think that is for issue 1, the Alt+Tab issue, not issue 2, the crash issue.

Today I used the AMD Bug Report Tool to report issue 1 and issue 2, but I’m not sure if AMD will actually do anything about it.

Tested A27.1 rc1 — the situation is still the same: it crashes with Vulkan and GPU skinning enabled. (No crash log, 2 errors in Windows Event Viewer)(Same as issue 2 in the post below) (issue2)Event viewer.txt

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.