Water3 slows the Editor excessively

Good day,

I implemented the new Water3 Pro (beautiful by the way) and saw that the script slows down the IDE considerably.

I expected in-game performance to be affected however what I didn’t expect was the whole IDE to become quite slow. Saving takes literally 10x longer (from a fraction to a second to actualy a good 2-3 seconds). Copying, renaming assets… everything is affected.

This happens in the wireframe mode too so it must be the scripts running behind the scene.

The solution right now is to deactivate the GO containing the Water3 when working. Either my computer is quite slow (it’s not a beast but it does the work) or the IDE is a CPU hog when dealing with editor scripts.

Thanks for any input.
I just wanted to share this.

Playing a bit with it, I just found one other problem… at least I think it is a bug…

Disabling the water3 after it’s been enabled initialy doesn’t do anything to lower the draw calls.

After launching the game, if I have the water3 activated, unity will give me 500 draw calls and around 120fps. If I deactivate the scripts gameobjects (by script or by hand during play mode) the exact same numbers are kept. And all of this even though I cannot see the water anymore (it does indeed dissapear from the view). Culling masks have no effect either.

Now, if I initialy launch the game without having water3 activated; 240 draw calls and over 300 fps.

Can anyone confirm this or I’m missing something?