Basic 3D Scene Renders Unpredictably
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
## Bevy version
0.16
## Relevant system information
bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 11 Home", kernel: "26100", cpu: "", core_count: "10", memory: "15.6 GiB" }
bevy_render::renderer: AdapterInfo { name: "Qualcomm(R) Adreno(TM) X1-85 GPU", vendor: 20803, device: 909329200, device_type: IntegratedGpu, driver: "Qualcomm Technologies Inc. Adreno Vulkan Driver", driver_info: "Driver Build: , , 1698055923\nDate: 10/23/2023\nCompiler Version: E031.47.15.00\nDriver Branch: \n", backend: Vulkan }
bevy_render::batching::gpu_preprocessing: GPU preprocessing is fully supported on this device.
## What you did
Started a new Rust project. Added Bevy crate. Copied basic 3D scene example into `main.rs`. Ran project.
## What went wrong
The scene renders unpredictably. The scene is supposed to be a cube sitting on a circular plane with a shadow. However, each time the project is started I get a different result. Here a few possibilities that I was able to capture with less than 10 runs as I'm writing this:
1) Looks exactly as a expected
2) Only the cube appears but not the circular plane
4) The plane appears with the cube, but the shadow from the cube is missing
4) The plane appears with the shadow from the cube, but the cube itself is missing
To be clear, I'm not changing anything each time I run the project. I'm just closing the window, waiting a moment, and then executing `cargo run` again.
## Additional information
Minimal reproduction project: [bevy-test.zip](https://github.com/user-attachments/files/20202323/bevy-test.zip)
Contributor guide
Research direction
Start with the minimal reproduction project linked in the issue and the copied basic 3D scene in main.rs. Run it repeatedly on the reported Windows 11 and Adreno Vulkan setup, then investigate why the cube, plane, and shadow appear inconsistently; done means identifying and resolving the cause so the scene renders consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100