Share animations and renders that you have created in this thread. We would love to see what you've made!

You may attach videos to your post, but you will first need to compress the video to a .zip. Feel free to share via YouTube or any other video/filesharing service.

An excellent free service for easily sharing short animations is Gfycat. Example:

https://gfycat.com/EnchantingPaleAnemonecrab

Hi,

I seem to get a blender crash sometimes when I render.

This happens whether using the 100 or 300 resolution.

Still using the test version - wanted to complete all tests with that first. I have changed the environment as I didn't have the version with textures.

Which files would you like? I can send the version of the scene file I am using.

This happens regardless of if I use the GPU. Have run through VisualStudio for a stack trace if it helps.

To save time you don't need to wait for whole render. As soon as I stop render early the crash happens.

Hello Folks,

I just bought Flip Fluid Simulation Tool for Blender during the May sale; and, too bad for me, I'm not able to install the addon. Any help would be greatly appreciated.

ValueError: register_class(...): already registered as a subclass.

I tried installing Flip on 2.8 out of curiosity, and got the same error.

Kind regards, Bruce

Blender Version (including hash): Blender 2.80 (d415b5c7b85) FLIP Fluids Version: 9.0.5.1 (Experimental) Operating System: Windows 10 CPU: Intel Core i7-7700 @ 3.60GHz GFX: GTX 1070 8GB RAM: 32GB

The FLIP Fluids addon is currently unable to render a frame in EEVEE without crashing (using F12). EEVEE rendering in the viewport appears stable. This seems to be related to this issue: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Scene-Troubleshooting#blender-often-crashes-suddenly-or-does-not-apply-transforms-while-rendering

A workaround that helps render stability is to lock the Blender interface during render (Blender > Render > Lock Interface).

Hoping to get to the bottom of this issue quickly!

Just wondering if there was news of efficiency gains with respect to the solver (or perhaps a different solver better able to leverage multiple cores/GPU). Didn't know how/where else to pose the question.

System Information

Blender Version: 3.2.0, master, 2022-06-08 10:22, e05e1e369187 Addon Version: A FLIP Fluid Simulation Tool for Blender (v1.4.0 Stable 07-JUN-2022) OS: Windows-10-10.0.19043-SP0 GPU: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78 CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz RAM: Unknown (fill in)

Describe the bug

Ok, so i've been trying to render a scene that i made for like 5 days now and nothing is working, the water is frozen on the render but everything else works and is rendering correct in my scene its just the water. I tried everything like exporting the animation but that didn't work, well it did but was taking really long. If I let the export keep going it would have took like 50 hours.

To Reproduce

i had my water at 400 quality and left all the settings the same and enabled sheeting and added textures for bubbles, etc. which i think this is the problem because i was able to easily export the water without any of the foam or bubbles. I then render and think the render is going great and the water is just frozen

Expected Behaviour

I expect the water to be animated when i render it.

Actual Behaviour

the water doesnt move, but it moves in the viewport.

Screenshots

If applicable, add screenshots to help explain your problem.

this is the scene i rendered with the foam and everything but also the foam or the bubbles didn't appear: https://user-images.githubusercontent.com/108705030/178857158-0890c058-6df7-4bcb-8a1e-d59b64dd64cd.mp4

This is the scene i rendered with the fluid exported and then imported in after: https://user-images.githubusercontent.com/108705030/178857227-53c87aa3-61d4-4573-922f-1abe096b516b.mp4

The surface tension solver is in an experimental stage. A known issue is that simulations involving surface tension can become unstable and produce errors in the simulation that look like small pops/explosions (Example 1, Example 2).

At the moment, I am unsure of the cause of these stability problems, but am hoping to solve this problem before a stable release of v1.0.5! It seems that these problems occur more frequently with higher surface tension values and complex obstacle geometry, but also can happen without obstacles in the scene.

The next experimental version (v9.0.5.3 available Feb 1st) includes a change in settings to add a stability parameter for development/testing purposes. Documentation here: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Domain-World-Settings#surface-tension.

- Ryan

System Information

