Strange behavior on PinePhone Pro

[Shatur]

Bevy version

v0.13.1

[Optional] Relevant system information

Adapter Gl AdapterInfo { name: "Mali-T860 (Panfrost)", vendor: 65541, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Gl }

Phone specs. More detailed CPU specs.

What you did

I trying to run examples from the Bevy repo.

What went wrong

If I try to any example like this:

cargo run --example sprite --features=wayland

I have the following error:

Handling wgpu errors as fatal by default    
thread 'main' panicked at /home/shatur/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.19.3/src/backend/wgpu_core.rs:3006:5:
wgpu error: Validation Error

Caused by:
    In Device::create_bind_group_layout
      note: label = `mesh2d_layout`
    Binding 0 entry is invalid
    Downlevel flags DownlevelFlags(VERTEX_STORAGE) are required but not supported on the device.
This is not an invalid use of WebGPU: the underlying API or device does not support enough features to be a fully compliant implementation. A subset of the features can still be used. If you are running this program on native and not in a browser and wish to work around this issue, call Adapter::downlevel_properties or Device::downlevel_properties to get a listing of the features the current platform supports.

In order to fix it I set WGPU_SETTINGS_PRIO=webgl2 environment variable.

Now all 2D examples work, I can run sprite or breakout examples without issues.

But when I try to run any 3D example like this:

WGPU_SETTINGS_PRIO=webgl2 cargo run --example 3d_scene --features=wayland

It crashes with the following output: log.txt

Additional information

My setup:

[JMS55]

Hard to tell from the lack of info in the logs, but if I had to guess, your GPU crashed.

[Shatur]

How can I provide more information about the issue?

[rmader]

This part of the log:

Caused by:
    In Device::create_render_pipeline
      note: label = `pbr_opaque_mesh_pipeline`
    Internal error in ShaderStages(FRAGMENT) shader: 0:2(12): error: extension `GL_EXT_texture_cube_map_array' unsupported in fragment shader

looks weird - it's a GLES 3.2 / GL 4.0 feature, not supported by Panfrost yet (neither GL_OES_texture_cube_map_array nor GL_ARB_texture_cube_map_array) and isn't required for webgl2. AFAIK webgl2 should even work with GLES 3.0.

[Shatur]

Interesting... @superdump maybe you have an idea why it happens?

[superdump]

I think we need to expose: https://docs.rs/wgpu/latest/wgpu/struct.DownlevelCapabilities.html and use it for various parts of feature detection logic.

• For the vertex storage problem - we use storage buffers based on the maximum storage buffer bindings allowed per shade stage: https://github.com/bevyengine/bevy/blob/017ffc5a7ba00e2734a68c03459ba718bd4aa462/crates/bevy_render/src/render_resource/gpu_array_buffer.rs#L41 but it seems we also need to consider whether storage buffers are allowed in the vertex stage: https://docs.rs/wgpu/latest/wgpu/struct.DownlevelFlags.html#associatedconstant.VERTEX_STORAGE
• For the cube map array problem - we know that on proper WebGL2, we don't support cube map array textures, but I guess detection of that is slipping through the cracks. We need to disable cube map array textures like this https://github.com/bevyengine/bevy/blob/017ffc5a7ba00e2734a68c03459ba718bd4aa462/crates/bevy_render/src/render_resource/pipeline_cache.rs#L285 based on https://docs.rs/wgpu/latest/wgpu/struct.DownlevelFlags.html#associatedconstant.CUBE_ARRAY_TEXTURES