Bevy version and features
0.19.0
Relevant system information
SystemInfo { os: "Windows 11 Home", kernel: "26200", cpu: "", core_count: "8", memory: "15.6 GiB" }
AdapterInfo { name: "Qualcomm(R) Adreno(TM) X1-45 GPU", vendor: 20803, device: 925975600, device_type: IntegratedGpu, device_pci_bus_id: "", driver: "Qualcomm Technologies Inc. Adreno Vulkan Driver", driver_info: "Driver Build: b3549aaa68, I04672aa9d4, 1769138363\nDate: 01/23/2026\nCompiler Version: E031.50.36.00\nDriver Branch: bvt165\n", backend: Vulkan, subgroup_min_size: 64, subgroup_max_size: 128, transient_saves_memory: true }
What you did
Migrated my project from Bevy 0.18.3 to 0.19.0 and ran it on a Windows ARM64 system.
I also ran the 3d_scene example from the Bevy examples. In that example, the rendered objects were visible for only a single frame after startup and then disappeared completely.
What went wrong
Meshes flicker only on the Windows ARM64 build.
Initially, no meshes are visible. However, after interacting with the window (for example, hovering the cursor over the minimize, maximize, or close buttons, or scrolling in the terminal), the meshes begin to flicker. Gizmos are rendered correctly and remain visible.
In the 3d_scene example, the behavior is even more severe: the meshes are rendered for only one frame after startup and then disappear entirely.
Additional information
The same project runs correctly on Windows x86-64 with Bevy 0.19.0. The issue appears to be specific to the Windows ARM64 build.
Bevy version and features
0.19.0
Relevant system information
What you did
Migrated my project from Bevy 0.18.3 to 0.19.0 and ran it on a Windows ARM64 system.
I also ran the
3d_sceneexample from the Bevy examples. In that example, the rendered objects were visible for only a single frame after startup and then disappeared completely.What went wrong
Meshes flicker only on the Windows ARM64 build.
Initially, no meshes are visible. However, after interacting with the window (for example, hovering the cursor over the minimize, maximize, or close buttons, or scrolling in the terminal), the meshes begin to flicker. Gizmos are rendered correctly and remain visible.
In the
3d_sceneexample, the behavior is even more severe: the meshes are rendered for only one frame after startup and then disappear entirely.Additional information
The same project runs correctly on Windows x86-64 with Bevy 0.19.0. The issue appears to be specific to the Windows ARM64 build.