Aevyrie

> but if I let go too early My best guess is it's caused by bevy's lack of event ordering within a frame.

This already exists in the form of events and event listeners. You could create your own special purpose component for this purpose if you want some other behavior. https://docs.rs/bevy_mod_picking/latest/bevy_mod_picking/events/struct.Drag.html https://github.com/aevyrie/bevy_mod_picking/blob/main/examples/drag_and_drop.rs...

The highlighting plugin was built to support any asset type. You can add a `HighlightingPlugin`, which will allow you to swap out an entity's `Image` asset based on picking state....

Ideally this would be an implementation detail that users would not see, and we would handle batching similar lines either by NaN separating, or by storing something like run length...

> If this process is enough of a burden that you prefer not doing it, does that point to an issue with the public API of this plugin? Is there...

Closing, as this is very out of date.

FYI, https://github.com/bevyengine/bevy/pull/6707 should reduce excess noise in darker areas of banded fog, when not using HDR. Upon pixel peeping, the dithered screenshot above has a lot more noise than it...

IIRC, we are limited by the `winit` event loop, and we can't poll mouse input asynchronously. I had some ideas that I could prototype, that effectively act as a frame-limiter,...

> I believe mailbox vsync should behave similar to disabled vsync in terms of latency. That's what I would expect, but not what I experience in bevy apps. > Predicting...

That doesn't get around the timing problem, presenting it this way just makes it seem like the problem doesn't exist. That's why I presented it in reverse - it makes...