Cherry Pick Fix logic for determining the file extension for shader files #17784
Conversation
This file contains 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
…7689) Signed-off-by: Steve Pham <82231385+spham-amzn@users.noreply.github.com>
spham-amzn
changed the title
lemonade-dm
approved these changes
Apr 20, 2024
AMZN-daimini
approved these changes
Apr 22, 2024
spham-amzn
deleted the
cherry_pick_fix_cheate_shader_variant_python_script
branch
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.
What does this PR do?
Cherry pick for fixing the logic for determining the file extension for shader files from #17689
How was this PR tested?
Run on the Shader Management Console on Linux on a system that has '.' in the current working directory