Wireframe on `2d_shapes` example is just an outline

[hukasu]

Bevy version

6ed3c32

[Optional] Relevant system information

2025-02-08T01:20:23.636141Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux (NixOS 24.11)", kernel: "6.6.69", cpu: "Intel(R) Core(TM) i7-14700KF", core_count: "20", memory: "31.2 GiB" }    
2025-02-08T01:20:23.872382Z  INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce RTX 4060 Ti", vendor: 4318, device: 10243, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "565.77", backend: Vulkan }

What you did

Ran 2d_shapes example and toggled wireframes on.

What went wrong

Wireframe was just an outline instead of showing the triangles.

Additional information

6ed3c32

83b725f

I bisected 3 times and got 3 different results, but it is known that wireframes are generally broken

@pcwalton
wireframes are known broken because of the fact that they break 1:1 entity:mesh
https://discord.com/channels/691052431525675048/743663924229963868/1337598834330832988

also #16896

[serialsss]

I have same issue. sometime wireframe shows, sometime just outline.
2025-02-10T07:59:24.738290Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 11 Pro", kernel: "22631", cpu: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz", core_count: "4", memory: "31.9 GiB" }
2025-02-10T07:59:25.050127Z INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce GTX 960", vendor: 4318, device: 5121, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "561.09", backend: Vulkan }
2025-02-10T07:59:25.229545Z INFO bevy_winit::system: Creating new window "App" (0v1#4294967296)

[hukasu]

@serialsss the work around for now is to remove MeshMaterial2d when adding Wireframe

[hukasu]

More broken on fb1e829, bisected to #17903

[hukasu]

@alice-i-cecile does wireframe count as gizmos?

[alice-i-cecile]

Hmm, technically not currently. Same sort of "debug visualization" though.

[JMS55]

Just to make this a little more visible: This is the same issue as #16896

[krunchington]

@IceSentry has indicated that there is an intended fix for this issue coming up