Ls_Fluid (Compatible with IFFS 2017.0.0 and up)

Download this shader

Fluid - a 2D fluid simulation. Make sure bit depth is 16-bit fp!

The vector input can be fed motion vectors to affect the fluid, and the obstacle input can be fed with a matte for areas which the fluid should move around.

The matte output works well as the Displacement input to BumpDisplace, or as a displacement map in Action. The RGB output can be the front input image mapped onto the surface of the fluid, or various vector or UV outputs.

The simulation is based on Jos Stam’s ‘Stable Fluids’, 1999. The process also owes a debt to Theodor Groeneboom’s Sprut gizmo for Nuke.

Remember to disable Adaptive Degradation on this node if viewing downstream!

Demo: https://www.youtube.com/watch?v=N6nIwt2BcMM

lewis _at_ lewissaunders.com


Version notes

UI tweaks


Older versions that shader

12th of September 2022

Download

UI tweaks

23th of April 2016

Download
  • demo links

23th of April 2016

Download
  • Warn about 2017

23th of April 2016

Download
  • accum stuff for 2017 beta
  • Ls_Stickon 2-pass nice stuff
  • bit more fluids, still bruk
  • made fluid mega-simple for debugging
  • added premult option, and refuse to comp if output is UV map
  • going back to fluids wip now single frame input bug is identified
  • fluidy fruidy frings
  • workable fluids, a lil
  • flock beginings
  • stickon bit-depth and socket colours
  • more flocky
  • airglow flow blow
  • terrible. super slow, corruption, crashes GPU, abandoning
  • no
  • progress being made
  • flock speed, comments, icon
  • p-map output, obstacle input
  • jets, sinks, noise
  • spaces
  • ewa
  • supersampled UV-mapping, stuff
  • p much there
  • axis icons
  • channel names
  • stupid dashes. also float32 errwhere
  • bit depth warnings
  • comm
  • seed
  • flmstrip… this border maths is the worst
  • something funny when rows <> cols
  • good enough
  • icon, limits
  • Merge branch ‘2017yo’

Something wrong with this page or the download?

Contact the site custodians via email, if:

How to get help with this particular shader

Sadly, the custodians likely will not be able to explain to you how a shader works or debug its code, or fix it for you. That is the (volountary) role of the shader author.

If the shader does not work on your system or you have questions about it - read the shader description, and try to find the email address of the shader author. Contact them for any issues – letting them know whether you are on Mac or Linux, what version of IFFS you are running etc. will likely help. Be kind and respectful. If you can't get hold of the author - you can try asking in the Logik forum at logik.tv and ask whether anyone could help you debug a particular shader not working.