11-28-2014, 10:42 AM
Have you profiled this with Unity 4.6 (or 5 Beta) to be sure this is still a problem? UT said they greatly improved performance on this. I'll run some tests with 5.0 by myself and probably add pooling if this still is an issue.
Otherwise, pre-generating them and enabling them on demand is an option, but to be honest I doubt that the current version can handle this properly because the spline sorts it's CPs by hierarchy order (I changed this for 2.0).
Also, without having it profiled I would guess that the recalculation the spline does when adding CPs eats more time than instantiating a GameObject. Though you can add multiple points in a row and then refresh the spline once.
Another idea that you might want to consider: What about pregenerate a spline with 20 CPs and set all "unused" CPs to the same position as the last "enabled" one? Or, probably even easier, ignore them completely and only use (render, travel etc..) the range you want (say from TF=0 to TF=0.5, if you have 10 of 20 CPs in use)
Let me know if that helps, otherwise I'll add pooling to the current 2.0 dev version and give you access to it.
Jake
Otherwise, pre-generating them and enabling them on demand is an option, but to be honest I doubt that the current version can handle this properly because the spline sorts it's CPs by hierarchy order (I changed this for 2.0).
Also, without having it profiled I would guess that the recalculation the spline does when adding CPs eats more time than instantiating a GameObject. Though you can add multiple points in a row and then refresh the spline once.
Another idea that you might want to consider: What about pregenerate a spline with 20 CPs and set all "unused" CPs to the same position as the last "enabled" one? Or, probably even easier, ignore them completely and only use (render, travel etc..) the range you want (say from TF=0 to TF=0.5, if you have 10 of 20 CPs in use)
Let me know if that helps, otherwise I'll add pooling to the current 2.0 dev version and give you access to it.
Jake