I noticed there was a new driver update pushed yesterday. Haven’t turned on my RA machine yet, but let me know if the new driver update fixes the issue!
I didn’t find any driver updates today, I’ll check again tomorrow
That’s my bad, it looks like I misread the page, a new version of the auto-detect tool was released, not a new driver version.
Edit: Or, rather, it looks like, for some reason, they’ve unpublished the update? The release notes page for the update I originally saw seems to still exist, but the 23.9.3 version is still showing up as the newest version.
At least there is no new driver available for the RX 560
Updating to add that the recent 23.10.2 update (which does not appear to cover the RX 560, and a quick google search shows that they may be phasing out driver updates for that card/architecture) seems to continue the issues. To date, the latest AMD driver I’ve been able to make work is version 23.5.2
New Driver 23.11.1 https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-11-1-polaris-vega
Fixed Issues
- Intermittent corruption may be briefly observed while playing Counter Strike 2 with Vulkan API on some AMD Graphics Products, such as the Radeon™ RX 580.
- Unable to select summary table in ACCA Software Edificius Architectural Design on some AMD Graphics Products, such as the Radeon™ VII.
Known Issues
- Performance Metrics Overlay may report N/A for FPS on various games.
- System crash or AMD Software: Adrenalin Edition may fail to respond when changing Tuning Present on some AMD Graphics Products, such as the Radeon™ RX Vega 64.
Important Notes
- Factory Reset has been temporarily disabled as a precautionary measure while we address isolated installation issues that have been reported during PC upgrades. Users may use AMD Cleanup Utility as a temporary option.
- For users who previously installed an AMD Software insider preview driver, running AMD Cleanup Utility is recommended before installing this driver.
1 Like
I don’t think the problem is due to the AMD drivers, also because the problem also exists with NVIDIA, we should analyze the issue better and understand where this problem is created
See this old thread https://github.com/libretro/RetroArch/issues/9668
That old bug report has been closed because the culprit was outside retroarch and specific to windows+nvidia+some other software, but definitely not retroarch.
Just saying that the issues are likely not related.
Yes, but the problem remained with AMD, and having updated both retroarch and the AMD drivers, I can’t understand if the problem comes from AMD or retroarch. With old AMD driver versions and old retroarch everything worked fine
Why don’t you install old rettoarch just to check?
1 Like
Great idea, I downloaded retroarch 1.13 from Buildbot same core and same roms as mame that I used on 1.17, with version 1.13 I HAVE NO STUTTERING PROBLEM, so the problem is not AMD drivers, but retroarch 1,17.
WORK PERFECT https://streamable.com/wjjgjl
1 Like
Great, indeed.
Please then, double check again ensuring you are using the same configuration and if confirmed, open a bug report to the github project page to let the devs know about the issue.
Ps: are you from Naples? I think I can understand some slang words in the video you posted 
Yes, I checked correctly, the problem is retroarch.
I’ll open a report now, thanks!
Yes, I’m from Naples 
1 Like
Fuorigrotta/Vomero here 
1 Like
Io sto in zona Panuozzo 
1 Like
To help devs, you could try to understand where exactly it started to happen. 1.14? 1.16?
I should try installing those versions again, however I remember that the problem was already present, but I don’t remember in which version exactly.
Stop ! I am going crazy . Wanting to find out at what precise moment Retroarch broke with the Vulkan drivers, I also downloaded the other versions, unpacked them on C:\user\Desktop, and ironically all the versions work fluidly including 1.17 Normally my retroarch folder is located in **C:\Launchbox (**and not on desktop), so for a strange reason the stuttering defect occurs depending on the folder in which I have retroarch, I can’t understand what it could depend on
It doesn’t make much sense… any chance you are using different configs?
No, I used the same CORE, same setup with Vulkan and Slang shaders. At this point I may suspect a question of folder permissions, let me explain… I created this romset on another PC years ago, then I copied it here and updated it from time to time. I wouldn’t want the folder to bring with it old permissions that perhaps interfere with the Vulkan drivers, I can’t find any other explanation… (and I’m an old Microsoft beta tester with Windows 7)