@pi4papiba I'm using the Monkabuntu 2.0 64bit Ubuntu build. My MESA is 220.127.116.11
This isn't my primary build for my Pi, My official Pi 4 Retropie image is so my MESA is the current (updated a few weeks ago) stable build that Retropie-update installs. I did consider trying downloading a more cutting edge version but I want to keep my Retropie build stable without having to modify the firmware back.
When things are more stable I may try an installation of Dolphin over Raspberry Pi OS. This build has several emulators installed but performance on N64 and PSP seems to be much worse than on my official build so I have not bothered with them.
Out of interest have you been able to successfully connect a real Wiimote on your build? I can connect it but the emulator disables it when the game starts. If I could connect my Wiimote then I could probably give Wii games a more thorough testing. Now I've got some Gamecube games to run at 30FPS I think some Wii game may be viable.
Most of the links go over similar steps for compiling, installing, and testing Vulkan and its demos. Some additional notes:
The older posts point to a developer's fork of Mesa. Now that Vulkan has been merged into Mesa, whereever you see a git clone you'll want to make sure that you're pointing to Mesa's repository (https://gitlab.freedesktop.org/mesa/mesa/)
You'll be able to get Vulkan from the master branch of of the Mesa repository. It doesn't look like it's been tagged to a release yet, so there's likely more work to be done and your mileage may vary.
You can actually have different versions of Mesa installed on your system simultaneously, as long as you put them in different directories. In order to ensure stability of my Pi systems, I do this, so I can test and play around while not worrying about everything else. Though Mesa is pretty self contained so it's not too hard to get things back to normal if you overwrite the original drivers.
If you have compiled Mesa for installation in another directory, then you'll need to add the following line to your launch scripts or your bash profile in order to point programs to your special installation. You do that with the following line:
export VK_ICD_FILENAMES=[YOUR INSTALLATION PATH]/share/vulkan/icd.d/broadcom_icd.armv7l.json
I've found that Raspbian/Raspberry Pi OS (which is what RetroPie is built on) actually uses NVIDIA's Vendor Neutral Dispatch version of Mesa (which uses code from Mesa), and not Mesa's version of Mesa. I have no idea if that will be changing or not, but it at least indicates that there will be more work to do before we see Vulkan drivers as part of Raspbian/Raspberry Pi OS/RetroPie as a default.
I've been playing around with Vulkan and so far it's looking pretty good. I have high hopes that as programs begin to adopt Vulkan we'll be seeing some really awesome performance increases. I have not tried Dolphin though. The only thing I've found regarding Dolphin and Vulkan was someone testing it out on a Jetson Nano, which is a different hardware platform. He did compare Vulkan vs. OpenGL and found that Zelda: Wind Walker ran very well with Vulkan where it was choppy on OpenGL. The post is on Facebook (https://www.facebook.com/groups/retropieofficial/permalink/1387063751494192/).
I created a scriptmodule for my own purposes to automate building / installation of Mesa with Vulkan. I may create a separate post for that.
You need to launch the dolphin-emu program from the /opt/retropie/emulators/dolphin/bin/ folder first. You can do that from command-line or through a file explorer in the desktop environment. This should bring up the GUI version of dolphin. It wont launch a game, but it will show the window for the program.
I have solved the audio issue. I looked back at my es_systems.cfg file in my .emulationstation folder. I noticed that it points to the RetroArch executable in D:\ (my microSD card). I double clicked it and went to the Audio driver section/Output to make sure that audio was turned on. The Audio was also changed from xaudio to dsound. I also went to the Driver section to make that Audio was identified as dsound there as well.
EDIT: wow performance is absolute garbage, how can this be, i looked in some forums, and everybody is like "oh you need dual core" dude i have a quad core 3.4 Ghz i7? Is it the settings or is it ubuntu itself?
I'm new to retropie, the PI4 was sleeping nearly a year until I guess I found a project where I want to use it. :-)
although well documented on the github it is not for raspberry pi, did anybody try to compile and build it as a selectable option in retropie based on a raspberry pi 4, suceeded and has a half-newbie howto for this? :-)
@grant2258 Thank you for the response! I certainly can use the standalone version, which I will probably end up doing. I want to eventually (possibly) replace my Raspberry Pi with a small laptop that runs RetroPie, since I have access to better hardware. So I was hoping to setup a system I can connect to the TV and use the interface entirely with the controller.
I'll just have to make due for now, and choose a solution that suits me best.