05-27-2024, 04:14 PM
Update:
After looking at the source code I can see a big issue for me. The way how CurvyGlobalManager works currently isn't something that will be ok for me.
I noticed the comment:
//TODO split this class in two, one containing monobehaviours, that should inherit from dtsingleton, the other containing non monobehaviours, that would use a regular singleton (CurvyProject?). The goal is to avoid instantiating CurvyGlobalManager (which in expensive, see DTSingleton.Instance) when not needed
Which lets me thinking that you might be onto something similar as I am. Is there any eta or progress going on with it?
On the other hand - I think there should be a possibility to keep one CurvyGlobalManager per scene (and accessing it with scene reference). Is it something that could be done easily?
After looking at the source code I can see a big issue for me. The way how CurvyGlobalManager works currently isn't something that will be ok for me.
I noticed the comment:
//TODO split this class in two, one containing monobehaviours, that should inherit from dtsingleton, the other containing non monobehaviours, that would use a regular singleton (CurvyProject?). The goal is to avoid instantiating CurvyGlobalManager (which in expensive, see DTSingleton.Instance) when not needed
Which lets me thinking that you might be onto something similar as I am. Is there any eta or progress going on with it?
On the other hand - I think there should be a possibility to keep one CurvyGlobalManager per scene (and accessing it with scene reference). Is it something that could be done easily?