Add Vulkan Support to RetroPie for Pi 4?

bluestang

@BuZz said in Add Vulkan Support to RetroPie for Pi 4?:

Also we don't run under x11 on the RPI. I'm confused as to what you are suggesting. We are not going to include a WIP driver and build retroarch against it.

Just out of curiosity, why is x11 not disabled if it is not a supported configuration? Upstream it is left to auto - https://github.com/libretro/RetroArch/blob/master/qb/config.params.sh#L83

This is very vague. Did you build debs, or install to /usr/local or.. if you want any changes considered or for us to test you will need to be more verbose please.

meson --prefix /usr -Dplatforms=x11,drm -Dvulkan-drivers=broadcom -Ddri-drivers= -Dgallium-drivers=v3d,kmsro,vc4 -Dbuildtype=release build
ninja -C build
sudo ninja -C build install

BuZz

@bluestang it was enabled (RPI+Kms only) some time ago in case we needed to use it on a per emulator basis (eg. Due to testing issues outside of X on kms). Originally enabled by another dev but having it enabled doesn't mean we support running on X in general on the RPI. RetroPie isn't just retroarch also.

bluestang

@BuZz said in Add Vulkan Support to RetroPie for Pi 4?:

Existing GLSL shader code is working?

So the Vulkan driver only sees slang shaders - https://github.com/libretro/slang-shaders (I commented out your existing shader path patch when I compiled RetroArch)

I copied the whole repo to the /opt/retropie/confis/all/retroarch/shaders and did not have problems navigating through all the folders that had the *.slangp files and selecting them. Obviously performance will vary on shader complexicity but the crt-pi one works nicely.

I also was able to save the shader preset options for game, core, or global and the shaders applied as set. For each type the respective *.slangp file is created.

Setting them through the Configuration Editor does not work though. It also appears that both sets of shaders are needed, the glslp ones for the GL driver and slanp for Vulkan.

Darksavior

@bluestang Last time I checked, the slang version of the crt-pi shader looks nothing like the glsl version, and looks quite ugly.

bluestang

@Darksavior I’m sure someone will improve the slang shaders for the pi when the time comes.

bluestang

@Darksavior I just took a look at the differences between the GLSL vs SLANG pi shaders...

To get the SLANG shader comparable to the GLSL one, you just need to change:

linear_filter0=true in the .slangp file
uncomment #define GAMMA in the .slang file

bluestang

@BuZz I haven’t tried your MESA repo in a bit for various extenuating circumstances but the RPi4 Vulkan driver was officially merged upstream today.

It only works on X11, and DRM/KMS support will be added later according to the devs. I believe focus now will be on performance since they implemented 1.0 features with this first release.

I’m sure that the Vulkan driver will makes its way to the Debian maintainers in the near term.

BuZz

@bluestang thanks for the info.

bluestang

@BuZz I made the jump to the 5.9 kernel and KMS video driver for the exact reasons @Brunnis stated.

I modified the sdl2.sh script to install v2.0.12 and I also installed upstream MESA with my own script.

With my MESA script though, I did not have to install libdrm2-.4.102. It installs the needed KMS/V3D/VC4 drivers and dependencies as was provided by the devs that worked the RPi4 Vulkan driver. In addition, I did some digging and I didn't see vc4 changes from 2.4.100 to 2.4.102 in libdrm...for the other Gallium drivers yes, but nothing for the RPi. My RetroPie image is still using libdrm2-4.100 and I'm running the latest of MESA, 5.9 kernel, and sdl2 v2.0.12.

I say all that to say, that your Mesa script could cut down on the dependencies needed if you strictly built the MESA stack for just the RPi drivers. This may be better in the long run since not all the dependencies are needed for the meson builder in upstream MESA. It will also save some space as you only build the Gallium drivers required for RPi - v3d,vc4,kmsro.

I need to try out the latest SDL2 with the atomic stuff but I will get to that at a later date.

BuZz

@bluestang as I have explained before I wanted to minimise my patch set. As this was made for my purposes, I want to build it with everything included as it would be when the Raspbian packages are updated.

