libretro / libretro/RetroArch

content-directory-override / shader options don't work on subfolders

Open
#16,993 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Example:

I have a DOS games launched with the dosbox core and also windows 3.1 games that are launched with the dosbox core. I want to use different shader presets for dos games and windows 3.1 games. Both platforms have their games stored in individual folders.

The folder structure is as follows:

MS DOS
-- game folder 1
-- game folder 2
-- ...

Windows 3.1
-- game folder 1
-- game folder 2
-- ...

So since both platforms use the same core, I cannot use the save shaders for the whole core option. But I cannot use the "content directory" option either, because that does not work for subfolders.

What I'd like to see is an option in RetroArch that allows me to apply teh "content directory" option for all the subfolders of the content directory folder as well.

Is this possible?

Thx!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by locating RetroArch's content-directory and shader-option handling, then trace how paths are matched when content is inside nested folders. Done means content-directory shader settings apply consistently to the requested subfolders without changing core-wide behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.