What a month! GOAT releases, yuzu ventures onto new platforms, we get a taste of Project Gaia, full Amiibo support, further Project Y.F.C., and a lot more!Put on your safety belt and start playing some eurobeat, this will be a long ride.
While investigating very low VRAM devices, byte[] found that yuzu used incompatible memory property flags when the Vulkan memory allocator was under pressure, causing low VRAM GPUs to crash when trying to actually use a recycled allocation.
In addition, byte[] has also tuned the memory manager to be more ruthless.This change should help improve gameplay stability during long sessions on systems with less RAM.yuzu always aims to support a minimum of 8GB of RAM on systems with dedicated GPUs.
We recommend that you read the dedicated yuzu on Android article here.In this section, we will give you an overview of our future plans, some tips on settings and hardware requirements, and a realistic outlook on what you can expect from yuzu on Android right now.
The Android version of yuzu was not an easy feat. It took us almost eight months of hard work to make it happen.Right now, the core is essentially the same as the desktop version, with an Android UI and very few platform-specific tweaks.This means you can enjoy features like 32-bit game support, NVDEC video decoding support, motion, controller automapping, resolution scaling, and filters.On the other hand, features like mod and cheat management, LDN, and the controller configuration applet are still under development.Our goal is to gradually have the Android builds reach parity with the PC version.
Users with capable hardware stuck on older Android versions can either build yuzu themselves and remove the code responsible for performing this check, or install custom ROMs such as LineageOS to get unofficial Android updates on their device.
Maide found an issue related to the size of the pipeline cache.yuzu used to return the size of the shader code in bytes, which was later used to resize the unsigned 64 bit integer array in charge of storing the cache, making the array 8 times larger than it was supposed to be.This is fixed by using the length of the array instead of the size in bytes.
The war against properly shutting down yuzu rages on.This time Maide implements a fix in the DSP engine so it closes before a required system instance is terminated.This way a deadlock is avoided during shutdown, improving the situation slightly.Another battle won, but how many remain?
If your yuzu is configured with multiple user profiles, and the Prompt for user on game boot option in Emulation > Configure > General option is enabled, you will have to click the profile you want to boot and then click OK.Well, for the newcomer Qigo42, this was unsatisfactory, so they allowed the profile selection pop-up to work with just a double click!Nothing beats quality-of-life changes. Thank you!
If you double clicked a game in the game list, you could end up double clicking it again or pressing enter before the game list got unloaded, which would cause yuzu to try to load the game twice, and usually just crash.german77 fixed this up by immediately disabling the game list after a game has been launched.
As the VRAM fills up, an AMD card will get slower and slower until it stops working and crashes yuzu, while an NVIDIA GPU would corrupt the entire desktop, taking all the displays with it, sometimes even forcibly rebooting the system.
And in other good news, Special K now supports HDR in Vulkan and it works with yuzu!NVIDIA is still the only supported vendor, as this is only possible thanks to the magic Prefer layered on DXGI Swapchain option, but the quality and customization offered by Special K over AutoHDR is outstanding. That expensive OLED never looked so tempting.
Sadly, fixing this issue showed us two areas where yuzu is at fault.But luckily both issues have fixes in testing in the latest Early Access release (at the time of writing). If everything goes according to plan, they should hit Mainline in a few days. Stay tuned.
760c119bf3