Problem with working with multiple scenes

[_Aka_]

Your solution is not a bad one, but you need to be aware of what it implies:
If you see how the CurvyGlobalManager is used in the code, you will see that it is mainly for 3 things: connections, pools and editor settings (such as what gizmos to display).
By having one CurvyGlobalManager instance for each scene, I suspect that:

• you will solve your connections problem
  
• have duplicated pools, which will reduce the efficacy of the optimizations brought by the usage of pools. This might not be a big deal for you
  
• have duplicated fields storing editor settings, which might create discrepancies between the actual editor setting and the one stored in CurvyGlobalMange. This might not be a big deal if you don't change the editor settings much
  

Please let me know how your idea of having an instance per scene will go
Thanks and have a nice day