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

MVKGraphicsPipeline: Don't use _tessInfo to decide if pipeline is a tessellation pipeline. #2244

Merged
merged 1 commit into from
May 31, 2024

Conversation

js6i
Copy link
Collaborator

@js6i js6i commented May 30, 2024

With dynamic patch control points enabled, the pipeline does not need to be created with tessellation info included in the create info. Store a separate boolean flag to treat all pipelines that have tessellation shaders properly.

…essellation pipeline.

With dynamic patch control points enabled, the pipeline does not need to be
created with tessellation info included in the create info. Store a separate
boolean flag to treat all pipelines that have tessellation shaders properly.
@billhollings billhollings merged commit dc6d383 into KhronosGroup:main May 31, 2024
6 checks passed
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.

3 participants