Elabajaba

> my CI just got updated to Firefox 128 and can now reproduce this error so... yay 🎉 What GPU is the CI running on? I'm pretty sure this is...

> Why is it that my GPU is a RX 460, but bevy reports an R9 200? Firefox buckets all GPUs into a few different device names for privacy reasons...

The ASTC coverage seems low if we're going for vulkan capable android. https://vulkan.gpuinfo.org/listoptimaltilingformats.php?platform=android has it at ~99% supported.

[LZ4 1.10](https://github.com/lz4/lz4/releases/tag/v1.10.0) is out now with multithreaded compression, which gives some nice speedups at higher compression levels. Here's the PR that added multithreading https://github.com/lz4/lz4/pull/1336

This is something that needs to be fixed at the graphics api (eg. wgpu)/engine level, and can't be fixed in winit afaik. On dx12 I'd probably just disable fullscreen exclusive...

> Could there be any other fixes for this, @Elabajaba ? This has been a problem for many of my own users and I've yet to find solutions for bevy....

I can't reproduce this on AMD+Windows 11 on either bevy 0.10.1 or bevy main (10f5c9206847ae01b8dc833c2680562e7bd46664). ``` SystemInfo { os: "Windows 11 Pro", kernel: "22621", cpu: "AMD Ryzen 9 5900X 12-Core...

I think we need something like wgpu's supported platforms table. https://github.com/gfx-rs/wgpu?tab=readme-ov-file#supported-platforms > My personal vote is for "leave it as is". There is no harm in cataloging this information and...

I ran the renderpass benchmarks through superluminal (with `[profile.bench] debug=1` in `Cargo.toml`), and all logging seems to be completely disabled during them, so I'm not sure how useful they are...

> I assumed so far that the entire logging performance discussion is on the premise that most logs are not rendered All the bevy performance results have been with only...