dire ivy
There's some seriously lacking tooling that tbh is very easy to implement. Here's a couple I've fixed personally that I think Unity should replicate.
This is a 1 line fix
https://github.com/tertle/com.unity.entities/commit/4fa71eee8de12b4fc2f77e7eb89d44b471e1bda0
I've wanted this for ages, the ability to see all a systems dependencies in the editor [not just from queries] and I finally just implemented this and why this post exists. It was a 30min job as thankfully Entities pretty much has all the tools already for this.
https://github.com/tertle/com.unity.entities/commit/7f0106667b6e69a009562cd416296e6b9d52e952
Pretty minor but nothing yells not used and maintained than visual bugs. A quick example of this is the above image, the 4 on the Read Dependencies (which is a FoldoutWithoutActionButton) is clearly visible - this is only because I've fixed it.
If you look at default entities this number is very hard to read, for example lets look at relationship view.
Before and after screenshots are attached on the relationship view. Notice how it's barely readable.
This is a 1 line uss change
https://github.com/tertle/com.unity.entities/commit/7f0106667b6e69a009562cd416296e6b9d52e952#diff-0e0abfc111590a8f4aca9bd60a48b5d3f8adbfa1b9934808863b0373b5460b78R28
Lack of maintained tooling
dire ivy
Missing Tooling
terse ridge
Haha I though 1 was like that for a reason. Seems like a pretty significant bug.
cobalt lion
number 2 is pretty important to figure out why jobs from multiple systems can't run in parallel.
however i wish this would be extended in its final form so 2 systems can be compared and highlight the components that are preventing it. should be quite easy to calculate just the UX is something to be figure out
lavish jackal
Great stuff, @dire ivy ❤️
Thanks for taking the time to improve the tooling for us! I'll see if we can include this in a future release of the Entities package
lavish jackal
The changes have landed and will be available in the next Entities 1.4.x release
Thanks again Tertle