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

Put some implementation dependent values of FSR under pipeline FSR instead of attachment FSR #600

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

Conversation

PanGao-h
Copy link

@PanGao-h PanGao-h commented Feb 3, 2024

In Vulkan, fragmentShadingRateNonTrivialCombinerOps must be VK_FALSE unless either the primitiveFragmentShadingRate or attachmentFragmentShadingRate feature is supported. But the table here is under shading_rate_attachment alone. It's a bit confusion. This MR tries to make the connection between Vulkan/OpenGL ES explicit.

In Vulkan, `fragmentShadingRateNonTrivialCombinerOps` must be VK_FALSE unless
either the `primitiveFragmentShadingRate` or `attachmentFragmentShadingRate` feature is supported. But the table here is under shading_rate_attachment alone. It's a bit confusion. 
This MR makes the connection between Vulkan/OpenGL ES a bit more obvious.
@PanGao-h PanGao-h marked this pull request as draft February 6, 2024 03:46
@PanGao-h
Copy link
Author

PanGao-h commented Feb 6, 2024

In a detailed check with Vulkan spec for Limite Requirements, move more items that are covered in feature pipelineFragmentShadingRate. For example:

Type Limit Feature
VkBool32 fragmentShadingRateWithShaderDepthStencilWrites pipelineFragmentShadingRate
VkBool32 fragmentShadingRateWithSampleMask pipelineFragmentShadingRate

@PanGao-h PanGao-h changed the title Clarify non-trivial combiner could be used when either primitive or attachment shading rate feature is supported Put some implementation dependent values of FSR under pipeline FSR instead of attachment FSR Feb 6, 2024
@PanGao-h PanGao-h marked this pull request as ready for review February 6, 2024 09:54
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.

None yet

2 participants