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.
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
Metal: Add MetalFX upscaling support #99603
Metal: Add MetalFX upscaling support #99603
Changes from all commits
11dc4f2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it worth putting this behind a support check so platforms without metalfx won't show those options?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per @clayjohn, these need to be included in the public APIs, so that they can be selected on a per-platform basis. Windows will have the option for a DirectX-specific scaler too. There may still be some details to work out here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember that different users working on the same project might be able to see those options, so if you couldn't, the scene would be saved with different values once you save it in the editor (since your inspector's enum would have fewer options available).
Therefore, the set of available properties in the inspector should remain the same across platforms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was thinking about removing this comment because definitely the simplest and least surprising thing would be to just list all options although FWIW setting this to an unsupported value causes it to fallback to not using scaling at runtime but it doesn't overwrite the project settings file even when other options are changed.
Maybe an option later on would be higher level cross platform options like
Off, Bilinear, Spatial, Temporal
with flags to allow those to defer to platform specific apis when available/appropriate, so if a project was using metal by default it would use fsr automatically rather than disabling scaling entirely on a non-mac. That might be too rigid for other scaling options to fit in, for example it looks like DirectSR does not make the distinction in the same way, but I imagine this will come up for other api specific additions in the future like frame gen.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now done – we have specialisation options for
ios
andmacos
.