Windows Examples have misplaced transforms

[kfc35]

Bevy version and features

Current Main 1a21cbe

What went wrong

Pixel eagle started reporting weird example results for windows with respect to the position of meshes on the screen. This seems to be the first instance of it (April 19 2026): https://pixel-eagle.com/project/b25a040a-a980-4602-b90c-d480ab84076d/run/16656/compare/16646

(Ignore the meshes being dark since that is a wgpu separate problem that has since been resolved)

The previous run was only five hours prior, so it’s a narrow commit window that could be the culprit?

Additional information

In the pixel eagle link, it lists the commits it could be between, however none of them look like they would obviously break Windows transforms…

https://github.com/bevyengine/bevy/commits/main/?since=2026-04-18&until=2026-04-19

[alice-i-cecile]

This would be good to test locally too.

[kfc35]

If someone with windows dx-12 could bisect this within the given commit range, that would be a great help 🙏

[meepleek]

If someone with windows dx-12 could bisect this within the given commit range, that would be a great help 🙏

What are the steps to repro this locally? Just running one of the examples which show misalignment? I tried orthographic, but I'm not seeing any transform shift. Note that I'm not initially seeing anything and I had to resize the window to actually render anything and it's giving me weird artifacts at different window sizes.

Console output:

SystemInfo { os: "Windows 11 Education", kernel: "26200", cpu: "AMD Ryzen 9 5900X 12-Core Processor", core_count: "12", memory: "31.9 GiB" }
2026-05-04T18:02:07.852230Z INFO bevy_render::renderer: AdapterInfo { name: "Radeon RX 590 Series", vendor: 4098, device: 26591, device_type: DiscreteGpu, device_pci_bus_id: "0000:26:00.0", driver: "31.0.21924.61", driver_info: "", backend: Dx12, subgroup_min_size: 64, subgroup_max_size: 64, transient_saves_memory: false }
2026-05-04T18:02:08.560771Z INFO bevy_pbr::cluster: GPU clustering is supported on this device.
2026-05-04T18:02:08.561077Z INFO bevy_render::batching::gpu_preprocessing: GPU preprocessing is fully supported on this device.
2026-05-04T18:02:08.564321Z INFO bevy_winit::system: Creating new window orthographic (65v0)

I've also tried occlussion_culling which takes a while to render any meshes, but then looks fine.

I don't use Windows very often, I just dualbooted into it, pulled bevy & ran the examples, then also tried updating the gpu driver, but that made no difference.

[kfc35]

Sorry, I should’ve been more specific. The example runner uses release mode; it runs this specific command (if the example needs additional features, feel free to append):
cargo build --profile release --example orthographic --features bevy_ci_testing and then it runs the resulting .exe in target

Since creating this issue, I have a hunch about which commit it is. I created a draft revert for it here: #24122 . If you’re able to see weirdness on main with that command, I’d appreciate testing the potential solution from that PR if you’re up for it, since I’m unable to test it myself (beyond a pixel eagle run, which is currently executing!)