Duncan 64405469a5 Expand FallbackImage to include a GpuImage for each possible TextureViewDimension (#6974) ... # Objective Fixes #6920 ## Solution From the issue discussion: > From looking at the `AsBindGroup` derive macro implementation, the fallback image's `TextureView` is used when the binding's `Option<Handle<Image>>` is `None`. Because this relies on already having a view that matches the desired binding dimensions, I think the solution will require creating a separate `GpuImage` for each possible `TextureViewDimension`. --- ## Changelog Users can now rely on `FallbackImage` to work with a texture binding of any dimension.		2023-06-19 22:56:25 +00:00
..
src	Expand FallbackImage to include a GpuImage for each possible TextureViewDimension (#6974)	2023-06-19 22:56:25 +00:00
Cargo.toml	update syn, encase, glam and hexasphere (#8573)	2023-05-16 01:24:17 +00:00