Fluvio - Fluid Dynamics for Unity

They can be added in the Player Settings for each platform (Edit > Project Settings > Player).

 

Adding FLUVIO_PRO;UNITY_5 the error still persist but adding FLUVIO_DEVELOPMENT;UNITY_5 managed to compile it, the problem now is with the blob, it show up as purple blob instead of bluish on paint scene, also logged error :

Code (csharp):

1.  
2. [Fluvio] (FluvioHelpers.FindAttachedFluid): No associated fluid found. Have you created a fluid in the scene?
3. UnityEngine.Debug:LogError(Object, Object)
4. Thinksquirrel.Fluvio.FluvioBase:LogError(Object, String, String, Object) (at Assets/Fluvio/_Main/Source/Thinksquirrel/Fluvio/FluvioBase.cs:147)
5. Thinksquirrel.Fluvio.Internal.FluvioHelpers:FindAttachedFluid(Fluid, FluidPlugin) (at Assets/Fluvio/_Main/Source/Thinksquirrel/Fluvio/Internal/FluvioHelpers.cs:57)
6. Thinksquirrel.Fluvio.Plugins.FluidPlugin:OnEnable() (at Assets/Fluvio/_Main/Source/Thinksquirrel/Fluvio/Plugins/FluidPlugin.cs:78)

On '3' scene nothing shows up when playing on editor.

 

A few things:

1) When using the source code directly, you don't need to define UNITY_5 as Unity will do that one automatically. Also remember to delete the DLLs if you haven't already.
2) Also when using source code builds directly, the example scenes won't be compatible. This is unfortunately due to how Unity stores metadata differently for assemblies vs individual source files. We recommend recompiling the modified source back into a DLL instead (without the FLUVIO_DEVELOPMENT define, but with the FLUVIO_PRO and UNITY_5 one). The new DLL would need the same .meta file as the old one.
3) If you're just attempting to use Fluvio (and not modify any code), do note that using source code directly isn't required - Fluvio ships pre-assembled. You're most likely aware of this but occasionally some customers may think they are required to rebuild the assemblies for Pro.