**Blender Version (including hash):**2.79b f4dc9f9d68b and 2.79 5e5f2ead437 (old daily build) **FLIP Fluids Version:**1.0.4 **Operating System:**Windows 10 **CPU:**intel core i7 5960x **GFX:**GTX Titan X **RAM:**G.Skill F4-2800C15-16GRKD

Describe the bug

The fluid motion blur in the attached frames is sometimes apparent - (frames 10, 12,14,16,17,etc) and sometimes not (11, 13, 15, 19, 21, etc. ). All stills were rendered on the same PC. Motion blur on objects in the scene apperars as normal. As expected, there isn't motion blur for the white water particles.

To Reproduce

Following is a link to the blend file and stills: https://1drv.ms/f/s!AuL_h2DNeOJch-1G2w1W6fqjqKMgAw

Expected Behaviour

I expected Blur on the surface object.

Actual Behaviour

Sometimes it's there, sometimes not.

Screenshots

included in the link

Hi,

Have a sim (res 200) where parts of mesh or at least where I expect them) go missing.

If you follow the frames you notice drips falling to the right of the question mark on frames 106-109.

However on frame 110 onwards (I have attached 110, and 111) a whole load of them disappear - it almost looks like they are 'clipped' out. It doesn't look like they are moving so fast as to have been filtered that way?

Thanks

Blender 3.0 is in early development and is set to release on August 25, 2021. At the time of this writing, we have not extensively tested Blender 3.0 and would consider this version not yet officially supported with the FLIP Fluids addon.

Official support will be added at a later date. Typically, the compatibility changes between Blender versions after Blender 2.80 are very small - if there even are any changes needed.

At the moment, there are no known issues when using Blender 3.0 with the FLIP Fluids addon version 1.0.9b or the latest experimental version. The Blender 3.0 Cycles-X branch also seems to work after some brief testing.

This issue thread will be used to track issues related to the FLIP Fluids addon and Blender Version 3.0.

Is there a plan to add a control to the system to influence the flow of fluids? I would think that a mesh-based tool might provide the most capability and flexibility. Something similar to Blender's current control settings might be a good starting point:

https://docs.blender.org/manual/en/dev/physics/fluid/types/control.html

Physics force fields might be another option or an additional option. This feature would open up a LOT of different special effects. Think of all of the water-bending we could do!

Blender 3.5 is set to release on March 15, 2023 and at this moment it is too early for us to begin extensively testing this version. We will start looking further into official Blender 3.5 support shortly after Blender 3.4 releases on December 7, 2022.

Blender 3.5 Release Notes

At this moment, there are no known compatibility issues between FLIP Fluids 1.5.0 and the latest Blender 3.5 Alpha (November 14, 03:47:02, 5fe146e505d4)

This issue thread was created to update you with a solution to a recent issue that has been causing frequent Blender crashes when running simulations with the FLIP Fluids Addon. This issue is relevant to artists that run systems containing NVIDIA GeForce RTX series video cards. In this post we will detail the issue and the current solution to this problem.

The fix for this issue is to update your NVIDIA GeForce RTX drivers to the "Studio Driver" version: https://www.nvidia.com/en-us/geforce/drivers/

Issue Symptoms and Patterns

• Frequent baking crashes closing Blender, typically within a few frames of beginning or resuming a simulation.
• Issue began appearing in October 2022 or early November 2022.
• System containing a NVIDIA GeForce RTX series video card.
• Issue occurs on all versions of Blender and the FLIP Fluids addon.
• Issue occurs in all Blend files: older files, newly created files, example files.

Issue Summary

Beginning in early November, we were made aware of an issue where baking a simulation using the FLIP Fluids addon was resulting in frequent Blender crashes. Over the past few days we had received a large number of reports of this issue. While troubleshooting the problem and gathering feedback, it was found that this issue was not related to updating to a newer version of the addon or Blender, but was being caused by a change external to Blender. This change suddenly began causing crashes across all version of Blender and the FLIP Fluids addon.

After troubleshooting, it has been found that this issue was being caused by a recent NVIDIA GeForce RTX driver update. Specifically, the "Game Ready Driver" version was determined to be the cause of the issue. This issue was causing an interaction between the addon and the Blender UI/Viewport that would trigger a crash - typically within a few frames after beginning a simulation.

Issue Solution

