Warnings from the winit platform impl
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
## Bevy version
0.12
## \[Optional\] Relevant system information
`SystemInfo { os: "Windows 10 Pro", kernel: "19045", cpu: "AMD Ryzen 9 5950X 16-Core Processor", core_count: "16", memory: "31.9 GiB" }`
## What you did
Open any software "overlay" while a [rendering] bevy app is running. If you have an NVIDIA card, the "GeForce Experience" overlay reproduces this reliably.
## What went wrong
Warnings emitted from the winit platform implementation.
## Additional information
Example:
When opening the overlay
```
2023-11-26T03:10:04.551497Z WARN winit::platform_impl::platform::event_loop::runner: NewEvents emitted without explicit RedrawEventsCleared
2023-11-26T03:10:04.551727Z WARN winit::platform_impl::platform::event_loop::runner: RedrawEventsCleared emitted without explicit MainEventsCleared
```
When closing
```
2023-11-26T03:10:05.552778Z WARN winit::platform_impl::platform::event_loop::runner: NewEvents emitted without explicit RedrawEventsCleared
2023-11-26T03:10:05.552903Z WARN winit::platform_impl::platform::event_loop::runner: RedrawEventsCleared emitted without explicit MainEventsCleared
```
*Note* I haven't yet tried to reproduce on a pure winit example. I will try to get to that when I can.
Contributor guide
Research direction
Start by reproducing the warnings with a Bevy 0.12 rendering app and a GeForce Experience overlay on Windows 10. Compare the behavior with a pure winit example, as suggested in the issue, then inspect the winit platform implementation and event-loop warnings. Done means opening and closing the overlay no longer emits these warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100