02-11-2021, 04:25 PM
Hello 
I'm trying to optimize Curvy as much as possible so it runs well also on lower-end platforms. I've been looking at the profiler and found some Curvy related updates:
Node.Update
CurvySpline.Update
SplineComputer.Update
CurvySplineSegment.Update
All together they take around 2ms on my target platform.
I don't need to update anything at runtime (except moving PathControllers). The splines don't change. Generators don't change, don't need to regenerate.
I was wondering what I could do to reduce the footprint of Curvy as much as possible for this.
What I did so far:
- I turned off Auto Refresh for all Generators.
- I have the output of Generators as Static
Can I set a Spline to not update at Runtime? Is just disabling the component an acceptable way to do that?
Any tips would be very appreciated
Thank you
Michel

I'm trying to optimize Curvy as much as possible so it runs well also on lower-end platforms. I've been looking at the profiler and found some Curvy related updates:
Node.Update
CurvySpline.Update
SplineComputer.Update
CurvySplineSegment.Update
All together they take around 2ms on my target platform.
I don't need to update anything at runtime (except moving PathControllers). The splines don't change. Generators don't change, don't need to regenerate.
I was wondering what I could do to reduce the footprint of Curvy as much as possible for this.
What I did so far:
- I turned off Auto Refresh for all Generators.
- I have the output of Generators as Static
Can I set a Spline to not update at Runtime? Is just disabling the component an acceptable way to do that?
Any tips would be very appreciated

Thank you
Michel