Unsupported GL_EXT_texture_shadow_lod causes panic in PBR pipeline about bevy HOT 4 OPEN

@ByteNybbler thanks for the info! Removing the milestone then.

from bevy.

Am I understanding it correctly that this did not happen in 0.13 and is due to the wgpu update?
Update: yes, gfx-rs/wgpu#5171 is part of WGPU 0.20.0 which is first used by Bevy 0.14.
As such, this is a regression: some older hardware can no longer run Bevy stuff.

Open question: is this important? How many machines are affected? I'd like to test this, but I don't know how to force WGPU to use my integrated GPU (other than physically removing my actual GPU of course).

Running the pbr example on OpenGL on my dedicated GPU at least renders fine but spams the following hundreds of times:

I don't think this is related to this issue in particular, but worth noting.

from bevy.

Set the WGPU_ADAPTER_NAME environment variable to force a specific GPU: https://github.com/gfx-rs/wgpu?tab=readme-ov-file#environment-variables

from bevy.

Am I understanding it correctly that this did not happen in 0.13 and is due to the wgpu update? Update: yes, gfx-rs/wgpu#5171 is part of WGPU 0.20.0 which is first used by Bevy 0.14. As such, this is a regression: some older hardware can no longer run Bevy stuff.

I switched to v0.13.2 and tried WGPU_BACKEND=gl cargo run --example pbr and I still got the same 'GL_EXT_texture_shadow_lod' is not supported errors as above. This seems to prove that gfx-rs/wgpu#5171 is not the cause of this error, and therefore this doesn't seem to be a regression (as far as I can tell, anyway).

Open question: is this important? How many machines are affected?

I think my integrated GPU is around a decade old now. However, it can run almost every game I come across without issue. In order for Bevy to be truly competitive as a game engine, I would argue that it's important to try to maximize hardware compatibility (within reason, of course).

Running the pbr example on OpenGL on my dedicated GPU at least renders fine but spams the following hundreds of times:

That looks like #13115 which is probably only tangentially related to this issue.

from bevy.