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

Sprites sometimes not rendering when displayed along Mesh2d/MeshMaterial2d. #17318

Open
jingchan opened this issue Jan 12, 2025 · 0 comments
Open
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong

Comments

@jingchan
Copy link

Bevy version

0.15.1

[Optional] Relevant system information

AdapterInfo { name: "Apple M3 Pro", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }

What you did

Two entities: Player and Enemy.

  1. Both render fine with Sprite components (using TextureAtlases).
  2. On the Enemy entity, add Mesh2d and MeshMaterial2d with a Circle and ColorMaterial, respectively.
  3. Observe that Player's Sprite no longer renders when Enemy's Mesh2d is displayed on the screen.
  4. Once the camera is moved so that the Enemy is no longer visible, the Player's Sprite does begin to render. It disappears again if moving the camera back to the previous position, exactly as the Enemy comes into frame.

What went wrong

Expect to see Sprite, but don't.

@jingchan jingchan added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Jan 12, 2025
@BenjaminBrienen BenjaminBrienen added A-Rendering Drawing game state to the screen S-Needs-Investigation This issue requires detective work to figure out what's going wrong and removed S-Needs-Triage This issue needs to be labelled labels Jan 12, 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 S-Needs-Investigation This issue requires detective work to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

2 participants