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
When you start a game from command line with a shader included, cycling with N or M keys changes to retroarch/shaders folder, instead of the subfolder where the selected shader was. This doesn't happen if the shader is selected from Retroarch's menu.
Expected behavior
N and M keys should cycle between the rest of the shaders in the selected shader folder.
Actual behavior
N and M keys cycle to whatever shaders are in the retroarch/shaders folder instead.
Steps to reproduce the bug
Start a game from command line, selecting a shader in the process.
Try to cycle between shaders with the N and M keys.
Version/Commit
RetroArch: [1.16.0/14cb373]
Environment information
OS: Windows
The text was updated successfully, but these errors were encountered:
zoltanvb
added a commit
to zoltanvb/RetroArch
that referenced
this issue
Feb 3, 2024
If shader is given on command line, use it for directory init.
Fixeslibretro#16181, shader cycle should now work using the dir of the
shader passed to CLI.
If shader is given on command line, use it for directory init.
Fixeslibretro#16181, shader cycle should now work using the dir of the
shader passed to CLI.
Description
When you start a game from command line with a shader included, cycling with N or M keys changes to
retroarch/shaders
folder, instead of the subfolder where the selected shader was. This doesn't happen if the shader is selected from Retroarch's menu.Expected behavior
N and M keys should cycle between the rest of the shaders in the selected shader folder.
Actual behavior
N and M keys cycle to whatever shaders are in the
retroarch/shaders
folder instead.Steps to reproduce the bug
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: