rlguy / blender-flip-fluids Goto Github PK

test_case_viscous_net100.zip
test_case_cascading_water_feature100.zip
test_case_cascading_water_feature200.zip
test_case_fluid_in_an_invisible_box100.zip
test_case_fluid_in_an_invisible_box200.zip
test_case_lighthouse125.zip
test_case_viscous_net65.zip

test_case_fluid_in_an_invisible_box100.zip

Will try a higher resolution next...

I have finished the test scenes. Here are the results.
Thank you,

test_case_fluid_in_an_invisible_box100.zip
test_case_cascading_water_feature100.zip
test_case_lighthouse125.zip
test_case_viscous_net65.zip

test_case_cascading_water_feature200.zip

Here is a first test, it went okay at 100 resolution.

test_case_cascading_water_feature100.zip

I am now simulating the highest resolution tests, but it might take a while before I can post them as they take a very long time to simulate, CPU load was low on the 100 resolution test, but it gets over 90% at time with the one i am running at the moment at 400 resolution, as it goes, it should take over 12 hours to simulate!

3 more tests, all ran without problems and I was able to playback the cached data.

test_case_fluid_in_an_invisible_box100.zip
test_case_lighthouse125.zip
test_case_viscous_net65.zip

I noticed that the GPU is not used during calculation (1-2%), Houdini fluids calculation went a lot faster when they made use of OpenGL, I mean quite a bit faster, so I would suggest to look into GPU support for the add-on, just a thought!

This error only applies to the Test Suite addon.

1. Set the export test case directory to an absolute path
2. Click the Export Test Case button

This error is displayed:

Workaround

Until this is fixed, don't use absolute paths when exporting a test case.

This bug has been fixed and will be included in the next Test Suite addon version (0.1.2t).

Hi,

Missing script file bl_flip_fluids_test_suite warning when installing the non-test version of FLIP fluids right now

• CPU: Intel i7 7700
• RAM: 32 GB
• GPU: GTX 1070, 8 GB
• OS: Windows 8.1
• Blender Version: 2.79
• Addon Version: 0.1.1

A banding effect can be seen in the fluid particles when a thin layer of fluid is sliding down a gradual sloping obstacle.

Example .blend file:
https://www.dropbox.com/s/a9om9oimpbiii0a/gradual_slope_banding_artifacts.blend?dl=0

Note: this issue is about simulation banding artifacts rather than mesh banding artifacts. Simulation banding artifacts cause particles to group and align to the grid. A fix for mesh banding artifacts can be found here: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Scene-Troubleshooting#mesh-banding-artifacts-against-curved-obstacles

Without documentation, it is unclear which domain settings will take effect post-bake and which settings must be applied before baking. Documentation should be added to clarify this.

In general:

Must be applied pre-bake

• FLIP Fluid Simulation settings
• FLIP Fluid Surface settings
• FLIP Fluid Whitewater settings
• FLIP Fluid World settings
• FLIP Fluid Advanced settings
• FLIP Fluid Debug settings (fluid particle debugging, obstacle debugging)

Can be applied post-bake

• FLIP Fluid Display Settings
• FLIP Fluid Presets settings
• FLIP Fluid Materials settings
• FLIP Fluid Debug settings (display grid, display console output)

Hi,

Changing the viewport display options seems to have no effect between final/preview/none

Neither do they seem to make a difference on different elements - for example fluid_surface.

Have only run 100 resolution test so far.

Come to think of it - what does is the difference between the display settings on the domain and the different elements (i.e. surface) mean?

Thanks

Hi,

The title says it all really.

Just get a rendered cube for the domain when rendering in the viewport.

Thanks

test_case_fluid_in_an_invisible_box100.zip
test_case_cascading_water_feature100.zip
test_case_viscous_net65.zip

test_case_cascading_water_feature200.zip

An error occurred when trying to export the test case data (see attached image) so I manually compressed and renamed the directory. Hopefully everything is there.

Thanks,
Bruce

test_case_viscous_net65.zip

Hi,

Firstly should say I am really loving playing with this - it just so happens I have the week off work which has enabled me plenty of playtime! Sorry I keep sending so many reports!

This could simply be how the solver works but in simple example below (images) where
Domain dimensions are: 8 X 8 X 8
And Fluid is 8 X 8 X 2
With as you can see an initial Z displacement so the water drops as block

The water lands as a solid rigid block and has very little motion when it reaches the bottom.

However, if I reduce the size of my water block to 7 X 7 X 2 - it works as expected. See other image below.

Thanks

Rigid.... 8 X 8 X 2

Working 7 X 7 X 2

