03-22-2021, 05:27 PM
There is unfortunately little you can do that doesn't involve Curvy's code modification. Besides the idea of subdividing the work on multiple generators, and update them at different frames, I don't see much to do. But maybe if I have a look at your scene, I might find something to improve the situation. I am right now in the middle of making some optimizations for Curvy Generator, so sharing your scene might be helpful for me to use as a benchmark
About having a single generator or multiple ones, every generator comes with an overhead, but it is a negligible overhead compared to whatever your generator is doing if it manages to freeze the game.
About multithreading, CG is single threaded right now, and besides modifying Curvy's code, there is nothing you can do to execute a CG in a multithreaded fasion.
Having multithreading in CG is definitely something that could improve the performance. I am not expecting huge performance increase from it, since Unity's methods are very often not allowed to be called from outside, and the nature of the CG implies a sequential order of execution between the different modules, but still things can be further improved with more multithreading.
When Curvy 8.0.0 will be released, one of the new modules in it will execute most of its work in different threads, but nothing major will be done to make the whole Curvy Generator multithreaded.
About having a single generator or multiple ones, every generator comes with an overhead, but it is a negligible overhead compared to whatever your generator is doing if it manages to freeze the game.
About multithreading, CG is single threaded right now, and besides modifying Curvy's code, there is nothing you can do to execute a CG in a multithreaded fasion.
Having multithreading in CG is definitely something that could improve the performance. I am not expecting huge performance increase from it, since Unity's methods are very often not allowed to be called from outside, and the nature of the CG implies a sequential order of execution between the different modules, but still things can be further improved with more multithreading.
When Curvy 8.0.0 will be released, one of the new modules in it will execute most of its work in different threads, but nothing major will be done to make the whole Curvy Generator multithreaded.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.