That particular error by the way usually points to a missing component (it happens when a plugin can't any fluid in the scene to attach to).

Hope that helps!

 

Thanks again , Would you please add Cloo source code in the next release?

 

That part is open source and available here:
https://github.com/thinksquirrel/cloo-unity

 

Runtime compiled fine but got some struggle on editor

Code (csharp):

1.  
2. 1>------ Build started: Project: Fluvio.Editor, Configuration: Release Any CPU ------
3. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(37,10,37,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
4. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(37,10,37,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
5. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(62,10,62,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
6. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(62,10,62,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
7. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(68,10,68,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
8. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\EditorWindows\FluvioWelcomeWindow.cs(68,10,68,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
9. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioComputeShaderPostprocessor.cs(47,10,47,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
10. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioComputeShaderPostprocessor.cs(47,10,47,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
11. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioEditorHelpers.cs(395,6,395,20): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
12. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioEditorHelpers.cs(395,6,395,20): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
13. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(81,10,81,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
14. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(81,10,81,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
15. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(120,10,120,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
16. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(120,10,120,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
17. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(189,10,189,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
18. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(189,10,189,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
19. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(195,10,195,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
20. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(195,10,195,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
21. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(203,10,203,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
22. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(203,10,203,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
23. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(218,10,218,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
24. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(218,10,218,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
25. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(277,10,277,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
26. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioMenuItems.cs(277,10,277,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
27. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioPreferences.cs(232,36,232,50): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
28. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\FluvioPreferences.cs(232,36,232,50): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
29. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1560,10,1560,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
30. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1560,10,1560,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
31. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1608,10,1608,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
32. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1608,10,1608,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
33. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1731,66,1731,80): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
34. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1731,66,1731,80): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
35. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1736,72,1736,86): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
36. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1736,72,1736,86): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
37. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1742,74,1742,88): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
38. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1742,74,1742,88): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
39. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1747,80,1747,94): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
40. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1747,80,1747,94): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
41. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1753,74,1753,88): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
42. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1753,74,1753,88): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
43. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1758,80,1758,94): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
44. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluidParticleSystemInspector.cs(1758,80,1758,94): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
45. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluvioInspectorBase.cs(177,65,177,79): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
46. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluvioInspectorBase.cs(177,65,177,79): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
47. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluvioInspectorBase.cs(182,56,182,70): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
48. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\Inspectors\FluvioInspectorBase.cs(182,56,182,70): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
49. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\PropertyDrawers\FluvioMinMaxCurveDrawer.cs(249,10,249,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
50. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\PropertyDrawers\FluvioMinMaxCurveDrawer.cs(249,10,249,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
51. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\PropertyDrawers\FluvioMinMaxCurveDrawer.cs(255,10,255,24): error CS0246: The type or namespace name 'UsedImplicitly' could not be found (are you missing a using directive or an assembly reference?)
52. 1>C:\Users\Public\Documents\Unity Projects\Fluvio\Fluvio.Editor\Thinksquirrel\FluvioEditor\PropertyDrawers\FluvioMinMaxCurveDrawer.cs(255,10,255,24): error CS0433: The type 'JetBrains.Annotations.UsedImplicitlyAttribute' exists in both 'c:\Users\Public\Documents\Unity Projects\Fluvio\Assets\Fluvio\_Main\Fluvio.Runtime.dll' and 'c:\Program Files\Unity\Editor\Data\Managed\UnityEngine.dll'
53. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
54.  

 

Don't have the source at hand right now but I think you need to include the FLUVIO_ANNOTATIONS define as well (for Resharper stuff) when building. Will double check that and include it in the guide, since that's new.

 

Now my define are FLUVIO_PRO;UNITY_5;FLUVIO_ANNOTATIONS and still getting the same error. Should JetBrains.Annotations compiled in runtime? or i need to add it into editor?. Currently it being referenced from runtime dll.

From your original Package, it seems JetBrains.Annotations only exist on runtime not on editor dll, hence i am confused about above error.

 

Taking a quick look at the code, annotations are compiled under these conditions:

Code (csharp):

1.  
2. #if (!UNITY_EDITOR && FLUVIO_DEVELOPMENT) || !FLUVIO_DEVELOPMENT || FLUVIO_ANNOTATIONS
3.  

So that is:

• When using source code directly, in a build with FLUVIO_DEVELOPMENT defines, or
• If FLUVIO_DEVELOPMENT is not defined, or
• If FLUVIO_ANNOTATIONS is explicitly defined

I was actually wrong, you shouldn't need to define FLUVIO_ANNOTATIONS directly. The annotations do need to be included at runtime, but when recompiling the source (FLUVIO_DEVELOPMENT not defined, UNITY_EDITOR not defined for DLL builds) that will happen automatically following the conditions above.

Not entirely sure what the issue is here without knowing your project setup. Do you have both the DLLs and C# files in the project right now? That will break things. Also, are you trying to A) Use the source directly or B) Build it into a separate DLL? If building it into a separate DLL, you need to create a separate Visual Studio/MonoDevelop solution for this (and reference UnityEngine/UnityEditor as appropriate).

 

Just read your edit also. If Fluvio.Editor.dll is referencing Fluvio.Runtime.dll, it will have access to the annotations as well. Do note your DLLs need to be named Fluvio.Runtime and Fluvio.Editor (the editor assembly is defined as a friend assembly, so has access to internal members of the runtime).

Finally, we may want to take this to a ticket in order to not derail the forum thread. I'd be happy to provide some additional help to get your source build working You can open up a ticket here and I'll pick it up:

Submit a request

 

Having OpenCL issues? I've assembled a list of recommended OpenCL drivers for Fluvio:

https://support.thinksquirrel.com/hc/en-us/articles/204662628

 

Hi,
I have used your plugin for 1 year , but now I find that my standard edition is no wealth. It always crashes in nvidia gtx 750 cards(lastest drivers and cuda drivers have been tested).
And i'm in a B2B exhibition business, I can't tell my custom to repurchase all his video cards !!
Is there a way to solve the crashes in OpenCL?
Or is there a way to update my standard edition to Pro ?

 

Hi Free Compass,

There are a few options here:

• In Edit > Project Settings > Fluvio, you can change the OpenCL hardware acceleration to use the CPU instead of the GPU and blacklist the NVIDIA drivers. OpenCL works on the CPU as well, not just the graphics card, so your customers definitely won't have to repurchase any video cards. OpenCL CPU simulation with Fluvio may actually perform better than GPU simulation (unless your particle counts are really high and not realtime, which is unlikely).
• OpenCL can be disabled entirely - the new C# solver is still much faster than Fluvio 2.x. Obviously not the best route, of course.

The post above is mainly for guidelines when developing using the beta until the NVIDIA issues are sorted out. I will actually be blacklisting the NVIDIA OpenCL driver in the next version for now, since I've had a decent amount of bug reports on it and I don't recommend using it in production just yet.

I definitely hear you with the NVIDIA issues though (I develop with an NVIDIA card and get just as many OpenCL crashes). Working on a fix, but it will take some time.

EDIT: Maybe I spoke too soon! Some more digging and I think I've found the portion of the OpenCL kernel that the NVIDIA drivers balk at. It definitely seems like a bug on NVIDIA's end. I've inserted a workaround for now which will be in the next update, until I figure out how to get this piece of code to work properly.

 

Thank you !
I will have a try for Intel OpenCL now.

 

Beta 5 is out! This build includes the NVIDIA workaround I mentioned above. For the majority of people, you shouldn't be getting OpenCL crashes anymore (so please send me bug reports if you do). There's still a minor OpenCL-related bug that can cause particles to disappear when using multi-fluid simulation, but I should have that fixed soon.

Also, a few big changes with beta 5:

• I've added the Waterfall example! However, example scenes have been moved from the main project. This was done to provide updates of Fluvio's core at a much faster rate. You can find all example scenes on our publisher page (link here). Once the Asset Store updates its search index (I think this can take up to a day or more), the "Explore Fluvio" button in the welcome window should find all example scenes as well. You may get an import error when importing example scenes. These can be ignored and should be fixed by the next beta.
• Unity 4.5/4.6 users may need to do a find/replace on GUIDs when updating with an existing project. I changed the GUIDs for the DLLs in 4.6 to match the ones in 5.0. Now all editions and versions of Fluvio have the same GUIDs for DLLs, making upgrading from Free -> Standard -> Pro painless (just a couple of clicks when using the same version of each package).

Here are some pictures of the updated waterfall scene. The old scene had 200 particles - this one has 3000. On top of that, even the fish have fluid simulation! I still have plans to update the textures on the included models with proper high-resolution PBR materials. Expect more high quality example scenes like this as well!







Finally, you guys have been awesome - this past week we had over 100 installs of Fluvio in just a 1-week period!

 

Since this information has been publicly released, I wanted to share a bit of awesome news for Fluvio in Unity 5.1, and the future of our platform support.

Also keep in mind that Unity's roadmap is always subject to change, and the following is entirely based on when they ship these features.

So, if you haven't already, you should check out this forum post from Unity, specifically the "Unified GL rendering backend" document:
http://forum.unity3d.com/threads/5-1-beta-information-preview.317493/

This is fantastic news for Fluvio. Unity's Compute Shaders (meaning GPU accelerated fluid simulation) will soon be available on mobile, and likely other platforms in the future. Fluvio Professional will support this out of the box (we already provide support for consoles), hopefully at or soon after compute support is available on other platforms.

Exciting times up ahead

 

Can't wait. That sounds fantastic !

 

A new beta release will be landing for Fluvio either today or tomorrow with lots of bug fixes. It re-introduces the optimizations I shut off for NVIDIA cards, fixes some bugs with the index grid (disappearing particles on non-NVIDIA cards), and now uses a much more GPU-friendly grid implementation.

Also, if you're based out of Texas - I'll be speaking this Thursday at the Houston Unity Group about Fluvio, including best practices and tips and tricks. I'll also be giving out some Asset Store vouchers. Definitely come and see it if you can! If not, I'll make sure to release the presentation notes after

 

And beta 6 is up! This should have a fairly decent performance increase overall, especially with OpenCL GPU simulation. There are more performance increases in the works, mainly reducing the amount of kernel arguments, and allowing users to specify which arguments they want to pass to plugins and cut out the unnecessary ones. All known disappearing particle issues should be fixed with this update.

As of this update, the default simulation mode is set to OpenCL GPU. If you're upgrading, you'll want to change it manually under Edit -> Project Settings -> Fluvio. Tests are showing that GPU performance is now surpassing CPU performance by a decent amount in most cases (especially with higher particle counts).

I've also pushed a minor update for the waterfall example that sets the camera to deferred rendering by default, and moves some Add Component menu items into the proper location.

 

Just released a hotfix for beta 6 (still versioned 3.0.0b6) that should fix the 404 error in the welcome window. It also adds a short README document to the root Fluvio folder with links to example projects, documentation, and support.

 

Asset Store Madness!



Fluvio Standard and Professional are both currently 65% off in the Asset Store!

If you haven't tried it yet, what are you waiting for? Explore Fluvio today!

 

Is this example included in pro or standard or free?

 

It currently isn't (was a 5 minute demo) - would you be interested in it? I am currently taking suggestions for the next few examples.

Also, all examples are now separate from Fluvio itself. You can find them on the Asset Store by searching for Fluvio, clicking "Explore Fluvio" in the Welcome window, or checking out the README in the newest beta.

 

Hi,

Is there a comparisson between versions for Fluvio 3 ?

I recall GPU acceleration was initially planned for Pro only, but later was announced for other versions, is Free included in this or is Standard and Pro only ?

Is there any difference between Pro and Standard other than open code in Pro ?

I am targeting Windows and consoles (PS4 mainly, maybe XBONE too), would Pro be recommended for such use, even if code access is not nessesary ?

Thanks

 

You can find the up-to-date comparison here:
https://support.thinksquirrel.com/hc/en-us/articles/202267604

GPU acceleration is available for all three versions (Free, Standard, and Pro). Along with source code, Pro adds GPU acceleration support for Android (Unity 5.1 beta only) and for consoles.

 

Thanks for clarifying. So for PS4 would best to have Pro i suppose.

Is there a webplayer demo showcasing the water with the Pro features, like the fluid image effect and refractive shaders ?

 

Working on it

I've been quite busy with a few projects, so I haven't been able to post enough demos and videos as I would like - been putting priority on keeping beta builds updated and fixing bugs. But expect quite a few of these - the latest beta split off examples into their own projects, and we plan on having a lot more of them.

 

A simple demo like the scene with the water wheel should be fine, i just want to see the blending and possibilities.

My main problem right now is that in the waterfall demo the water seems a bit confusing, while the waterweel seems clear and refractive which is closer to what i would like to achieve in my game. An export to webplayer of this scene would be great to have before buying the Pro, to see how this shader and blob blending/shading look exactly close up.

Maybe a very hi res pic/gif/video would be fine too, but seeing it in motion and full zoom would be even better

 

Also, is this example 2d or 3d?

and if it is 3d, is the force of the water particles turning the wheel?

 

I didn't realize people wanted to see that scene, I should've saved it!

I'll definitely do that - the water here is actually the water in the Three example, with a Color by Density gradient and Size by Density curve.

It's a 2D fluid, but using 3D rigidbodies. And correct, the water particles are turning the wheel here (the wheel is just a hinge joint anchored to the world).

 

Is it possible to get that water look in 3D using the Pro shaders / image effects ?

 

Sure! So, to explain what's going on with that water there:

1) Fluid Effect shader with PBR, with almost full smoothness
2) Color by Density plugin, which goes from a white color (foam) to a transparent black color (water) to an opaque dark blue color (to simulate depth) and finally an opaque white color (internal foam). This is probably the most important plugin to set up correctly.
3) Size by density plugin. This one is a curve that starts out near zero, spikes up at a low value (for foam/splash particles), then spikes back down and gradually increases in size as the density increases.

I'll definitely see about getting some of these examples on the store. I actually gave a presentation on Fluvio a few weeks ago and made about 20 example scenes for it (including a VR-compatible one). I'd like to have pretty much all of those available as well.

 

That would be great , thanks for the clarifications.

 

To hold you guys over for now, I've made a massive 1440p image dump with a sample of some of the examples that will be making their way to the store (as full scenes). Many of these are work-in-progress; the space scene in particular is under some heavy development and will ship with VR support out of the box.

Also, a new paint scene is on the way!

Full album:
http://imgur.com/a/74FjC

Some samples:

 

Check out this updated video of the Waterfall example, with over 10x as many simulated particles as the Unity 4 version:

 

Hi.

Can you provide an example video of your pro version showing a 3d cup being filled with water that looks realistic? I tried with the free version but I could not get it working right.

Thanks

 

Hey SuperNewbee,

More resources on making boundary fluids are coming soon! Right now I suggest taking a look at the "Three" example to see how to make boundary fluids - you can combine them with Untiy colliders in 3D in order to get realistic collision behavior with concave shapes (like a cup).

If you have any specific questions on how to get things working with your project, please feel free to open a ticket at:
https://support.thinksquirrel.com/hc/requests/new

 

I got the full version, looks very cool so far

I would love to have one ready to use sample that will use clear water like in the pic above, with water blending, but in the 3D waterfall sample

Is it possible to have such a setup sample inlcuded in the pack ?

Thanks

 

Working on it! We have plenty to announce with Fluvio regarding examples and sample fluids really soon...

For reference, that fluid is using the default fluid effect with a black, clear color (alpha near zero), and "Fake specular effect" turned up a little bit.

 

I just imported Fluvio into my project, and even though it's not being used in my scene yet, I get log spam every time I save the scene:

Cleaning up leaked objects in scene since no game object, component or manager is referencing them
FluvioSettings has been leaked 1 times

Is there anything I can do to avoid this log spam?

 

Hi OneThree,

Thanks for the report! We'll look into this one. Deleting the FluvioManager asset under Assets/Fluvio-ProjectSettings (and any duplicates, if any) should fix it. It'll reset your project settings for Fluvio to the defaults, of course. The asset is automatically created when you go to Edit > Project Settings > Fluvio.

If you don't have a settings file visible, try going to that option and seeing if that fixes it.

 

Thanks for the quick reply!

I just imported Fluvio into my Unity 5.0.2 Pro project and ran the C# installer. For whatever reason, that error isn't showing up any more. The settings file is still there, but it isn't leaking. Weird; must have been some odd collision with another asset or a corrupted install or something.

Anyway, all appears to be well now. I'll report back if it crops up again.

 

This just cropped up. :-/

I didn't have that file, but it was created by going to the menu option. Unfortunately, deleting FluvioManager did not fix the issue. I also went into the options to regenerate the fils, but the result is the same: I get log spam every time I save my scene.

 

Hm, do you have a fluid in your scene? I'm thinking somewhere a reference to the FluvioManager object isn't going away when it should. Another thing to check would be to see if you have a second inspector tab open with the object (or a fluid) selected, or if you have either the FluvioManager/fluid selected when saving the scene.

Can you try to reproduce the issue from a from-scratch project and send some specific steps to support? You can access the support website at:
https://support.thinksquirrel.com/hc/requests/new

This issue is mainly cosmetic by the way, it shouldn't happen in a build (and if it does, Unity will always clean it up). Will definitely see what I can do though; even if I can't reproduce the issue there are some checks that I can probably do to make sure the manager never leaks.

 

Nope, nothing in the scene.

I just started a new project in Unity 5.0.2. Completely blank. Once it was created, I imported only the Fluvio package and installed C#. I then went to Edit->Project Settings->Fluvio and opened that.

Every time I save the scene, I get this:

Cleaning up leaked objects in scene since no game object, component or manager is referencing them
FluvioSettings has been leaked 2 times.

Does that happen for you if you follow the same steps?

Also, while I know this is mainly cosmetic, it's still an issue for people who want the log to be useful. I use the console for P4 integration and legitimate warnings and errors, so having it constantly get filled with useless messages that I can't fix really detracts from the usefulness of the console window; it should only output messages if it's something the user needs to address.

 

I just found another bug with Fluvio, this one insanely frustrating.

After I ran into the log spam above, I deleted Fluvio from my project. After doing so, I started getting two warnings every time I ran the scene:



I endlessly searched my project and hierarchy tabs and found no objects with missing scripts, and finally got to the point where I made a copy of my project and started deleting elements until there was literally nothing in my project except an empty scene. There was nothing in the project tab, and the hierarchy of the scene was blank ... but the two warnings kept coming up.

It turns out that Fluvio had added a hidden object to my scene that was then saved into the scene ... and not cleaned up when Fluvio was deleted from the project. I got to the point where literally the only thing in my project was an empty scene, so I serialized it to text and opened it in a text editor and found this:

--- !u!1 &983704827
GameObject:
m_ObjectHideFlags: 1
m_PrefabParentObject: {fileID: 0}
m_PrefabInternal: {fileID: 0}
serializedVersion: 4
m_Component:
- 4: {fileID: 983704829}
- 114: {fileID: 983704828}
m_Layer: 0
m_Name: Fluvio Runtime Helper
m_TagString: Untagged
m_Icon: {fileID: 0}
m_NavMeshLayer: 0
m_StaticEditorFlags: 0
m_IsActive: 1
--- !u!114 &983704828
MonoBehaviour:
m_ObjectHideFlags: 1
m_PrefabParentObject: {fileID: 0}
m_PrefabInternal: {fileID: 0}
m_GameObject: {fileID: 983704827}
m_Enabled: 1
m_EditorHideFlags: 0
m_Script: {fileID: 1904570633}
m_Name:
m_EditorClassIdentifier:
--- !u!4 &983704829
Transform:
m_ObjectHideFlags: 1
m_PrefabParentObject: {fileID: 0}
m_PrefabInternal: {fileID: 0}
m_GameObject: {fileID: 983704827}
m_LocalRotation: {x: 0, y: 0, z: 0, w: 1}
m_LocalPosition: {x: 0, y: 0, z: 0}
m_LocalScale: {x: 1, y: 1, z: 1}
m_Children: []
m_Father: {fileID: 0}
m_RootOrder: 0
--- !u!115 &1904570633
MonoScript:
m_ObjectHideFlags: 0
m_PrefabParentObject: {fileID: 0}
m_PrefabInternal: {fileID: 0}
m_Name:
serializedVersion: 4
m_Script:
m_DefaultReferences: {}
m_Icon: {fileID: 0}
m_ExecutionOrder: 0
m_ClassName: FluvioRuntimeHelper
m_Namespace: Thinksquirrel.Fluvio.Internal
m_AssemblyName: Assembly-CSharp.dll
m_IsEditorScript: 0​

That hidden object (FluvioRuntimeHelper) was embedded and invisible in my scene. I had to edit the scene in text by hand -- which is a dangerous thing to do -- to get rid of it.

I downloaded this asset today because it was free, but so far it has given me nothing but headaches ... and I haven't even tried to use it in a scene yet. Just installing it has infected my project.

 

I have been unable to reproduce this on a clean project, but see below:

Oh, 100% agree here - log spam is never a good thing.

Eek! In that case, it's definitely the runtime helper leaking here. Going to escalate this, and I'll definitely have a hotfix up for this ASAP (in fact, Unity 5 doesn't need the runtime helper due to an API function that was added, so I'll probably remove it for 5.x users). Many apologies for the issue, and thanks for reporting it in such detail.

 

Cool, thanks for the quick reply and escalation. Also, apologies, I forgot to paste in the actual warnings in my previous post; they were standard "The referenced script on this Behaviour is missing" Unity warnings.

 

I've created a hotfix for all Fluvio editions with the following:

• Runtime helper object is no longer saved with the scene, ever
• Any already-existing runtime helper objects will be fixed upon opening a scene, even if they have a missing behaviour on them
• Also fixed a few minor issues preventing compilation for Windows 8 Store/Windows Phone 8

The update is currently running through QA and automated testing and should be up by this afternoon. As it is a hotfix, it will still show up as beta 6 (I'll update this post once it's live).

Edit - This hotfix is now live. If you run into missing behavior issues, opening and re-saving the problematic scenes should fix it.

 

Awesome, thanks so much for the super-rapid reply!