Jump to content

little Guest

Community Members
  • Posts

    20
  • Joined

  • Last visited

Recent Profile Visitors

366 profile views

little Guest's Achievements

Discens

Discens (2/14)

2

Reputation

  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.
  2. 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
  3. @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.
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. What is your driver version? When I have time, I'll try to see if I can reproduce the same situation.
  12. 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!
  13. 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.
  14. 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?
×
×
  • Create New...