-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Vulkan has been broken with the Flycast core since version 1.19.0 #16973
Comments
These seem to be the only major changes made to the Vulkan code in 1.19.0 - VIDEO/VULKAN: Add support for A2R10G10B10 HDR format Do you have HDR support enabled in RetroArch? Can you try disabling it in RetroArch and then seeing what happens? |
No such issues here with fresh versions, and also no HDR. Windows 10, GTX 970 + 536.23. |
I do have an HDR display but i don't have HDR enabled in both Windows and RetroArch. All the RA versions i've tested with have used default settings, so HDR was disabled (i just doubled checked to make sure). |
@sonninnos List your Nvidia driver version and OS. @PoloniumRain Same as well. Also maybe post your retroarch.cfg file. Maybe you have some setting/feature enabled which is causing this. |
Windows 11 version 23H2, OS build 22631.3447 But as mentioned, i've also tried several older Nvidia drivers. I don't remember what versions, but they were all released within the past 7-ish months. Here's the config files for 1.19.0 (corruption) and also the config for 1.17 (working fine), which are both clean installs so they should be using default settings: config.zip |
Yep same issue here. I found per-pixel helps but doesn't solve the issue. Crazy Taxi is almost unplayable because it fills the screen. Funny thing is Naomi 2 works fine as well as Dreamcast. It's a Vulkin issue. Switching to Open GL fixes the problem. |
@Boomerps2 What OS and GPU drivers are you using? For me everything has it - DC, Naomi and Naomi 2. The cores Per-pixel option can reduce the problem in a game area or menu screen, but then in another area or menu it can make it worse. Enabling/disabling RA shaders also has the same effect... Weird. |
I can't reproduce it here unfortunately. |
Window 11 with latest Nvidia drivers with the latest Retroarch 1.19
Yahoo Mail: Search, Organize, Conquer
On Mon, Sep 9, 2024 at 10:10 AM, ***@***.***> wrote:
@Boomerps2 What OS and GPU drivers are you using? For me everything has it - DC, Naomi and Naomi 2. The cores Per-pixel option can reduce the problem in a game area or menu screen, but then in another area or menu it can make it worse. Enabling/disabling RA shaders also has the same effect... Weird.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@flyinghead can't seem to reproduce it either. |
@PoloniumRain May you provide some log also ? Thank you. |
I can't reproduce the issue with latest, and also no HDR. Windows 10, GTX 1060 and Nvidia driver version 560.94. |
Maybe you can try this pr based build Maybe it's because the RA vulkan head version is too old, and Flycast updated the vulkan version sdk to 1.3.261 last year |
@crashGG Sadly that didn't help. I tried copying the working 1.17 Is it possible to download nightly builds between 1.17 - 1.19.0? I can't find any that old on https://buildbot.libretro.com/nightly But then i could narrow down this problem to an exact date. |
RA_vulkan13.zip |
Still has the same problem. |
@PoloniumRain @faxesystem So this issue only happens in Windows 11 with Nvidia ? If it is the case, the issue title should be renamed with this information. Thank you. |
Description
When using Vulkan with the Flycast core, there is significant graphical corruption in all Dreamcast games in the form of many small flickering blocks, as shown in the videos below. At first i thought this was a Flycast problem so i posted about it on the Flycast GitHub. But after much more testing i've now narrowed this issue down to a change that was introduce with RA version 1.19.0, and it still persists in version 1.19.1. All older versions like 1.17 do not have this problem, at least going back to 1.14, which is the oldest that i've tested.
Some things of note:
Steps to reproduce the bug
Online Updater > Core Downloader
and get the latest Flycast coreVersion/Commit
RetroArch stable 1.19.0 and 1.19.1 are both affected.
Environment information
Rayman2.mp4
MDK2.mp4
Daytona.mp4
The text was updated successfully, but these errors were encountered: