Repository navigation
GS/Shaders: Disable unused cas functions to get around intel specific driver issues. - #15108
Merged
Merged
Conversation
Gets around intel specific driver bugs.
lightningterror
force-pushed
the
gs_intel_cas_driver_bug
branch
from
October 23, 2026 10:59
a36c535 to
6a120c3
Compare
JordanTheToaster
approved these changes
Oct 23, 2026
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.
Description of Changes
GS/Shaders: Disable unused cas functions.
The following code ACpySgnF1-4, as well as ASignedF1-4 causes compilation issues on Intel HD4000 in combination with windows 11 which is likely a driver issue which seems to be either related to macro nesting or signed/unsigned types. Windows 10 might be fine. Since we don't currently use this code we can just disable it for now instead of working around it.
Rationale behind Changes
Bugfix, regression fix.
Suggested Testing Steps
Smoke test if CAS still works on all renderers, Sly2 is a good testcase.
Did you use AI to help find, test, or implement this issue or feature?
Yes Claude for helping debug the issue faster, it also came to the same conclusion that this may be a driver issue, and according to it the functions are unused so we don't have to add any alternative handling/workarounds for now.