02-06-2020, 10:13 PM
Hi,
I did some preliminary work on this. The CPU usage boils down to these Unity methods: Gizmos.DrawRay, Gizmos.DrawCube and HandleUtility.GetHandleSize. These methods seem to not be efficient enough when called thousands of times. I might get some 10% or 20% perfs with some small improvements, but the real optimization (things like twice as fast, or an order of magnitude faster) would mean writing my own batchable alternatives to these methods.
Like I said earlier, I will work on this later, but I thought you might be interested in my preliminary work.
I did some preliminary work on this. The CPU usage boils down to these Unity methods: Gizmos.DrawRay, Gizmos.DrawCube and HandleUtility.GetHandleSize. These methods seem to not be efficient enough when called thousands of times. I might get some 10% or 20% perfs with some small improvements, but the real optimization (things like twice as fast, or an order of magnitude faster) would mean writing my own batchable alternatives to these methods.
Like I said earlier, I will work on this later, but I thought you might be interested in my preliminary work.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