The current solution to this issue is to update your NVIDIA GeForce RTX drivers to the "Studio Driver" version which is typically more stable for content creation software. You will be able to download the latest NVIDIA drivers and specify the "Studio Driver" download type in the manual driver search here: https://www.nvidia.com/en-us/geforce/drivers/

How can I check which driver version I have installed?

Refer to NVIDIA Customer Help: Is there any way to determine whether the installed driver is a NVIDIA Studio Driver or Game Ready Driver?

Issue Workaround

If you are unable to update to the NVIDIA Studio Drivers, a workaround is to bake the simulation from the command line. The FLIP Fluids addon contains a tool to automatically launch a command line baking process in the FLIP Fluids sidebar menu (See Documentation).

If you are affected by this issue and this solution does not fix the problem, or if you have any questions at all, please reach out to us here or by sending us an email at [email protected].

This issue thread my be used to discuss the issue or to report more information/findings about the issue. We will be leaving this issue open for some time to increase visibility of this issue.

We apologize for the inconvenience that this issue has caused. Thank you for your patience and for supporting our FLIP Fluids addon.

- The FLIP Fluids Addon Development Team

Currently, when trying to use flip fluids and have the inflow settings run with drivers, the inflow settings refuse to notice the derived values. It also does not react to scaling drivers of the inflow object, treating the inflow as if it was the same scale as when the bake started.

It seems flip takes its values before the driver sets the final values? Order of operation issue, perhaps?

Blender 3.4 is set to release on December 7, 2022 and at this moment it is too early for us to begin extensively testing this version. We will start looking further into official Blender 3.4 support shortly after Blender 3.3 releases on September 7, 2022.

Blender 3.4 Release Notes

so ive been scratching my head here, and maybe i missed something but when i try to render a frame (i tested a two frame animation as well) and have my particles visible in the render, the only way i can get them to show up, is if i have them viewable in the viewport first.

so i need to disable "hide particles" in each of the systems, change the dispaly mode to final , and then reolad the frame, and only then when i render are the particles viewable..

i can confirm it does work with the command line render. but it would be nice to be able to use the internal renderer as well...and for still frames...maybe we can get a command line render for jus the frame...

im on blender 3.1, ff 1.4.0 and using a modified version of the waterfall a1 template.

thanks

Hello FlipFluids developers,

I noticed some minor visual bugs in my simulations and haven't really found a good way to avoit it. The fluid mesh generates some weird carvings/bumps near the domain floor and sometimes on the domain walls giving the fluid mesh in my final renders a weird result. As result there are some weird out of place reflections/refractions on the fluid facing the scene's floor because of these weird bumps in the mesh. (I usually use the FF volumetric ocean material or own materials with glass and volume...) Even when the simulations is not chaotic and there isn't much movement in the water the bug still occurs and the mesh starts to generate these sometimes noisy and annoying bumps on the floor and sides.

I tried increasing the fluid particle scale which lead to a little less bums but it created very blobbly and big fluid splashes. Increasing the simulation resolution makes the bumps more detailed but doesn't really get rid of it... I went up to 250 (my PC can't handle more) and still didn't get rid of the bumps.

Would be cool if there is a better method to avoid this visual bugs or maybe a patch in future updates.

Sincerely, Gluttonium

System Information

Blender Version: 3.0.0, master, 2021-12-02 18:35, f1cca3055776 Addon Version: A FLIP Fluid Simulation Tool for Blender (v1.2.1 Stable 03-DEC-2021) OS: Windows-10-10.0.19044-SP0 GPU: NVIDIA GeForce GTX 1050 2GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79 CPU: Intel(R) Core(TM) i5-8400 CPU 6 cores @ 2.80GHz RAM: (1(2) KINGSTON ValueRam KVR26N19S6 8 GB DDR4 2666MHz (not pre-installed, ordered+installed Dec. 2021) (2/2) 8GB DDR4 2666MHz ECC Unbuffered DIMM CL19 1Rx8 1.2V (looks pretty much like the one that's pre-installed, from 2018)

Attachments (pictures taken from below the mesh)

https://user-images.githubusercontent.com/98273272/155844426-9e83e568-1086-4126-bafb-caef46c50f31.mp4