Marvel vs Capcom 2 (Naomi): "Grid" artifacts on AMD APU #1086
-
Hi @flyinghead , I'm having a very similar problem to this issue in the standalone version (v2.1). This wasn't a problem on my NVIDIA GPU as far as I can recall, but I recently got a Beelink SER5 Pro (Ryzen 7 5800H) mini PC. The grid is visible on Hulk's torso and feet, but it's on each of the characters (sorry not very visible on phone cam) and it moves with them. Changing between OGL, Vulkan, D3D9, D3D11 also didn't remove it. Any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
If you are running at native 640x480 resolution and with default settings then this is likely a gpu or gpu driver issue. And unfortunately I don't have any workaround. |
Beta Was this translation helpful? Give feedback.
-
Hi @flyinghead , thanks for the quick response as always. I ran native resolution with that option enabled and the grid is still there. 3D games appear unaffected. As much as I love these Ryzen minis, I have observed AMD just doesn't seem to like Dreamcast emulators. Weird quirks with their APUs and GPUs, even high-end ones. Suffice to say, Flycast did better than the other emulator. Guess I'll just have to live with this one. |
Beta Was this translation helpful? Give feedback.
-
I am using a Ryzen 2400G APU and it plays games quite reasonable in DirectX11 mode of Win10. (Even Ferrari F355 Challenge runs fast enough.) But with OpenGL (Sega Driving Simulator crashes in other modes) some games run a bit choppy, and with Vulkan there are graphics glitches (e.g. water in the arcade game Soul Surfer). I employ a 22'' 4:3 CRT (1280*1024@72Hz) on a HDMI2VGA converter, which may look different than TFT. |
Beta Was this translation helpful? Give feedback.
-
Please disable "Fix upscale bleeding edge" when upscaled. You won't have the lines/grid. |
Beta Was this translation helpful? Give feedback.
If you are running at native 640x480 resolution and with default settings then this is likely a gpu or gpu driver issue. And unfortunately I don't have any workaround.
The
Native Depth Interpolation
option is recommended for AMD GPUs but I don't think it would help in this case.