To bypass this hardware limitation, yuzu uses D32 textures instead, which can cause precision issues during the conversion process. Those were the good days.Īhem, anyway, AMD Radeon GPUs lack support for fixed point 24-bit depth textures, or D24 for short, a relatively common texture format. Ultimate turning completely white or ghosting, akin to when applications would freeze back in the Windows XP era. Performance returned to normal after the introduction of this PR.ĪMD Windows users are also familiar with certain stages in Super Smash Bros. So we had to lay down the pitchforks, this time. Surprisingly, this only started affecting official AMD drivers recently, after their periodical Vulkan version update. epicboy found out that during the process of initializing Vulkan, the emulator assigned Int8Float16’s values after its memory was freed. We even singled out Int8Float16 as the culprit, providing an alternative path that reduced performance on all AMD GPUs running non-RADV drivers. We rushed once again to blame AMD for breaking another extension, as it wouldn’t be the first time. With the release of AMD’s Windows driver version 21.9.1, and its equivalent AMDVLK and AMDGPU-PRO Vulkan Linux counterparts, users started noticing crashes in most games right at boot. While this was fine for other drivers and vendors, ANV (Intel’s Vulkan driver) expected to have the frame already rendered before this command, causing this error.Įpicboy fixed the synchronization behaviour so that yuzu now waits until the frame is fully rendered and ready before presenting it. Previously, yuzu would issue the Vulkan Present command, then wait for the frame to be rendered before continuing with the process. The problem was in the synchronization between the rendering and subsequent presentation of frames.

Due to the nature of this presentation mode, this may cause visible tearing on the screen, so bear that in mind if you try this out.Īnd this is with just an RX 550 (Metroid Dread)īooting a title in Linux with the Vulkan API using the Intel Mesa driver resulted in a crash due to a device loss error. They, however, support VK_PRESENT_MODE_IMMEDIATE_KHR, another mode that allows Vulkan to present at a higher framerate than the screen refresh rate, so epicboy made the necessary changes in order to unlock the FPS on these GPUs. Yet more AMD specific changes and other graphical fixesCertain AMD and Intel GPUs were unable to utilize yuzu’s unlock FPS feature with the Vulkan API, due to the lack of driver support for the VK_PRESENT_MODE_MAILBOX_KHRpresentation mode. We have even more GPU rendering fixes, TAS support, 8 player mayhem, input and UI changes, some preliminary work for future big changes, and more! Hi yuz-ers! Welcome to the latest entry of our monthly progress reports.

Nintendo switch pc emulator