Mateusz Wachowiak
Mateusz Wachowiak
I believe we can use `bevy_diagnostic` for this.
Okay, I get the idea, if we create a `bevy_debug` crate, we should consider moving `bevy_log` into it. I'm not sure if this wouldn't create some issues, but having two...
Probably, we also want an option to enable only some tools ### 1st solution We remove `bevy_dev_tools` from default features and lock every tool under a new feature - this...
I've rebased onto main
From PR that you linked: > While a AMD driver update can resolve this issue, it still gets reported regularly and is likely to become a source of support headache...
> Which PR was this adopted from? We should link it here and close it out. I've seen it before, it's #3440
> should we Block this until the bevy tools get merged (#11341)? I don't think there is a need for that. We can move it later - it's probably going...
> Hmmm, dont quite get the Dependencies error, didn't changed anything in dependencies... Seems to be failing since 35ac1b1
> Forgot to say: Due to the limitations with windows of bevy_gizmos, I limited this tool to the primary window only, I don't have any idea in particular of how...
Makes sense, but I still think we should at least mention it in `OrthographicProjection` so that we can point users in the right direction. Would like to get someone else's...