1. Click on the 'Export Test Case' operator
2. Fill out the test case form
3. Click 'OK'

This error popup message is displayed:

test_case_lighthouse125.zip

I could not see that any of my two GPUs was utilized.
But everything seemed to run smoothly.

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.

I believe I've installed flip correctly. Once I've loaded up any of the test scenes, I get a windows error:

Here's what I'm getting from the system console:
Traceback (most recent call last): File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\bake.py", line 1149, in bake fluidsim = FluidSimulation(init_data.isize, init_data.jsize, init_data.ksize, init_data.dx) File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\fluidsimulation.py", line 65, in __init__ self._init_from_dimensions(isize, jsize, ksize, dx) File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\method_decorators.py", line 68, in check_values return func(self, *args) File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\fluidsimulation.py", line 81, in _init_from_dimensions libfunc = lib.FluidSimulation_new_from_dimensions File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\pyfluid.py", line 39, in __getattr__ self._lib = self._load_library("pyfluid") File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\pyfluid.py", line 57, in _load_library raise LibraryLoadError("Unable to load library: " + name) bl_flip_fluids_test_suite.pyfluid.pyfluid.LibraryLoadError: 'Unable to load library: pyfluid' Exception ignored in: <bound method FluidSimulation.__del__ of <bl_flip_fluids_test_suite.pyfluid.fluidsimulation.FluidSimulation object at 0x0000023C30FDF080>> Traceback (most recent call last): File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\fluidsimulation.py", line 88, in __del__ libfunc = lib.FluidSimulation_destroy File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\pyfluid.py", line 39, in __getattr__ self._lib = self._load_library("pyfluid") File "C:\Users\Ryan\AppData\Roaming\Blender Foundation\Blender\2.78\scripts\addons\bl_flip_fluids_test_suite\pyfluid\pyfluid.py", line 57, in _load_library raise LibraryLoadError("Unable to load library: " + name) bl_flip_fluids_test_suite.pyfluid.pyfluid.LibraryLoadError: 'Unable to load library: pyfluid'

test_case_cascading_water_feature100.zip
test_case_cascading_water_feature200.zip

test_case_fluid_in_an_invisible_box100.zip
test_case_lighthouse125.zip
test_case_viscous_net65.zip

These are the test cases I have done at the moment. The jpg image is a screenshot of the error I got while I was baking the 2nd test, but I hit the "resume" button and it finished succesfully. Maybe I will make some more with higher resolutions tonight, when I can leave the computer baking a few hours, while I sleep :)
I hope this is helpfull. Let me know what else I can do for you. I really like your software. Thank you for this chance.

Fernando Montero

Hi! I read that "Simulations can be baked to Alembic caches for export to other DCC software, although Guy says that this is currently slow for large caches.", I wanted to try but I do not succeed, just get the first and only one frame and not the animation (Cache)?

/Niklas

test_case_viscous_net65.zip

I ran the viscous_net succesfully on my laptop. Looking forward to trying out the more advanced tool, when this gets approved hopefully. I didn't experience other issues, than if I wanted to cache my results in a dropbox folder it would make an error since a sharing violation would occur. The simple fix was to store on harddrive instead.

test_case_cascading_water_feature200.zip

test_case_cascading_water_feature100.zip

test_case_cascading_water_feature100.zip

CPU usage was around ~30%, GPU usage was minimal.

I run the cascading water test scene here at 100 and 200 resolution and it finished successfully.
I'm running the same scene at 300 resolution now to see how it goes.
My processor is only a few seconds behind the original processor that appears in the tooltip from the resolution button.

test_case_cascading_water_feature100.zip
test_case_cascading_water_feature200.zip

Hi,

If I translate/rotate the domain origin and then apply the transform (Ctrl A -> then choose rotation or translate) those changes are not reflected properly in FLIP Fluid sim.

Thanks

Hey, I ran the fluid_in_an_invisible_box.blend test case at 100 resolution and I think it ran okay. Here are the results:

test_case_fluid_in_an_invisible_box100.zip

test_case_cascading_water_feature200.zip

Changing this option does not have any influence on how the fluid is displayed.

Only when I switch to Final here I can see how the high res fluid actually looks

Results from the first test case:

test_case_viscous_net65.zip

test_case_cascading_water_feature400.zip
test_case_cascading_water_feature100.zip

Test OK !
All is good for me.

test_case_cascading_water_feature200.zip
test_case_fluid_in_an_invisible_box100.zip

Didn't really have time to do a big one, but uh, oh well. Seems pretty good so far!

Hi,

