UkoeHB
UkoeHB
If bevy implements command batching, this would no longer be a perf issue (although observers *might* still run separately).
See discussion https://github.com/bevyengine/bevy/discussions/15014
See [this discussion](https://github.com/bevyengine/bevy/discussions/15014) for a required-components-based redesign.
Yep it just needs to be documented. > So far I haven't had a problem with occasionally updating both when there was a mismatch, so that seems like an acceptable...
If you reduce frame rate significantly, e.g. with `WinitSettings`, then CPU usage drops. That's the only 'solution' I have found. Framepacing does nothing.
> Reduce frame rate to what? Like 1-10 FPS...
There is prior art for this in `sickle_ui`, which has a 'flux interaction' framework for applying dynamic styles (in combination with a pseudostates feature for e.g. Open/Closed states). [Here](https://github.com/UkoeHB/sickle_ui) is...
> A reconnection attempt when a socket dies while establishing connection, or can not be opened should respect retry timeout as well, otherwise we're risking a potential DoS attack of...
> However, if the connection suceeds, and then the close frame is received immediately, a reconnection timeout is not applied, and the client reconnects immediately. It seems, that there should...
@asn007 fixed in latest master. Will ping @gbaranski for a point release.