Nicola Papale ffa489a846 Ignore Timeout errors on Linux AMD & Intel (#5957) ... # Objective - Fix #3606 - Fix #4579 - Fix #3380 ## Solution When running on a Linux machine with some AMD or Intel device, when calling `surface.get_current_texture()`, ignore `wgpu::SurfaceError::Timeout` errors. ## Alternative An alternative solution found in the `wgpu` examples is: ```rust let frame = surface .get_current_texture() .or_else(|_| { render_device.configure_surface(surface, &swap_chain_descriptor); surface.get_current_texture() }) .expect("Error reconfiguring surface"); window.swap_chain_texture = Some(TextureView::from(frame)); ``` See: <94ce76391b/wgpu/examples/framework.rs (L362-L370)> Veloren [handles the Timeout error the way this PR proposes to handle it](https://github.com/gfx-rs/wgpu/issues/1218#issuecomment-1092056971). The reason I went with this PR's solution is that `configure_surface` seems to be quite an expensive operation, and it would run every frame with the wgpu framework solution, despite the fact it works perfectly fine without `configure_surface`. I know this looks super hacky with the linux-specific line and the AMD check, but my understanding is that the `Timeout` occurrence is specific to a quirk of some AMD drivers on linux, and if otherwise met should be considered a bug. Co-authored-by: Carter Anderson <mcanders1@gmail.com>		2022-11-12 08:06:56 +00:00
..
macros	Use new let-else syntax where possible (#6463)	2022-11-04 21:32:09 +00:00
src	Ignore Timeout errors on Linux AMD & Intel (#5957)	2022-11-12 08:06:56 +00:00
Cargo.toml	Update glam 0.22, hexasphere 8.0, encase 0.4 (#6427)	2022-11-07 19:44:13 +00:00