I'm not interested in building a minimal Mesa.

bluestang

@buzz @mitu @dankcushions

There was an issue created about a week ago in upstream MESA to get Vulkan running in KMS/DRM. This involved getting the KHR_display extension added to the Pi4 Vulkan code base.

A contributor has done this and I am happy to report that RetroArch now works in KMS/DRM with the Pi4 Vulkan driver. It will be sometime before it gets merged into upstream MESA but it can be tested for now.

I've only tested FBNeo and MAME2K3+ and they work great. I did have to specify 1080p resolution using the retroarch.cfg settings:

video_fullscreen_x = "1920"
video_fullscreen_y = "1080"

Otherwise, it would default to 4K (my TV) which is a bit too much for the GPU.

I need to recompile 3D emus (i.e. Duckstation) with Vulkan support and do some more testing but I'd figure I'd pass along the news if you want to try it out too.

Some notes about my setup: (4GB Pi4)

5.9.3 kernel (32-bit)
vc4-kms-v3d display driver
MESA Vulkan build script here - https://pastebin.com/FnwWzbF2
RetroArch v1.9.0 with Vulkan support enabled
SDL2 v2.0.12 with Vulkan support enabled

dankcushions

@bluestang duckstation requires 64bit, fyi. i’ll try adding vulkan to my WIP branch soon

bluestang

@dankcushions said in Add Vulkan Support to RetroPie for Pi 4?:

@bluestang duckstation requires 64bit, fyi. i’ll try adding vulkan to my WIP branch soon

I am aware, here is the 64-bit version script - https://pastebin.com/9hggpAcK to install Vulkan on the Pi4. The only difference is dropping the neon flags since in 64-bit that is guaranteed.

I re-compiled RetroArch with the master branch since it now has your PRs with the correct GLES contexts for Duckstation. (3.1 is now the selected renderer)

I also tested out Vulkan w/ Duckstation and it worked in KMS/DRM. Here is the log for that - https://pastebin.com/z1FBuvWx

I tried FlyCast also but ran into segmentation faults. I need to do some more investigating.

Darksavior

@bluestang Do you have build scripts for ra1.9.0 vulkan and sdl2 vulkan?

bluestang

@darksavior said in Add Vulkan Support to RetroPie for Pi 4?:

@bluestang Do you have build scripts for ra1.9.0 vulkan and sdl2 vulkan?

The easiest way is to add the x11 platform flag to the system.sh script within the Pi4 function. This is not something that should be done unless you are prepared for possible broken builds.

I'm also using the master branch from RetroArch now as that has the proper GLES context selection now merged in.

Darksavior

@bluestang I'll wait for a proper script then.
Trying 5.10 with kms driver since building the kernel makes my pads work. Not trying 64bit since I use redream and the pegasus-frontend.

bluestang

Direct display support is now part of the Pi4's MESA repo. Vulkan apps can now take advantage of rendering direct to the display without using X11 , etc.

Some emulators have this support and some do not. Vulkan implementations across various 3D emulators vary a bit. Because the Vulkan API is explicit in nature, it falls on the developer to implement their windowing system of choice.

@vanfanel is working some SDL KMS changes but not sure what the exact changes are. As of now Vulkan support in SDL2 KMS/DRM is non-existent. Hopefully he can change that soon.

bluestang

@BuZz @dankcushions @mitu

https://www.raspberrypi.org/blog/vulkan-update-were-conformant/

There is one last MR pending but it is a trivial change. As my last post says some emus work, some do not.

I’ll be re-addressing my issue with lr-flycast shortly. DuckStation was working on 64-bit, I’d forgotten how well the soundtrack was for Ace Combat 2. Mame emus worked fine for me.

Darksavior

@bluestang Can you test out Beetle PSX with vulkan?

DreamcastKid

@bluestang said in Add Vulkan Support to RetroPie for Pi 4?:

https://www.raspberrypi.org/blog/vulkan-update-were-conformant/

Nice to hear some good news this year :)

Excited to see the new possibilities with emulation performance on Raspberry Pi :D