This probably won't add anything to the conversation but here's what happened to me today - sounds almost the same.

My older SN30 controllers were connecting via Bluetooth and in Emulation Station they would work fine. All buttons did what they were supposed to. When I tried to play a game with them the D-Pad worked BUT ABXY weren't even registering and for some reason START was acting like B. Turns out my controllers were on 3.00 Firmware. I updated them to 4.20 (looks like the SN30 Pro latest firmware is v1.34), deleted the Bluetooth entry, rebooted and then paired them again using the 8BitDo guide. Now they work exactly as they should. It was just a firmware issue for me. I didn't see it mentioned in the thread so just putting in my 2 cents. :)

Good luck!

@jimmyfromthebay said in Optimal settings for Asteroids and other vector games?:

@roslof said in Optimal settings for Asteroids and other vector games?:

Optional: There is a glow shader with the shaders_glsl package under "blurs" called kawase_glow.glsplp. It's nice, but hits perf a little and might be a bit much

Where might this be found, btw?

https://github.com/libretro/glsl-shaders

Thanks guys. Here's two for Playstation:
Playstation.png Playstation2.png

And the one that started all this for me:
AtariXEGS.png

@mechafatnick
I know, what you have done work very well. Honnestly, It's awesome! That's why I would like to continue to use it. Can you provide a link with what you have done, but not compiled with Makefiles. I would like to get what you have done but modify inputs.cpp

like this :

uiExit = AddSwitchInput("UIExit", "Exit UI", GAME_INPUT_UI, "KEY_ESCAPE,JOY1_BUTTON1+JOY1_BUTTON10");

or

uiExit = AddSwitchInput("UIExit", "Exit UI", GAME_INPUT_UI, "JOY1_BUTTON1+JOY1_BUTTON10");

and after that use Makefiles

@stoo While I haven't been able to replicate the weird performance problem I was getting before, I see why OpenGL is failing intermittently.

Seemingly at random when switching AA values, a shader fails to compile. It doesn't happen every time, but maybe 50% of the time?

