Rob Parrett

Is this considered a bug?

The above workaround seemed very promising at first, but I was seeing some very bizarre behavior from my vehicle -- almost as if the motor/collider were applying their forces in...

Thanks! Let me give this some brief thought. I had some existing vague plans for input filtering that I probably won't actually implement. But I'll likely merge as-is.

~~`auto_exposure` also seems completely broken. (tested macos, win/4080). separate issue created: #15824~~ `ssao` as well, bisected to #15320. run and press `151515` and observe nothing changing.

Opened #15997 and #15998. They may be platform specific if you weren't able to reproduce.

Just noting that this seems to be going in the opposite direction of a sentiment expressed here: https://github.com/bevyengine/bevy/discussions/15014#discussioncomment-10574459 with regard to the new `LineBreak` and `JustifyText` components. I think this...

Related: #14151

> No idea why this isn't happening when both width and height increase, https://github.com/bevyengine/bevy/pull/19462/files#diff-403d26a0d50b6a92a90c187a4241843e6b06d82c7540c72c013c231e8539c20dR68 Seems that `copy_size` here should be the minimum value in each dimension instead.

Same issue with Bevy 0.14 and current Bevy main. ``` AdapterInfo { name: "ANGLE (Apple, ANGLE Metal Renderer: Apple M1 Max, Unspecified Version)", vendor: 4203, device: 0, device_type: IntegratedGpu, driver:...

Still broken with Bevy 0.15 / current Bevy main. Presenting with a different error now, but this could just be #16525 also happening on top of the previous issue. ```...