05-29-2019, 01:13 PM
Hi,
Since the objects do not move, I suppose you either called controller.Stop() or set controller.Speed to 0. In both cases, there is no significant computations done, so the None option will not help much. But as always when asked about performance issues, you really should profile your game first, and check that the controller's updating code is really an issue, and only then try to optimize the controller's code.
If you have a lot of objects to place, you might want to use the Volume Spots CG module instead of controllers. Here is its documentation, and you can see examples of its usage in multiple example scenes, like 22_CGClonePrefabs.
Since the objects do not move, I suppose you either called controller.Stop() or set controller.Speed to 0. In both cases, there is no significant computations done, so the None option will not help much. But as always when asked about performance issues, you really should profile your game first, and check that the controller's updating code is really an issue, and only then try to optimize the controller's code.
If you have a lot of objects to place, you might want to use the Volume Spots CG module instead of controllers. Here is its documentation, and you can see examples of its usage in multiple example scenes, like 22_CGClonePrefabs.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.