Solari6 various improvements by jasmine-nominal · Pull Request #40 · JMS55/bevy

jasmine-nominal · 2025-10-31T13:59:32Z

No description provided.

# Objective Currently the docs for [`SpawnScene`](https://docs.rs/bevy/latest/bevy/app/struct.SpawnScene.html) link to the [`Main`](https://docs.rs/bevy/latest/bevy/prelude/struct.Main.html) schedule, but those docs don't mention when it runs. ## Solution Updates docs to include this information, based on the schedule ordering defined here: https://github.com/bevyengine/bevy/blob/78d940cbfe177e3585fe19145e73c76172f4085e/crates/bevy_app/src/main_schedule.rs#L222-L224

# Objective * Make DespawnOnExit more discoverable. * Fix broken link text - the parenthetical before it seems to mess it up. ## Solution * Link directly to DespawnOnExit from the module documentation instead of just the containing module. ## Testing None. Somebody should build the docs to make sure the links actually work (I'm 99% sure they do) and that the `\` added actually fixes the link on line 32 (I'm only 80% sure it does) ## Further Questions I'm wondering if this functionality should be listed in the bulleted list that precedes this paragraph. --------- Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>

) # Objective - Fixes bevyengine#20803 - See issue for motivations on this change ## Solution - Use ureq's `platform-verifier` feature and enable it in the agent config. I've gone the simple route and made this non-configurable, for now at least. The downside of this change is that you can longer use webpki-roots but if bevy only supports one certificate verification method then I think platform-verifier is the more sensible option. ## Testing - Tested the web_asset example on Windows and macOS

# Objective The docs state that `Entity::from_row` creates an entity with a generation of `1`, which was the case previously. With `Entity` internals being reworked in `0.17` however, this is no longer the case, as the generation used is now `EntityGeneration::FIRST`, currently equivalent to `0`. ## Solution This PR changes the docs to state an "unspecified" generation to allow further changes to implementation without needing another rewrite, as the docs rather consistently refer to `Entity`, `EntityRow`, and `EntityGeneration` as being opaque identifiers.

# Objective - Fixes bevyengine#21413 ## Solution - make bevy_input_focus dep on bevy_picking optional ## Testing - ci

# Objective - See rust-lang/rust#145457, we want to remove unconditional `[T; 0]: Default` impl. That would be a breaking change breaking `bevy_ecs` and (a test of) `bevy_camera`. ## Solution - Replace `<[T; 0]>::default()` calls with `[]` ## Testing - It compiles, the `<[T; 0]>::default()` is equivalent to `[]`, no additional testing required

# Objective close bevyengine#21334 ## Solution update linux dependencies in docs

Some small work on virtual geometry. Some other improvements we should do in the future for the builder code: * meshopt_computeSphereBounds instead of merge_spheres * Permissive simplification * Faster vertex locking, copying zeux/meshoptimizer#961 * Try out meshopt's clusterizer/partitioner instead of using metis --------- Co-authored-by: Jasmine Schweitzer <jasmine.schweitzer@nominal.io>

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4 to 6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/download-artifact/releases">actions/download-artifact's releases</a>.</em></p> <blockquote> <h2>v6.0.0</h2> <h2>What's Changed</h2> <p><strong>BREAKING CHANGE:</strong> this update supports Node <code>v24.x</code>. This is not a breaking change per-se but we're treating it as such.</p> <ul> <li>Update README for download-artifact v5 changes by <a href="https://github.com/yacaovsnc"><code>@yacaovsnc</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/417">actions/download-artifact#417</a></li> <li>Update README with artifact extraction details by <a href="https://github.com/yacaovsnc"><code>@yacaovsnc</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/424">actions/download-artifact#424</a></li> <li>Readme: spell out the first use of GHES by <a href="https://github.com/danwkennedy"><code>@danwkennedy</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/431">actions/download-artifact#431</a></li> <li>Bump <code>@actions/artifact</code> to <code>v4.0.0</code></li> <li>Prepare <code>v6.0.0</code> by <a href="https://github.com/danwkennedy"><code>@danwkennedy</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/438">actions/download-artifact#438</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/danwkennedy"><code>@danwkennedy</code></a> made their first contribution in <a href="https://redirect.github.com/actions/download-artifact/pull/431">actions/download-artifact#431</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/actions/download-artifact/compare/v5...v6.0.0">https://github.com/actions/download-artifact/compare/v5...v6.0.0</a></p> <h2>v5.0.0</h2> <h2>What's Changed</h2> <ul> <li>Update README.md by <a href="https://github.com/nebuk89"><code>@nebuk89</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/407">actions/download-artifact#407</a></li> <li>BREAKING fix: inconsistent path behavior for single artifact downloads by ID by <a href="https://github.com/GrantBirki"><code>@GrantBirki</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/416">actions/download-artifact#416</a></li> </ul> <h2>v5.0.0</h2> <h3>🚨 Breaking Change</h3> <p>This release fixes an inconsistency in path behavior for single artifact downloads by ID. <strong>If you're downloading single artifacts by ID, the output path may change.</strong></p> <h4>What Changed</h4> <p>Previously, <strong>single artifact downloads</strong> behaved differently depending on how you specified the artifact:</p> <ul> <li><strong>By name</strong>: <code>name: my-artifact</code> → extracted to <code>path/</code> (direct)</li> <li><strong>By ID</strong>: <code>artifact-ids: 12345</code> → extracted to <code>path/my-artifact/</code> (nested)</li> </ul> <p>Now both methods are consistent:</p> <ul> <li><strong>By name</strong>: <code>name: my-artifact</code> → extracted to <code>path/</code> (unchanged)</li> <li><strong>By ID</strong>: <code>artifact-ids: 12345</code> → extracted to <code>path/</code> (fixed - now direct)</li> </ul> <h4>Migration Guide</h4> <h5>✅ No Action Needed If:</h5> <ul> <li>You download artifacts by <strong>name</strong></li> <li>You download <strong>multiple</strong> artifacts by ID</li> <li>You already use <code>merge-multiple: true</code> as a workaround</li> </ul> <h5>⚠️ Action Required If:</h5> <p>You download <strong>single artifacts by ID</strong> and your workflows expect the nested directory structure.</p>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/download-artifact/commit/018cc2cf5baa6db3ef3c5f8a56943fffe632ef53"><code>018cc2c</code></a> Merge pull request <a href="https://redirect.github.com/actions/download-artifact/issues/438">#438</a> from actions/danwkennedy/prepare-6.0.0</li> <li><a href="https://github.com/actions/download-artifact/commit/815651c680ffe1c95719d0ed08aba1a2f9d5c177"><code>815651c</code></a> Revert "Remove <code>github.dep.yml</code>"</li> <li><a href="https://github.com/actions/download-artifact/commit/bb3a066a8babc8ed7b3e4218896c548fe34e7115"><code>bb3a066</code></a> Remove <code>github.dep.yml</code></li> <li><a href="https://github.com/actions/download-artifact/commit/fa1ce46bbd11b8387539af12741055a76dfdf804"><code>fa1ce46</code></a> Prepare <code>v6.0.0</code></li> <li><a href="https://github.com/actions/download-artifact/commit/4a24838f3d5601fd639834081e118c2995d51e1c"><code>4a24838</code></a> Merge pull request <a href="https://redirect.github.com/actions/download-artifact/issues/431">#431</a> from danwkennedy/patch-1</li> <li><a href="https://github.com/actions/download-artifact/commit/5e3251c4ff5a32e4cf8dd4adaee0e692365237ae"><code>5e3251c</code></a> Readme: spell out the first use of GHES</li> <li><a href="https://github.com/actions/download-artifact/commit/abefc31eafcfbdf6c5336127c1346fdae79ff41c"><code>abefc31</code></a> Merge pull request <a href="https://redirect.github.com/actions/download-artifact/issues/424">#424</a> from actions/yacaovsnc/update_readme</li> <li><a href="https://github.com/actions/download-artifact/commit/ac43a6070aa7db8a41e756e7a2846221edca7027"><code>ac43a60</code></a> Update README with artifact extraction details</li> <li><a href="https://github.com/actions/download-artifact/commit/de96f4613b77ec03b5cf633e7c350c32bd3c5660"><code>de96f46</code></a> Merge pull request <a href="https://redirect.github.com/actions/download-artifact/issues/417">#417</a> from actions/yacaovsnc/update_readme</li> <li><a href="https://github.com/actions/download-artifact/commit/7993cb44e9052f2f08f9b828ae5ef3ecca7d2ac7"><code>7993cb4</code></a> Remove migration guide for artifact download changes</li> <li>Additional commits viewable in <a href="https://github.com/actions/download-artifact/compare/v4...v6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/download-artifact&package-manager=github_actions&previous-version=4&new-version=6)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

# Objective - bevyengine#21664 broke CI. Failures wasn't triggered by this PR as it's the CI that runs from the main branch ## Solution - download-artifact v5 changed how artefacts are handled. we met a case not documented in their breaking change

…engine#21647) # Objective In bevyengine#21598 and the related Discord discussion, it was pointed out that the `async_compute` example promotes an inefficient and potentially error-prone pattern: `future::block_on(poll_once)`. It is now recommended to use `bevy::tasks::futures::check_ready` instead, which is much cheaper and avoids blocking the main thread while waiting on the future. Another valid approach is to pass a channel into the async tasks and detach them, letting the channel handle task readiness. This PR implements both suggestions. ## Solution * **Updated `async_compute` example** Replaced the use of `future::block_on(poll_once)` with the recommended `check_ready`. The change is minimal and limited to the directly affected lines. * **Added new example: `async_channel_pattern`** Demonstrates how to spawn async tasks using a channel-based communication pattern. * Each task is executed on a separate thread via `AsyncComputeTaskPool`. * Results (cube positions) are sent back through a `CubeChannel` once completed. * Tasks are detached to run fully asynchronously, ensuring the main thread remains unblocked. * A rotating light in the scene visually indicates that the frame loop remains responsive. I am relatively new to both Bevy and async Rust, and I genuinely appreciate any feedback or suggestions to improve these examples — especially regarding idiomatic async patterns and best practices for Bevy task management. Fixes bevyengine#21598 --------- Co-authored-by: syszery <syszery@users.noreply.github.com> Co-authored-by: François Mockers <francois.mockers@vleue.com>

# Objective This PR is to add SSAO support on WebGPU. ## Solution Add r16float detect and fallback to r32float if not supported. FYI the initial ssao PR [here](bevyengine#7402). ## Testing - Did you test these changes? If so, how? Yes, here is the command to test the ssao example `RUSTFLAGS="--cfg getrandom_backend=\"wasm_js\"" cargo run --example ssao --target wasm32-unknown-unknown --features webgpu` and then http://localhost:1334, make sure it supports [WebGPU](https://caniuse.com/webgpu) - Are there any parts that need more testing? N/A - How can other people (reviewers) test your changes? Is there anything specific they need to know? 1. For the R32Float fallback, only the 1st commit is needed. However, I ran into some strange flickering issue on Chrome (and Chrome canary too), so I added a "detect_r16float_support" flag and a temp fix in the 2nd and 3rd commit, which are intended to be reverted when merging. 2. with the 1st commit, Safari works fine, but Chrome has the flickering, and I fixed it by partially reverting a shader change from bevyengine#20313, which is very strange. It is probably caused by some shader optimization issue in Chrome, and I have no clue why, as the change is just moving the calculation to a different function. Here is the flickering on Mac Chrome(140.0.7339.133 (Official Build) (arm64)) <img width="353" height="327" alt="chrome_ssao" src="https://github.com/user-attachments/assets/0666673f-508e-4b57-a152-19327ffdb6f3" /> - If relevant, what platforms did you test these changes on, and are there any important ones you can't test? Tested on native(mac) and WebGPU. To test on native, set "detect_r16float_support" to false to force R32Float. I couldn't make the WebGPU ssao example running on Windows 11 Chrome or Firefox, there is some error in 'taa_pipeline' . ---

# Objective Remove the `line_height` field from `TextFont`. Line height is a property of the text layout, not the font. Part of the changes for bevyengine#21175 ## Solution Remove the `line_height` field from `TextFont`. Make `LineHeight` into a component. Update the text access API and text pipeline.

# Objective - This commit refactors the `from_viewport_and_override` function to improve readability and safety. ## Solution - Replaces the initial `cloned()` and subsequent `if/else` logic with a clearer `if let` structure. - Removes the need for `unwrap()` by handling both `Some` and `None` cases ## Testing - I don't know how to make sure there is no probelm, but I run some examples and I don't see the errors.

# Objective - This PR refactors the Frustum struct to improve code readability and maintainability by replacing magic numbers with named constants and unrolling a loop for clarity. ## Testing - I ran the command 'cargo test --package bevy_camera --lib -- primitives::tests --show-output' and all the test are passed. ---

# Objective For bevyengine#17647, we want to create a `QueryData` that can follow a relation and query data from an entity's parent. If the parent does not have the queried data, the child entity should be skipped in the query. However, there is no way to tell from the child's archetype whether the parent will match! So, we need to support *non-archetypal* `QueryData`, just as we support non-archetypal `QueryFilter`s for `Added` and `Changed`. That is, if `Query<Parent<&T>>` yields `&T`, and we do: ```rust let parent1 = world.spawn(T).id(); let child1 = world.spawn(ChildOf(parent1)); let parent2 = world.spawn(()).id(); let child2 = world.spawn(ChildOf(parent2)); let query = world.query::<Parent<&T>>(); ``` then `query` must yield a row for `child1` but not for `child2`, even though they have the same archetype. ## Solution Change `QueryData::fetch` to return `Option` so that entities can be filtered during fetching by returning `None`. To support `ExactSizeIterator`, introduce an `ArchetypeQueryData` trait and an `QueryData::IS_ARCHETYPAL` associated constant, similar to `ArchetypeFilter` and `QueryFilter::IS_ARCHETYPAL`. Implement this trait on existing `QueryData` types. Modify `ExactSizeIterator` implementations to require `D: ArchetypeQueryData`, and the `size_hint()` methods to return a minimum size of `0` if `!D::IS_ARCHETYPAL`. ## Alternatives We could do nothing here, and have `Query<Parent<&T>>` yield `Option<&T>`. That makes the API less convenient, though. Note that if one *wants* to query for `Option`, they can use either `Query<Option<Parent<&T>>` or `Query<Parent<Option<&T>>`, depending on whether they want to include entities with no parent. Another option is to re-use the `ArchetypeFilter` trait instead of introducing a new one. There are no places where we want to abstract over both, however, and it would require writing bounds like `D: QueryData + ArchetypeFilter, F: QueryFilter + ArchetypeFilter` instead of simply `D: ArchetypeQueryData, F: ArchetypeFilter`. --------- Co-authored-by: Periwink <charlesbour@gmail.com>

Depends on bevyengine#20838 # Objective There's some redundant sampler bindings in the atmosphere code ## Solution Remove them ## Testing Ran the example

# Objective - Splitting out the non-BSN parts of the work on popup menus. ## Solution - Added Popover and Menu components. ## Testing - Manual testing using example. ## Showcase <img width="311" height="261" alt="popup" src="https://github.com/user-attachments/assets/ab9e8959-65bc-45d3-aa36-9d56cc09ea9d" /> --------- Co-authored-by: Viktor Gustavsson <villor94@gmail.com>

…evyengine#21643) # Objective - Fixes bevyengine#10903 ## Solution - Stop using `Path::join` for joining asset paths and instead use `AssetPath::resolve_embed`. ## Testing - Added 2 tests!

# Objective Just a tiny fix of `log_layers` example path in documentation comments. ## Solution The comments are corrected. ## Testing No needed

# Objective Allows users to override `TextColor` and use a custom color for underline and strikethrough text decorations. ## Solution New components `UnderlineColor` and `StrikethroughColor`. Add them to a text entity with `Underline` or `Strikethrough`, respectively, to use a custom color for the lines. # This could just be an optional color field on `Underline` or `Strikethrough`, that would be fine. I spent a while going back and fourth about it. The main reasons why I went with a separate component: * The same color is almost always used for both text and its decorations. Overriding `TextColor` is going to be rare. * Once we have some sort of global or propagated text style support, underline and strikethrough colors probably won't be set per entity. The single component approach has some advantages too. Discoverability, obviously. Also compare: ```rust ( Text::new("Hello"), Underline, UnderlineColor(RED.into()) ) ``` with ```rust ( Text::new("Hello"), Underline::color(RED), ) ``` which seems clearly nicer. If it weren't for the planned non-entity-local text styling support, I'd lean more towards the single component approach. ## Testing Added a few color overrides to this example: ``` cargo run --example strikethrough ``` ## Showcase <img width="1924" height="1127" alt="strike-under-color" src="https://github.com/user-attachments/assets/83664f95-0926-4ccb-81e4-a3059cd2ccf3" />

…bevyengine#21685) # Objective Tests should be more resilient to entities added on `World` creation. This is necessary for resources-as-components to work without relying on `DefaultQueryFilters`. ## Solution I've added an empty entity during `World::bootstrap()` and ran the test suite (and CI). I've gone and fixed every test, except for the ones where it's not possible / doesn't make sense. Both `iter_entities` and `iter_entities_mut` and their tests have been removed as they were deprecated in 0.17.

# Objective - Computing the ndc from a viewport coordinates is already done in a few places. - It's can be useful for users, not just internally. ## Solution - Extract it to a function ## Testing - I'm using it in a currently unfinished PR for gpu picking and things worked as expected - I also tested 3d_viewport_to_world and 2d_viewport_to_world --------- Co-authored-by: atlv <email@atlasdostal.com>

…_2d_as_array` (bevyengine#21628) # Objective If you want to use a `TilemapChunk` (or more generally use a `texture2DArray` in a shader), you have to implement a mechanism that waits for your texture to load, then calls `Image::reinterpret_stacked_2d_as_array`. ## Solution Have the loader do it instead. Closes bevyengine#20799, which does very similar things and should be remade if more functionality is needed. ## Testing - Ran the updated examples --- ## Showcase ```rs let array_texture = asset_server.load_with_settings( "textures/array_texture.png", |settings: &mut ImageLoaderSettings| { settings.array_layout = Some(ImageArrayLayout::RowCount(4)); }, ); ```

# Objective Ended up with two release notes for strikethrough somehow after the merges or whatever. ## Solution Rename one, delete the other.

…evyengine#21689) # Objective Rename the example, fix a typo in its ("it's") comments.

# Objective Follow up to the underline and strikethrough PRs: * Replace the quintuples stored in `TextLayoutInfo::section_geometry` with a struct with named fields. * Rename `TextLayoutInfo::section_geometry` because "section" in our terminology implies a one-to-one correspondence with text entities. * Add some basic helpers to construct the underline and strikethrough lines. * Seperate the thickness values for underline and strikethrough. This is needed for an API that allows users to set custom thicknesses. ## Solution * New struct `RunGeometry`. `RunGeometry` holds the bounds and decoration geometry for each text run (a contiguous sequence of glyphs on a line that share text attributes). It has helper methods for placing underline and strikethrough. * Rename the `section_geometry` field to `run_geometry` and make it a `Vec<RunGeometry>` * `RunGeometry` has seperate `underline_thickness` and `strikethrough_thickness` values.

# Objective Some macros were handling Idents and indexes as seperate things, we can use syn::Member to make this more readable and nicer. revive of bevyengine#18199

…yengine#16396) # Objective Improve the performance of some dynamic queries with `FilteredEntity(Ref|Mut)` by allowing dense iteration in more cases, and remove a call to the sort-of deprecated `Access::component_reads_and_writes()` method. `QueryBuilder` currently requires sparse iteration if any sparse set components may be read. We do need sparse iteration if sparse set components are used in the filters, but `FilteredEntityRef` can still perform dense iteration when reading optional components or when reading all components. Note that the optional case is different from `Option`, which performs sparse iteration when the inner query is sparse so that it can cache whether the inner query matches for an entire archetype. ## Solution Change `FilteredEntity(Ref|Mut)` to have `IS_DENSE = true`. It used to require sparse iteration in order to filter the `Access` for each archetype, but bevyengine#15207 changed it to copy the entire access. Change `QueryBuilder::is_dense()` to check `D::IS_DENSE && F::IS_DENSE` instead of looking at the component reads and writes. `QueryBuilder::is_dense()` still checks the *filters*, so `builder.data::<&Sparse>()` will still cause sparse iteration, but `builder.data::<Option<&Sparse>>()` no longer will. I believe this is sound, even in the presence of query transmutes. The only `WorldQuery` implementations that rely on a sparse query being sparse for soundness are `&`, `&mut`, `Ref`, and `Mut`, but they can only be transmuted to if the component is in the `required` set. If a dynamic query has the component in the `required` set, then it appears in the filters and the query will use sparse iteration. Note that `Option` and `Has` will misbehave and report `None` and `false` for all entities if they do a dense query while wrapping a sparse component, but they won't cause UB. And it's already possible to hit that case by transmuting from `Query<EntityMut>` to `Query<Option<&Sparse>>`.

# Objective Have the layout of the tile chunk map the world axis. ## Solution Invert the calculated y index in the shader and transform calculation. ## Testing Ran the example and saw 0,0 move to the bottom left instead of the top left. ## Migration People manually calculating the tile index will have to invert the chunk relative y index from the current implementation. For example, with a chunk size of (16, 16) today: (5, 6) in world coords => (5, 9) in chunk coords Changes to: (5, 6) in world coords => (5, 6) in chunk coords --------- Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com> Co-authored-by: Martín Maita <47983254+mnmaita@users.noreply.github.com>

# Objective Text2d underline shadow is being drawn using the strikethrough position and size values. Draw it with the correct geometry. ## Solution Use the underline values.

…ources. (bevyengine#21673) # Objective - Trying to rewrite asset processing to be dynamic is hard, especially since we don't have tests verifying all the situations asset processing is supposed to be able to handle! ## Solution - Add a couple more tests! One to check that processing multiple sources works, and another to check that sending asset events triggers processing (including processing of dependent processing). ## Testing - ;)

…vements

andrewhickman and others added 30 commits October 25, 2025 02:25

make bevy_input_focus dep on bevy_picking optional (bevyengine#21659)

5530e8f

# Objective - Fixes bevyengine#21413 ## Solution - make bevy_input_focus dep on bevy_picking optional ## Testing - ci

update linux dependencies (bevyengine#21651)

40767f4

# Objective close bevyengine#21334 ## Solution update linux dependencies in docs

Atmosphere bindings cleanup (bevyengine#21625)

0fa0b0e

Depends on bevyengine#20838 # Objective There's some redundant sampler bindings in the atmosphere code ## Solution Remove them ## Testing Ran the example

Fix GLTF files being broken when loaded from custom asset sources. (b…

f6b34bd

…evyengine#21643) # Objective - Fixes bevyengine#10903 ## Solution - Stop using `Path::join` for joining asset paths and instead use `AssetPath::resolve_embed`. ## Testing - Added 2 tests!

Fix example file paths in doc comments (bevyengine#21674)

a5b9c41

# Objective Just a tiny fix of `log_layers` example path in documentation comments. ## Solution The comments are corrected. ## Testing No needed

Strikethrough release note clean up (bevyengine#21688)

0067171

# Objective Ended up with two release notes for strikethrough somehow after the merges or whatever. ## Solution Rename one, delete the other.

Rename the strikethrough example to strikethrough_and_underline (b…

8d1bf6e

…evyengine#21689) # Objective Rename the example, fix a typo in its ("it's") comments.

Cleaner macros utilizing syn::Member v2 (bevyengine#21678)

5a6a06a

# Objective Some macros were handling Idents and indexes as seperate things, we can use syn::Member to make this more readable and nicer. revive of bevyengine#18199

chescock and others added 7 commits October 30, 2025 02:53

Text2d underline shadows fix (bevyengine#21695)

346c47c

# Objective Text2d underline shadow is being drawn using the strikethrough position and size values. Draw it with the correct geometry. ## Solution Use the underline values.

Merge remote-tracking branch 'origin/main' into solari6-various-impro…

4e8ab80

…vements

Extract permute_pixel

49c9f8f

Fix roughness cutoff

191b794

JMS55 merged commit 55d0d59 into JMS55:solari6-various Oct 31, 2025
26 of 29 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Solari6 various improvements#40

Solari6 various improvements#40
JMS55 merged 37 commits intoJMS55:solari6-variousfrom
jasmine-nominal:solari6-various-improvements

jasmine-nominal commented Oct 31, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

Conversation

jasmine-nominal commented Oct 31, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants