-
Notifications
You must be signed in to change notification settings - Fork 14
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
bevy 0.15 #86
Comments
Hey just curious, is this update going to support vello 0.3.0? |
I believe so. Velato and vello_svg (our two backends) were already upgraded, however it looks like vello 0.3 is using wgpu 0.22, while bevy 0.15 is using 0.23. I think that will cause some friction. |
Bevy 0.15 uses wgpu 0.23 (Cargo.toml) but it will still cause issues with vello 0.3 using wgpu 22.0. However the |
After some conversation in Zulip, it looks like there will indeed be a vello 0.4 launched on wgpu 0.23 soon(tm) that will unblock our issues. I will release a draft PR shortly to begin the work regardless. |
@simbleau I actually have a branch with the bevy 0.15 update, maybe it can help you as a starting point. The branch builds without errors (but only with the default features) and the examples that don't require the extra features build as well. Some examples run fine and some have glitches. Let me know if I can help with something! |
@elaye submit it as a PR please :) |
#86 --------- Co-authored-by: Elie Génard <[email protected]> Co-authored-by: Spencer C. Imbleau <[email protected]> Co-authored-by: Robert Brewitz <[email protected]>
Merged, closing. |
No description provided.
The text was updated successfully, but these errors were encountered: