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

Intel MSAA Resolve + SRGB #725

Closed
2 tasks
cwfitzgerald opened this issue Jun 15, 2020 · 3 comments
Closed
2 tasks

Intel MSAA Resolve + SRGB #725

cwfitzgerald opened this issue Jun 15, 2020 · 3 comments
Assignees
Labels
external: driver-bug A driver is causing the bug, though we may still want to work around it type: bug Something isn't working

Comments

@cwfitzgerald
Copy link
Member

cwfitzgerald commented Jun 15, 2020

Description

On intel/linux systems, there is a long standing issue with doing MSAA resolve at the same time as SRGB resolve will cause MSAA not to work and the clear color to not be properly converted into SRGB.

Platform

Linux + Intel GPU

What we do

  • Verify this doesn't affect windows
  • We need to warn when doing MSAA and SRGB on an intel chip on affected platforms.
@cwfitzgerald cwfitzgerald added the type: bug Something isn't working label Jun 15, 2020
@cwfitzgerald cwfitzgerald self-assigned this Jun 15, 2020
@kvark kvark added the external: upstream Issues happening in lower level APIs or platforms label Jun 16, 2020
@kvark
Copy link
Member

kvark commented Jun 16, 2020

gfx-rs has some internal logic to work around bugs, so in general we should first consider putting a workaround there. Perhaps what we should do for this issue is change image_format_properties implementation on Vulkan to report the maximum MSAA count of 1 only for SRGB formats only on the affected platforms?

Edit: we'd modify the sample_count_mask based on the target OS and some HW info like one defined here.

In wgpu, we may still need something - like a proper check for the sample count mask (if we don't have one), but at least it would be backend-agnostic at this level.

@cwfitzgerald
Copy link
Member Author

I think we've fixed this.

@mockersf
Copy link
Contributor

this seems to still happen in Bevy with wgpu 0.16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external: driver-bug A driver is causing the bug, though we may still want to work around it type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants