Skip to content

Conversation

@tychedelia
Copy link
Member

@tychedelia tychedelia commented Feb 7, 2025

Objective

Things were breaking post-cs.

Solution

specialize_mesh_materials must run after collect_meshes_for_gpu_building. Therefore, its placement in the PrepareAssets set didn't make sense (also more generally). To fix, we put this class of system in PrepareResources QueueMeshes, although it potentially could use a more descriptive location. We may want to review the placement of check_views_need_specialization which is also currently in PrepareAssets.

@tychedelia tychedelia added C-Bug An unexpected or incorrect behavior A-Rendering Drawing game state to the screen S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels Feb 7, 2025
@tychedelia tychedelia changed the title Move specialize_* to PrepareResources. Move specialize_* to QueueMeshes. Feb 7, 2025
Copy link
Contributor

@HackerFoo HackerFoo left a comment

Choose a reason for hiding this comment

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

I tested these changes on my development build of Noumenal, and the glitches caused by #17567 are gone.

Copy link
Contributor

@pcwalton pcwalton left a comment

Choose a reason for hiding this comment

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

LGTM

@pcwalton pcwalton added S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it and removed S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels Feb 8, 2025
@superdump superdump added this pull request to the merge queue Feb 9, 2025
Merged via the queue into bevyengine:main with commit af6629c Feb 9, 2025
29 checks passed
mrchantey pushed a commit to mrchantey/bevy that referenced this pull request Feb 17, 2025
# Objective

Things were breaking post-cs.

## Solution

`specialize_mesh_materials` must run after
`collect_meshes_for_gpu_building`. Therefore, its placement in the
`PrepareAssets` set didn't make sense (also more generally). To fix, we
put this class of system in ~`PrepareResources`~ `QueueMeshes`, although
it potentially could use a more descriptive location. We may want to
review the placement of `check_views_need_specialization` which is also
currently in `PrepareAssets`.
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 S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants