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

Failed to parse shader SPIR-V code Warning #860

Closed
MinerSebas opened this issue Nov 13, 2020 · 4 comments
Closed

Failed to parse shader SPIR-V code Warning #860

MinerSebas opened this issue Nov 13, 2020 · 4 comments
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior

Comments

@MinerSebas
Copy link
Contributor

Bevy version

43aac1a

Operating system & version

Windows 10 64bit

What you did

Ran the command cargo run --example ui

What you expected to happen

No warnings in the Console.

What actually happened

The console shows this:

Nov 13 13:59:10.247  WARN wgpu_core::device: Failed to parse shader SPIR-V code: UnsupportedBuiltIn(4)
Nov 13 13:59:10.248  WARN wgpu_core::device: Shader module will not be validated
Nov 13 13:59:10.445  WARN wgpu_core::device: Failed to parse shader SPIR-V code: UnsupportedBuiltIn(4)
Nov 13 13:59:10.445  WARN wgpu_core::device: Shader module will not be validated
Nov 13 13:59:10.612  WARN wgpu_core::device: Failed to parse shader SPIR-V code: UnsupportedBuiltIn(4)
Nov 13 13:59:10.613  WARN wgpu_core::device: Shader module will not be validated

Though, the Example itslef isn't broken.

Additional information
The warnings also appear for other Examples, but here the Examples themselves also work correctly.

Bisceting the Repo, these Warnings appeared after the Merge of #836

@karroffel
Copy link
Contributor

Thanks for the report! Nice that you did a bisect too, unfortunately that PR just adds logging, meaning that the underlying issue probably has been there for longer and was caused by another commit.

@karroffel karroffel added C-Bug An unexpected or incorrect behavior A-Rendering Drawing game state to the screen labels Nov 13, 2020
@cart
Copy link
Member

cart commented Nov 13, 2020

Yup its definitely a result of the new logging / these warnings have been silently there for awhile. I'm planning on trying to address the warnings (if possible) and if thats not possible (because its a result of wgpu's still-in-progress naga shader validation) I might suppress wgpu warnings until naga validation has full coverage.

@RedlineTriad
Copy link
Contributor

This doesn't seem to be an issue anymore:

❯ cargo run --example ui
    Finished dev [unoptimized + debuginfo] target(s) in 0.09s
     Running `target/debug/examples/ui`

bevy on  main [!] is 📦 v0.5.0 via 🦀 v1.51.0 took 2s 
❯ 

but I don't know which commit fixed it.

@alice-i-cecile
Copy link
Member

Closing as resolved <3

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
Projects
None yet
Development

No branches or pull requests

5 participants