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

Bevy 0.15 no longer respects Material2d::depth_bias #17355

Open
SludgePhD opened this issue Jan 14, 2025 · 1 comment
Open

Bevy 0.15 no longer respects Material2d::depth_bias #17355

SludgePhD opened this issue Jan 14, 2025 · 1 comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior D-Straightforward Simple bug fixes and API improvements, docs, test and examples P-Regression Functionality that used to work but no longer does. Add a test for this! S-Ready-For-Implementation This issue is ready for an implementation PR. Go for it!

Comments

@SludgePhD
Copy link
Contributor

Bevy version

0.15

What you did

Enable wireframe on a 2D object with a ColorMaterial.

What went wrong

The wireframe renders behind the object instead of in front of it, and only its outline is visible. This happens despite the wireframe material setting a depth_bias that should make it render in front of the other material:

fn depth_bias(&self) -> f32 {
1.0
}

This issue seems similar to #14169, the 3D version of this problem.

This worked properly in bevy 0.14.

@SludgePhD SludgePhD added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Jan 14, 2025
@IceSentry
Copy link
Contributor

I think the solution is this PR or something like this #16511

@BenjaminBrienen BenjaminBrienen added A-Rendering Drawing game state to the screen P-Regression Functionality that used to work but no longer does. Add a test for this! S-Ready-For-Implementation This issue is ready for an implementation PR. Go for it! D-Straightforward Simple bug fixes and API improvements, docs, test and examples and removed S-Needs-Triage This issue needs to be labelled labels Jan 14, 2025
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 D-Straightforward Simple bug fixes and API improvements, docs, test and examples P-Regression Functionality that used to work but no longer does. Add a test for this! S-Ready-For-Implementation This issue is ready for an implementation PR. Go for it!
Projects
None yet
Development

No branches or pull requests

3 participants