-
Notifications
You must be signed in to change notification settings - Fork 3
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
Validation panic when loading a shader that accesses lighting data #13
Comments
In theory it would also be possible to remedy this on the bevy side, but that doesn't seem appropriate given that their lighting system is read-only as per GPU usage idioms. Patching in a read-write option for the sake of making a third-party crate's workaround viable isn't a great reason to do it. |
This is in the process of being fixed upstream (EmbarkStudios/rust-gpu#1009) and has been tested as working with |
Sorry, that PR is not for the |
As
rust-gpu
doesn't support access specifiers for storage buffers, bevy panics with the following error when trying to load a shader that accesses its lighting data:This can be worked around by forcibly disabling storage buffers via
WgpuSettings
(which is default behaviour in the currentBevyRustGpuPlugin
), but precludes their usage entirely, which is not ideal given that read / write storage buffers are viable.Upstream tracking issue: rust-gpu/#689
The text was updated successfully, but these errors were encountered: