Skip to content
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

Don't ignore unbatchable sorted items. #13144

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

pcwalton
Copy link
Contributor

In #12889, I mistakenly started dropping unbatchable sorted items on the floor instead of giving them solitary batches. This caused the objects in the shader_instancing demo to stop showing up. This patch fixes the issue by giving those items their own batches as expected.

Fixes #13130.

In bevyengine#12889, I mistakenly started dropping unbatchable sorted items on the
floor instead of giving them solitary batches. This caused the objects
in the `shader_instancing` demo to stop showing up. This patch fixes the
issue by giving those items their own batches as expected.

Fixes bevyengine#13130.
@mockersf mockersf added C-Bug An unexpected or incorrect behavior A-Rendering Drawing game state to the screen labels Apr 30, 2024
@mockersf mockersf added this to the 0.14 milestone Apr 30, 2024
@superdump superdump added this pull request to the merge queue Apr 30, 2024
Merged via the queue into bevyengine:main with commit f1db525 Apr 30, 2024
30 checks passed
@pcwalton pcwalton deleted the fix-shader-instancing branch April 30, 2024 15:38
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

example shader_instancing doesn't work after GPU frustum culling
3 participants