Skip to content

Upgrade to bevy 0.17#27

Draft
MarijnS95 wants to merge 3 commits intofslabs:mainfrom
MarijnS95:bevy-0.13
Draft

Upgrade to bevy 0.17#27
MarijnS95 wants to merge 3 commits intofslabs:mainfrom
MarijnS95:bevy-0.13

Conversation

@MarijnS95
Copy link
Copy Markdown

No description provided.

Comment on lines 35 to -38
opaque_phase.add(Opaque3d {
// TODO: https://github.com/bevyengine/bevy/pull/11671/files
asset_id: AssetId::invalid(),
// asset_id: CUBE_INDICES_HANDLE.into(),
// distance: inverse_view_row_2.dot(entry.position.extend(1.0)),
pipeline,
entity,
distance: inverse_view_row_2.dot(entry.position.extend(1.0)),
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Elabajaba since you wrote bevyengine/bevy#11671, how is an app like this that uses a simple index buffer and "generates"/computes vertex positions "on the fly" in the vertex shader supposed to provide an AssetId<Mesh>? Looks like we can't get the original sorting based on distance.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure tbh. I didn't realize anyone was doing vertex pulling with bevy's standard opaque3d pipeline.

I opened a PR on your fork (MarijnS95#1) that re-implements bevy's old Opaque3d pass as a custom pass to get this working, but I'm not sure if it's the best solution.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Elabajaba that sounds unfortunate.

Thanks for the ping. Looks like creating forks via the gh CLI doesn't automatically set myself as watching my own repo, so I didn't receive any other notification for you opening a PR there.

I'll take a closer look later but already see some drive-by fixes that you ought to better submit separately :)

) in cuboids.iter()
{
for (entity, cuboids, transform, materials_id, maybe_visibility) in &cuboids {
let instance_buffer_needs_update = cuboids.is_added() || cuboids.is_changed();
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Following the docs there's an is_added() etc now, as I no longer seem to be able to use the Added/Changed traits to get a boolean value out of the query. Something about ReadOnlyQueryData not being implemented, and I'm not familiar enough with bevy internals to debug that further.

@fslabs-bot
Copy link
Copy Markdown

fslabs-bot Bot commented Feb 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@fslabs-bot fslabs-bot Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 5, 2025
@MarijnS95 MarijnS95 changed the title Upgrade to bevy 0.13 Upgrade to bevy 0.17 Oct 30, 2025
@fslabs-bot fslabs-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 30, 2025
@fslabs-bot fslabs-bot Bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 30, 2025
hlorus pushed a commit to hlorus/vdb-rs that referenced this pull request Nov 20, 2025
- Updated dependency to use PR Traverse-Research#27 (commit 146889a)
- Restored examples to use real bevy-aabb-instancing instead of placeholders
- Added glam version conversion (0.24 to 0.30) for compatibility
- Both examples now compile and are ready to use

The PR is work-in-progress but functional for development.
Track progress at: fslabs/bevy_aabb_instancing#27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants