@DanielPiker I saw a post authored by you which mentioned that certain goals are computationally heavier than other and some are exceptionally heavy when dealing with many-against-many computations. Is there a way to see detailed computational profiling broken down by goal? What I’m hoping for is something like the profiler widget but specific to K2. I’m running very large models and while I have some ways to speed them up applying those methods blindly isn’t providing the results I’m looking for.
Ideal Example: I find data somewhere that shows a specific goal, lets use a soft body collide, is more computationally intensive per input than other goals. I then write a small script which only creates soft body collide goals for meshes which could be near each other instead of checking all meshes to all meshes in the environment.
Does something like this already exist? Is there another way to profile or performance check the goals?
Thank you!!