Content directory specific shader configuration is not loaded when core changes
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
I don't know if this is working as intended or not, but do this:
Save shader configuration as content-directory specific
Change core
Load same content
-> Shader configuration is ignored.
Either the description needs to be made more clear or there is a bug.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. First reproduce the reported sequence: save a content-directory-specific shader configuration, change the core, and reload the same content; then trace the shader configuration loading path and verify whether the configuration is retained after the core change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100