CPU: Ryzen 5 2500u
GPU: Radeon RX 560X
OS: Windows 10
CPU: Ryzen 5 2500u
I did not find anything wrong in your log file. Please wait for a moderator to assist.
Update your GPU Driver from hear, AMD has problems with download.
Driver update solves nothing.
That’s great that it works for you using Nvidia over OpenGL, but it doesn’t solve my issue.
If you post the log OpenGL and Vulkan you will get more help from @GoldenX86, the first one is incomplete, go where the log is located, start the game till you get in the starting point in the game, where you have this graphic glitche, close Yuzu and post the log.
yuzu_log.txt (316.6 KB)
There we go
System Information for Support
Client Version yuzu 509 . HEAD-mainline-636-4365-g453520279 Operating System Windows 10 (10.0) CPU AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx | AVX2 | FMA Graphics API OpenGL 4.3.1 Graphics Renderer Radeon RX 560X Series GPU Driver Version 20.12.1 27.20.14501.28009 Use Async GPU [x] BCAT Backend none GPU Emulation Accuracy Level Normal
Here’s some issues I found with your log that might help.
- Due to AMD’s poorly optimized OpenGL driver, you may experience slowdowns.
This is recommended for Xenoblade games.
GPU Emulation Accuracy Level High
Even with GPU accuracy set to high, the problem still occurs on Vulkan.
I meant for OpenGL hoping to get more FPS from it, not to fix the Vulkan glitch, but your GPU is integrated and that is a problem, you only have 2gb ram transformed in vram, and I have Geforce GTX 1060 6gb ram.
I have a dedicated RX560 with 4GB of RAM, but even using that, I only average about 10 FPS on OpenGL.
AMD vs. Nvidia = Nvidia is best for now, but in time AMD and Intel will start to work like Nvidia.
AMD has poorly optimized Drivers in general CPU and GPU.
AMD drivers a re poorly optimized for OpenGL. Vulkan should be running just fine.
And why Vulkan is not working on AMD and it is working on Nvidia.
I don’t know. It could just be my configuration. I won’t know unless someone who is a little more knowledgeable with programming takes a look at my case.
The only option is to ask @GoldenX86 if he knows something.