Andreas Reich
Andreas Reich
> Hit another snag though on the Naga side: the module -> wgsl writeout that is used when targeting WebGPU isn't emitting enable directives either right now :sigh: practically oftopic...
Thanks for all the logs on those variations! May be related to the hybrid setup. I know that for some folks Vulkan on wayland works just fine and for other...
@emilk still a problem for me on latest `main`. You've looked at the wrong thing? The problem here is that in the time series view (not the timelien) hovering a...
the PR that fixed this was reverted
An instance of tagged component @jleibs and me discussed recently is fill out and wireframe color in a situation where both solid & fill are supported at the same time...
ah, that's the issue I was looking for actually. ... closing the old one as duplicate because this one has more info.
Actually, this also hints at a missing validation in wgpu-core!
chrome gives you `Wgpu validation error 18446744073709551615: Value 31 is invalid for WGPUShaderStage.` wgpu-core is not validating unsupported (or from pov of WebGPU) invalid shader stages, thus causing unexpected discrepancy...
@SupaMaggie70Incorporated I think you're missunderstanding: wgpu-core does **not** do any validation on this today. But Chrome does for WebGPU (on this path there's no wgpu-core involved) which is what causing...