You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating the latest Mupen64Plus-Next core in retroarch (core version 2.7-Vulkan 4249e39), the HUD was no longer showing correctly in Mario Kart 64 in a two-player game (single player worked but I only tried for a minute or so). No mini map was shown and no Items were shown. RDP was GLideN64.
Steps to reproduce:
Fresh download of retroarch Windows x64
Update Mupen64Plus-Next core via online update (core version 2.7-Vulkan 4249e39)
Change GlideN64 config "Less accurate blending mode" from OFF to ON to get rid of black boxes in UI as described here
Run a two-player Mario Kart 64 game e.g. battle on donut (USA rom)
Observe the HUD not showing
Probably someone already noticed, but I am putting this here just in case.
Image that shows the issues attached.
Switching back to stable (2.6-Vulkan 5d2ac21) as included in retroarch v1.19.1 fixes the issue.
Cheers, AndBu
P.s. I feel like there should be an option to only download the latest stable cores when updating and it should be the default or the update functionality should come with a big fat warning that you are actually updating to nightly builds. This issue took me a while to track down because I was looking in the entirely wrong place (thought it must be a settings issue).
The text was updated successfully, but these errors were encountered:
After updating the latest Mupen64Plus-Next core in retroarch (core version 2.7-Vulkan 4249e39), the HUD was no longer showing correctly in Mario Kart 64 in a two-player game (single player worked but I only tried for a minute or so). No mini map was shown and no Items were shown. RDP was GLideN64.
Steps to reproduce:
Probably someone already noticed, but I am putting this here just in case.
Image that shows the issues attached.
Switching back to stable (2.6-Vulkan 5d2ac21) as included in retroarch v1.19.1 fixes the issue.
Cheers, AndBu
P.s. I feel like there should be an option to only download the latest stable cores when updating and it should be the default or the update functionality should come with a big fat warning that you are actually updating to nightly builds. This issue took me a while to track down because I was looking in the entirely wrong place (thought it must be a settings issue).
The text was updated successfully, but these errors were encountered: