-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All games have graphical corruption with Vulkan on RetroArch #1631
Comments
This is very likely a GPU or GPU driver issue. |
It happens with all of those settings. I also thought it may be my GPU, because the corruption looks similar to when a GPU's VRAM has been overclocked too high. But my GPU isn't overclocked, and any other emulators, games, benchmarks or stress tests that i try will all run fine, including Vulkan stuff. I've now tried 4 different drivers, all released within the past 7 months, and nothing makes a difference. |
Can you try Flycast standalone? |
Just tried 8 games with standalone v2.3 and Vulkan works fine. I've also now tried 20+ games with the RetroArch Flycast core and they all have the same graphical corruption, including the Dreamcast menu that appears when there's no disc in the console. |
I would try to do a fresh install of retroarch, using default settings and no add-ons, shaders, ... and see if the issue persists. |
Already tried that. But i've now tested older RetroArch versions, going back to 1.14. Theses all work without any issues with Vulkan. The problem was introduced in version 1.19.0, which was released on the 30th of May. So i'll make a post about this issue on the RA GitHub... EDIT: Created a post on the RA GitHub. |
On my Ryzen 2400G APU Vulkan also has glitches (e.g. water pixel mess in "Soul Surfer"). DirectX11 works better (only Sega Driving Simulator depends on OpenGL, which seems slower/choppier on my APU). |
Not sure if related but I find recently that Sega Rally 2 freezes quite often in RetroArch, particularly in the menus after the name entry screen. It doesn't seem to do this in standalone. It was more frequent with the gl driver but also occurs with d3d11 |
The corruption appears even in the Flycast 2.3.2-199 nightly and in Retroarch with the Vulkan Driver. Even in the BIOS as they say. With DX11 it seems to be mitigated or it doesn't appear, the same if you set the native resolution, it doesn't appear in the BIOS, but if you increase the resolution, there are artifacts in the BIOS at the bottom right, above the clock icon, both in Flycast and Retroarch. If Full Framebuffer Emulation is activated, the artifacts no longer appear, but we can't increase the resolution. This has been happening for a while and as it happens in both, it's not focused on AR. Many won't notice it because they use old versions, like March 2.3, but it seems to be something related to the framebuffer. |
@ToniBC if you increase the resolution you might need to increase the pixel buffer size. What you're seeing may be the result of the pixel buffer overflowing. |
This one has 128 layers and 4GB of pixel buffer. Tested by default and the same thing happens. I have tested the same configuration (even moving the .cfg from one version to the other) with Flycast 2.3 and it doesn't cause any problems, those errors are not observed in the bios or in the games, but the same thing happens with the latest versions. I will try to test other previous versions to see if the same thing happens. |
I have done several tests with several versions, I'll tell you. In version 2.3.2-4 (2024-05-21) everything apparently works fine, the glitch does not appear in the bios. In version 2.3.2-95 (2024-05-23), the glitch already appears there. The changes introduced there, some broke something. I'll put the changes here.
|
This is a merge commit from the dev branch, which includes many changes. |
Unfortunately I don't have enough knowledge to compile versions, the ones I found were those, between those two I don't have more versions. The oldest buildbot is from 2024-07 which is where the bug is already in the master branch. |
I didn't look at the dates but yes, the issue seems to have appeared a while ago. |
I guess that since Retroarch's default driver is now dx11 and before that GL, it doesn't fail there, it seems to only fail in Vulkan with resolutions higher than the native one. If Full Framebuffer is activated so that certain games work well, the problem is solved, because it is set to native resolution. Since many don't touch options, they have it in dx11 and there it seems to work well. All this with Nvidia RTX 3070 GPU. On AMD, I have to try it on Steam Deck and ROG which is the only AMD I have to see if the same thing happens. |
Platform / OS / Hardware:
RetroArch 1.19.1 on PC, Windows 11, AMD Threadripper 3960X, RTX 3080 (latest drivers)
Description of the Issue
Graphical corruption in the form of many small flickering blocks, shown in the videos below. I've tried 12 random games so far and it affects each one. RetroArch Shaders have an effect on it, but it also always happens without shaders. So Vulkan is unusable because this problem is always visable. Depending on the game and area it will sometimes have less or more graphical corruption when a shader is either enabled or disabled. I also have the D3D11 shader problem mentioned in #1612, so GL is only thing that's working for me.
Debugging Steps Tested
Rayman2.mp4
MDK2.mp4
Daytona.mp4
The text was updated successfully, but these errors were encountered: