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

Overdraw: Check for format support and convert if necessary #2097

Merged
merged 4 commits into from
Aug 3, 2018

Conversation

sean-purcell
Copy link
Contributor

This also requires adding to the extras on vkEnumeratePhysicalDevices to check what formats the device supports. I set it up to just get the format support for all formats, but if that is too expensive this feature only needs to know support for the stencil formats.

@ben-clayton
Copy link
Contributor

Am I right in thinking you're getting information about the trace device, storing this in the capture as an extra, and then using this to determine what you should do for replay? If so, we should chat.

@ben-clayton
Copy link
Contributor

Hi Sean.

I've filed #2101 to track my concerns here. I know this is your last week, so I won't block this.

@sean-purcell
Copy link
Contributor Author

Thanks Ben, I agree it's not ideal. If we were to loosen the "replay on original device" restriction at some point I don't think the modifications to this would be too complex.

@AWoloszyn AWoloszyn merged commit 3dec793 into google:master Aug 3, 2018
@sean-purcell sean-purcell deleted the overdraw-format branch August 3, 2018 20:10
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