reshade: update ReShade FX support up to v6.6.2#2195
Open
pchome wants to merge 1 commit into
Open
Conversation
Author
|
Yes, should have been the draft PR to not trigger CI ... Also FYI: CI seems needlessly recursive-cloning reshade repo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is just a hint to anyone who willing update reshade submodule.
But actually this is mainly it. Expected to just work after bump to v6.6.2.
ReShade FX v6.7.3 is a different story. They removed SPIR-V code output from
codegen->finalize_code()and I can't figure out how it should work now.However I have patched version (reverted finalize_code() change)
here.
The repository itself contains files to build shared ReShadeFX library, in case someone interested in.
BTW the next ReShade release will (seems) support cmake and Linux (for static ReShadeFX library and some examples).