Hi
- Is this a Curvy related issue?
It seems to me that it is not, since the Update method is taking nearly the same time in both scenarios. Also, the increase in CPU usage is done inside a method waiting for GFX commands. Curvy is mostly about CPU work, and not graphics one, so I doubt anything in Curvy could make the wait for graphics commands longer.I looked in Curvy's code for all the usages of the Invoke method (which is a Unity method used mostly to call methods with a delay). I found only one usage of the Invoke method on the CurvyGenerator's Update method. The call stack pf the Update method in the profiler's screenshot is clearly different from the one calling the Invoke method, but for the sake of completeness, let's ignore this point. The Invoke method is called inside the editor of property drawers. So to make a test, let's try to not make that code execute. That means: please try profiling again while making sure that no Generator window (or any other window from Curvy) is open, and no Curvy related game object is shown in the inspector. Did this change the profiling result? - How to solve the issue?
Based on my belief that this is due to a regression in Unity, please look in their forums (and internet in general) if anyone had the same issue. If no luck with that, try using the Unity versions between 2020.3.22f1 and 2020.3.25f to define which version introduced the regression. Once that done, look at its release notes, maybe something in their might help. Otherwise, open a unity bug ticket with all the details you have. Creating a forum thread on their forums might help too.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
