Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add LetMeReShade Plugin #757

Open
wants to merge 21 commits into
base: main
Choose a base branch
from
Open

Add LetMeReShade Plugin #757

wants to merge 21 commits into from

Conversation

itsOwen
Copy link
Contributor

@itsOwen itsOwen commented Feb 5, 2025

LetMeReShade Plugin

A seamless ReShade integration for Steam Deck that enables advanced shader customization and graphics enhancement. This plugin provides easy ReShade installation, game-specific shader application, and preset management.

Task Checklist

Developer

  • I am the original author or an authorized maintainer of this plugin.
  • I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin

  • I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
  • I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

  • No: I am using a custom backend other than Python.
  • No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
  • No: I am using a custom binary that has all of it's dependencies statically linked.

Community

  • I have tested and left feedback on two other pull requests for new or updating plugins.
  • I have commented links to my testing report in this PR.

Testing

  • Tested on SteamOS Stable or Beta update channel.

@itsOwen itsOwen requested a review from a team as a code owner February 5, 2025 17:20
@EMERALD0874
Copy link
Member

@itsOwen This plugin has similar issues we're addressing with #751 regarding curl statements being moved to the remote binary system. I'd rather not create standards for what should(n't) be using that system across multiple PRs, so I'm going to hold off on a code review until we're either blocked on that PR or we've agreed on a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants