Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple examples don't work on 0.15 #17167

Open
chamaloriz opened this issue Jan 5, 2025 · 3 comments
Open

Multiple examples don't work on 0.15 #17167

chamaloriz opened this issue Jan 5, 2025 · 3 comments
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior C-Examples An addition or correction to our examples O-Web Specific to web (WASM) builds O-WebGL2 Specific to the WebGL2 render API P-Regression Functionality that used to work but no longer does. Add a test for this! S-Needs-Investigation This issue requires detective work to figure out what's going wrong

Comments

@chamaloriz
Copy link

chamaloriz commented Jan 5, 2025

Bevy version & Info

0.15.0


AdapterInfo { name: "Apple M1, or similar", vendor: 4203, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "WebGL 2.0", backend: Gl } on Apple M2 Max

What went wrong

Some of the examples on the website do not work, I only tested them via the website.

index out of bounds: the len is 16 but the index is 16
Device::create_render_pipeline error: Error matching ShaderStages(VERTEX) shader requirements against the pipeline log.target = "wgpu_core::device::global";
Buffer structure size 1024, added to one element of an unbound array, if it's the last field, ended up greater than the given `min_binding_size`, which is 16
Tex storage 2D multisample is not supported
The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page.

( should add a text on screen to 'press space to start' )

Device::create_render_pipeline error: In the provided shader, the type given for group 2 binding 100 has a size of 4. As the device does not support `DownlevelFlags::BUFFER_BINDINGS_NOT_16_BYTE_ALIGNED`, the type must have a size that is a multiple of 16 bytes. log.target = "wgpu_core::device::global";
wgpu error: Validation Error

Caused by:
  In Device::create_bind_group_layout, label = 'CustomMaterial'
    Binding 0 entry is invalid
      Downlevel flags DownlevelFlags(VERTEX_STORAGE) are required but not supported on the device.
wgpu error: Validation Error

Caused by:
  In RenderPass::end
    In a set_scissor_rect command
      Scissor Rect { x: 1920, y: 0, w: 640, h: 360 } is not contained in the render target (2336, 1314, 1)
wgpu error: Validation Error

Caused by:
  In Device::create_render_pipeline, label = 'ui_material_pipeline'
    In the provided shader, the type given for group 1 binding 1 has a size of 4. As the device does not support `DownlevelFlags::BUFFER_BINDINGS_NOT_16_BYTE_ALIGNED`, the type must have a size that is a multiple of 16 bytes.

Don't know if it's supposed to do that

@chamaloriz chamaloriz added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Jan 5, 2025
@BenjaminBrienen
Copy link
Contributor

Please add your AdapterInfo and system info. :)

@BenjaminBrienen BenjaminBrienen added C-Examples An addition or correction to our examples P-Regression Functionality that used to work but no longer does. Add a test for this! S-Needs-Investigation This issue requires detective work to figure out what's going wrong and removed S-Needs-Triage This issue needs to be labelled labels Jan 5, 2025
@mockersf
Copy link
Member

mockersf commented Jan 5, 2025

it's the examples on the website, so it's webgl2 and adaptater info/system info don't matter that much

@BenjaminBrienen
Copy link
Contributor

A lot of the errors seemed to be about driver or hardware limitations, but I don't have the best insight about that.

@alice-i-cecile alice-i-cecile added O-Web Specific to web (WASM) builds A-Rendering Drawing game state to the screen O-WebGL2 Specific to the WebGL2 render API labels Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior C-Examples An addition or correction to our examples O-Web Specific to web (WASM) builds O-WebGL2 Specific to the WebGL2 render API P-Regression Functionality that used to work but no longer does. Add a test for this! S-Needs-Investigation This issue requires detective work to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

4 participants