This is probably very subjective - but was wondering if the option to enable the fluid whitewater should be higher up in the UI than the display settings for it.

As the option to use white water controls whether display setting is accessible (i.e. greyed out), it seems to be more intuitive (to me) to have that option first.

Just a thought.

Problem

When changing the viewport surface/whitewater display settings in the FLIP Fluid Display Settings panel, no effect is immediately seen. The effect only takes place after triggering a frame reload which can be done by changing the frame or re-entering the frame number in the timeline.

The reason why a frame reload is not automatically triggered when changing display settings is because for large meshes, a reload could take a second or two to load into the scene. This could cause the interface to 'hang' and feel unresponsive. For some users, automatic frame reloading may be desirable.

Solution

Add an option to the FLIP Fluids Helper panel (located in the toolbox) to allow the user to set whether they would like automatic frame reloading. Unchecked by default.

Comment and let us know if this is a feature that you would like! Let us know if you have any suggestions. If enough people would like this option added, we can add this functionality to the interface.

Problem

The simulator doesn't have a 'smart' method of selecting which GPU to use, it just picks the first GPU from a list. This can cause the simulator to choose the less powerful GPU, or even an integrated graphics chip which will slow down simulation baking.

Solution

1. Add an interface element to the Addon Preferences menu that allows the user to select which GPU they want the simulator to use.
2. Use a smarter method to try and detect the more powerful GPU and use that as the default selection

Workaround
Note: This workaround only applies to the FLIP Fluids Beta addon, not the Test Suite addon

If the addon is selecting the wrong GPU, try disabling GPU features until this issue is fixed. Simulations may run faster using your CPU.

test_case_cascading_water_feature100.zip

Im busy at the moment so could only do a short test but worked at first try, pretty impressive!

Hi. Did some of the tests, mostly low resolution, on my desktop computer and I think without any problems! I'll try to do some more of those with higher resolution during the evening!

Desktop computer results:
test_case_lighthouse125.zip
test_case_viscous_net65.zip
test_case_cascading_water_feature100.zip
test_case_fluid_in_an_invisible_box100.zip
test_case_fluid_in_an_invisible_box200.zip

You also got details on my laptop, when I run the tests on that machine should I just put the exported "results" here in the same thread too?

/Niklas

Hi, thank you for inviting me as a beta tester.

I have installed the addon, bl_flip_fluids_test_suite-x64_v0.1.1t.zip, without any error message.
And I confirmed that the Flip fluid button in the Physics.
After clicking the button, only header come up. But there is no contents.

The some error messages are caused by other addon, I think.

test_case_fluid_in_an_invisible_box100.zip
Was able to get it up and running and blazed through the first test. I'm loving how it looks.

I still get error in system console:
"Unable to load library: pyfluid".
I installed addon correctly.
And here is windows which is opened after i click "Run Test Case":

This is at 100. I am going to bake 200 through the night as I have some work to do.
Minus a few particles going through the object (which compared to the build in fluid means that this one beta is already flawless ha!) Everything went well.
I played back with 8fps even while baking to see if I could and it worked well.

test_case_cascading_water_feature100.zip

Hi,

Been trying to play with the FLIP Fluid Surface settings. However the two parameters I have been changing - subdivisions and smoothing factor - seem to have no effect.

Thanks

test_case_fluid_in_an_invisible_box100.zip

I was using my PC for some other tasks while this ran so the timing/performance may be impacted.

test_case_viscous_net65.zip

I understand that fluid material depends on the domain setting.
But if user want to use two type of materials to set to different fluid surface respectively which come from different source, is it or will it be possible?
See image below, for example,
A left fluid come from "fluid" source. A right fluid come from inflow source. I want to set red material to the left, blue material to the right.

test_case_cascading_water_feature100.zip
test_case_fluid_in_an_invisible_box100.zip
test_case_lighthouse125.zip
test_case_viscous_net65.zip

Hi,

This is really simple - however the download contains a zip withing a zip.

You have to unzip the first file and install the inner zip (if that makes sense) it's not a problem - just not 100% clear.

Thanks

Rob

Here are all the test cases I have completed.
Every simulation ran smoothly, though at only around 10-17% CPU and maximum of ~3% GPU load for each of them.

test_case_cascading_water_feature200.zip
test_case_fluid_in_an_invisible_box100.zip
test_case_lighthouse125.zip
test_case_viscous_net100.zip
test_case_cascading_water_feature100.zip

An icon to display a preset info is now "question" mark.
This is my opinion. I think that it is not good, because I think that it is for showing some help.
I think that it is better the icon is showing " ! " mark as blender info editor's icon.