rlguy/Blender-FLIP-Fluids

inversed obstacles prevent inflows from emitting fluids

MrMage750 opened this issue · 3 comments

MrMage750 commented

System Information

Blender Version: 3.6:
FLIP Fluids Version:1.7.0
Operating System: Windows 11
CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.6 GHz
GFX: NVIDIA GeForce RTX 2060
RAM:16 GB

inflows won't emit fluid when an obstacle in the domain has "inverse" ticked

  1. create domain object
  2. create inflow
  3. create obstacle
  4. tick the "inverse" box in the obstacle's properties
  5. attempt to bake the simulation
  6. play simulation after partial or full bake

inflow emits fluid into inversed object, which should reduce the chance the fluids ignores the obstacle (I think)

the inflow won't emit fluid at all, regardless of domain resolution/inflow size, unless the "inverse" box is unticked

MrMage750 commented

as a side note, I decided to buy the addon anyways since the demo worked beautifully, minus the watermark, and that building it for free requires way more knowledge on coding than I currently have. I know it's possible to achieve the result I'm desiring, but I know too little about how obstacles work to get this desired result

rlguy commented

Hi, thanks for the report!

My apologies for the late response. I have been away on holidays, but should be able to get back to you later this week. Our current support status and expected response times will be updated here: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Technical-Support-Guidelines#support-and-development-hours

Would you be able to attach or link to a Blend file so that we can take a look for any issues?

Documentation on obstacle object requirements can be found here: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Obstacle-Object-Settings#obstacle-object-requirements

And how Inverse type obstacles work here: https://github.com/rlguy/Blender-FLIP-Fluids/wiki/Obstacle-Inverse-Workflow

rlguy commented

Closing this issue due to inactivity. From the description, it sounds like the the 'Inverse' feature is working as expected. If you think this is an error, p[lease attach a Blend file that reproduces the problem and we can re-open the issue and look further into this.