[libretro INFO] [LibretroHostInterface] Hardware context reset, type = 5 [INFO] [Environ]: GET_SAVE_DIRECTORY. [libretro INFO] [LibretroHostInterface] Shader cache directory: '/home/pi/RetroPie/roms/psx//duckstation_cache/' [libretro INFO] [GPUBackend] GPU thread stopped. [libretro INFO] [GPU_HW_OpenGL] Max texture size: 4096x4096 [libretro INFO] [GPU_HW_OpenGL] Per-sample shading: not supported [libretro INFO] [GPU_HW_OpenGL] Max multisamples: 4 [libretro INFO] [GPU_HW_OpenGL] Uniform buffer offset alignment: 256 [libretro WARN] [SetCapabilities] GL_EXT/OES_copy_image missing, this may affect performance. [libretro INFO] [GPU_HW_OpenGL] Max fragment shader storage blocks: 16 [libretro INFO] [GPU_HW_OpenGL] Max shader storage buffer size: 134217728 [libretro INFO] [GPU_HW_OpenGL] Using shader storage buffers for VRAM writes. [libretro INFO] [GPUBackend] GPU thread started. [libretro INFO] [GPU_HW] Resolution Scale: 1 (1024x512), maximum 4 [libretro INFO] [GPU_HW] Multisampling: 4x [libretro INFO] [GPU_HW] Dithering: Disabled [libretro INFO] [GPU_HW] Texture Filtering: Nearest-Neighbor [libretro INFO] [GPU_HW] Dual-source blending: Not supported [libretro INFO] [GPU_HW] Using UV limits: NO [libretro INFO] [GPU_HW] Depth buffer: NO [libretro INFO] [GPU_HW] Downsampling: Disabled [libretro INFO] [GPU_HW] Using software renderer for readbacks: YES [INFO] [Environ]: GET_SAVE_DIRECTORY. [libretro INFO] [LibretroHostInterface] Shader cache directory: '/home/pi/RetroPie/roms/psx//duckstation_cache/' [libretro INFO] [GL::ShaderCache] 0 program binary formats supported by driver [libretro WARN] [Open] Your GL driver does not support program binaries. Hopefully it has a built-in cache, otherwise startup will be slow due to compiling shaders. [libretro INFO] [HostInterface] Loading: Compiling Shaders 81 of 0-156 [libretro ERROR] [CompileShader] Shader failed to compile: 0:105(68): error: `gl_SampleID' undeclared 0:105(63): error: cannot construct `uint' from a non-numeric data type 0:105(59): error: cannot construct `int' from a non-numeric data type 0:105(17): error: no matching function for call to `texelFetch(sampler2DMS, ivec2, error)'; candidates are: 0:105(17): error: vec4 texelFetch(sampler1D, int, int) 0:105(17): error: ivec4 texelFetch(isampler1D, int, int) 0:105(17): error: uvec4 texelFetch(usampler1D, int, int) 0:105(17): error: vec4 texelFetch(sampler2D, ivec2, int) 0:105(17): error: ivec4 texelFetch(isampler2D, ivec2, int) 0:105(17): error: uvec4 texelFetch(usampler2D, ivec2, int) 0:105(17): error: vec4 texelFetch(sampler3D, ivec3, int) 0:105(17): error: ivec4 texelFetch(isampler3D, ivec3, int) 0:105(17): error: uvec4 texelFetch(usampler3D, ivec3, int) 0:105(17): error: vec4 texelFetch(sampler2DRect, ivec2) 0:105(17): error: ivec4 texelFetch(isampler2DRect, ivec2) 0:105(17): error: uvec4 texelFetch(usampler2DRect, ivec2) 0:105(17): error: vec4 texelFetch(sampler1DArray, ivec2, int) 0:105(17): error: ivec4 texelFetch(isampler1DArray, ivec2, int) 0:105(17): error: uvec4 texelFetch(usampler1DArray, ivec2, int) 0:105(17): error: vec4 texelFetch(sampler2DArray, ivec3, int) 0:105(17): error: ivec4 texelFetch(isampler2DArray, ivec3, int) 0:105(17): error: uvec4 texelFetch(usampler2DArray, ivec3, int) 0:105(17): error: vec4 texelFetch(sampler2DMS, ivec2, int) 0:105(17): error: ivec4 texelFetch(isampler2DMS, ivec2, int) 0:105(17): error: uvec4 texelFetch(usampler2DMS, ivec2, int) 0:105(17): error: type mismatch [libretro ERROR] [Initialize] Failed to compile programs [libretro ERROR] [CreateGPU] Failed to initialize OpenGL renderer, falling back to software renderer [INFO] [Environ]: SET_MESSAGE: Failed to initialize OpenGL renderer, falling back to software renderer. [libretro INFO] [GPUBackend] GPU thread stopped. [libretro INFO] [GPUBackend] GPU thread started.

When this happens, it says it's falling back to Software rendering, but a black screen appears instead. The game is still running, audio is playing but no display. You can switch internal resolutions up or down to force it to initialize the OpenGL renderer again and it usually comes back.

No idea if this is a bug in duckstation, Retroarch or a GL driver bug. I'm using glcore.

Do you have the Pi in a case that could interfere with wireless ? Are you using the USB3 or USB 2 ports for the BT dongle ?

@bizt go into the retroarch settings from the emulator. Back out until you see settings and select that. Then go to video, and then change the aspect ratio to either 4:3 or default. Then go back a couple menus and go to to
Configuration, then save core overrides.
Another option if you wanted to keep the stretched out 16:9 image, it turning on Bilinear filtering in the same video menu, and then save the core overrides for that. The filter helps smooth out the chunkyness of ps1 games. Or do a combination of both

@wolfyn-claw That won't work on a stadard RetroPie image or on Raspberry Pi OS, since it's a 32bit (armhf) version. Support for the beta 64 bit image of Raspberry Pi OS is still beta at the moment in RetroPie, so YMMV if you wish to install it (manually, since there's no image provided for it).
FWIW, there are a few topics here in the forums with Dolphin installations - you can take a look at how other users have installed it and what are their experience with it.

@yfzdude said in Trouble creating desktop launcher file [SOLVED]:

I'm still curious if any GNU/Linux wizards know why the original method was not working. Either way it is working now.

Because runcommand needs a terminal to show the launch menu, launching ES directly would break this. On Debian and friends, you can use x-terminal-emulator as the terminal starting command, which would be expanded to one of the installed terminal emulators.

Ok i will try . I don't think it'll work though. If use startx it basically ignores second line.
I had tried it with many a script before finding this forum thread.

Never mind, fixed it :)

I think I'd crossed the streams while flailing at the options. The key is to add -gameio joy to emulators.cfg, so that it reads like this:

lr-mess-apple2 = "/home/pi/RetroPie-Setup/scriptmodules/run_mess.sh /opt/retropie/emulators/retroarch/bin/retroarch /opt/retropie/libretrocores/lr-mess/mess_libretro.so /opt/retropie/configs/apple2/retroarch.cfg apple2e /home/pi/RetroPie/BIOS -gameio joy -flop1 %ROM%"

And then go into the MESS menu and set the analog controls up like this:

ap2.jpg

The key is those "P1 Joystick X Analog" and "P1 Joystick Y Analog" lines - you have to make sure those are set to "None", which isn't the default. Take those two steps and you should be sorted.

@kiddzeal if you update to the latest retropie (you'll need to start from a fresh image at this point) you can try the experimental new psx emulator 'lr-duckstation' which i expect plays this game well (it's been very good for most things).

there's likely little you can do to resolve issues with pcsx_rearmed -it's a mostly abandoned emulator.

I was hoping maybe we could have some information here about the issues surrounding preliminary v19 builds because I'm curious --- I've been looking around the RPi org and Kodi forums and it's not clear to me if there's technical problems that need sorting or just time to compile the package.

I'd love to help out with testing like I did for 18.x. I'm also hoping that with the latest 19.1 release might have eased RPi issues on the Kodi side if truly blocking if any were there on the initial 19.0 release.

There seems to be some compatibility issues around higher res videos and the latest kernel versions, but that doesn't seem to be unique to Kodi 19. Or are there kms/vlc considerations too?

Some reading I've bumped into so far:

https://www.raspberrypi.org/forums/viewtopic.php?f=35&t=312199&p=1867804&hilit=rascas#p1867804

https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=251645&p=1874730&hilit=kodi#p1874730

https://github.com/raspberrypi/linux/issues/4112

Slightly unrelated, but I'm also curious why packages like this could be compiled in RetroPie directly rather than a curated binary release? Are there dependency differences just pointing at the libreELEC / OSMC repositories? I'm out of my depth probably here --- but they've had test builds and from what I've gathered they kind of work.

I don't mean to sound too impatient or ungrateful, but I've hit a few issues now, at least one that was fixed between 18.7 and 18.9 --- and as others have mentioned I'd love to take a look at the new features too. Also, some of my Kodi plugins are already reporting updates that are for Python 3 only.

Thanks in advance for any updates!

mkreisl created this issue in raspberrypi/linux open Kernel 5.10 - RPI3 - Kodi 18.x does not play HEVC videos anymore #4112