Is your feature request related to a problem? Please describe.
Different platforms have strange MSAA requirements, so there needs to be some way of exposing this through wgpu so programs can not crash. This ultimately needs to be a problem that is solved by WebGPU for exposing properly, but we can lead off with a temporary api which can be adjusted later. gpuweb/gpuweb#108 is mildly related, though old.
Describe the solution you'd like
Pass forward framebufferColorSampleCounts, framebufferDepthSampleCounts, and framebufferStencilSampleCounts from gfx-hal as native-only limits.
Describe alternatives you've considered
Not supporting this isn't ideal as it requires the developer to accurately know what hardware they are on, and what features it supports. This is a little silly when we can just ask the api.
Additional context
OSX seems to not support > 4x at least on macbook pros. Phones may also have strange requirements.
Is your feature request related to a problem? Please describe.
Different platforms have strange MSAA requirements, so there needs to be some way of exposing this through wgpu so programs can not crash. This ultimately needs to be a problem that is solved by WebGPU for exposing properly, but we can lead off with a temporary api which can be adjusted later. gpuweb/gpuweb#108 is mildly related, though old.
Describe the solution you'd like
Pass forward framebufferColorSampleCounts, framebufferDepthSampleCounts, and framebufferStencilSampleCounts from gfx-hal as native-only limits.
Describe alternatives you've considered
Not supporting this isn't ideal as it requires the developer to accurately know what hardware they are on, and what features it supports. This is a little silly when we can just ask the api.
Additional context
OSX seems to not support > 4x at least on macbook pros. Phones may also have strange requirements.