64405469a5
# 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. |
||
|---|---|---|
| .. | ||
| android-res/mipmap-mdpi | ||
| branding | ||
| data | ||
| environment_maps | ||
| fonts | ||
| models | ||
| pixel | ||
| scenes | ||
| shaders | ||
| sounds | ||
| textures | ||