Skip to content
Implementation of the i3D2018 paper "A Narrow-Range Filter for Screen-Space Fluid Rendering".
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Binary
Icons
Screenshots
Shaders
Source
Textures
.gitignore
FluidRendering.licenseheader
FluidRendering.pro
PlayList.txt
README.md
Resources.qrc
config.ini

README.md

A screenshot of the program A screenshot of the program A screenshot of the program
A screenshot of the program A screenshot of the program A screenshot of the program

This is implementation of my i3D2018 paper "A Narrow-Range Filter for Screen-Space Fluid Rendering". It is not the one that used in my paper but has been written from scratch for demonstration purpose and depends heavily on many external libraries, especially Banana. Users should not expect to compile it by themselves but instead please download and run the provided binary (Windows x64) over the provided datasets.

Download

Brief Usage

Firstly, one need to download and extract the provided datasets. For loading data, there are two ways:

  • Modify the file "PlayList.txt" to the correct paths of the extracted data folders. Then just click into the corresponding line on the SimulationList window.
  • From the main window, click the open icon of the "Data Path" box at the lower left corner and select a data folder.

Then, using program for rendering particle data is very straighforward.

Textures

Skybox textures and floor textures are loaded from disk automatically at launching time. Users can modify textures to their own in the Textures folder. Note that each skybox texture needs to be put in a separate subfolder while all floor textures are put in the same folder.

Data Format

Users can generate their own dataset similar to the provided one. Each dataset is a folder which has the following structure:

viz_info.txt
FluidFrame
...frame.%4d.pos
...frame.%4d.ani
SolidFrame
...frame.%4d.pos

viz_info.txt file contains simulation (number of particles, particle radius etc) and rendering information (light position, camera position etc), which can be inferred easily from the existing examples.

FluidFrame/frame.%4d.pos files contain particle positions, which have the following format:

Bytes 0-3(unsigned int): number of particles of the current frame
Bytes 4-7(float): particle radius
Next (4 x 3 x numParticles) bytes: array of particle positions

FluidFrame/frame.%4d.ani files contain particle anisotropic kernels, generated using the algorithm in the paper "Reconstructing Surfaces of Particle-Based Fluids Using Anisotropic Kernels". These files are optional, and have the following format:

Bytes 0-3(unsigned int): number of particles of the current frame
Next (4 x 9 x numParticles) bytes: array of 3x3 matrices (anisotropic kernels)

SolidFrame/frame.%4d.pos files contain triangle mesh objects in the following format:

BYTE 0-3(unsigned int): number of meshes
For each mesh i in numMeshes:
    Next 4 bytes(unsigned int): number of vertices of mesh[i]
    Next (4 x 3 x numVerticesOfMesh[i]) bytes: array of vertex positions of mesh[i]
    Next (4 x 3 x numVerticesOfMesh[i]) bytes: array of vertex normals of mesh[i]

Happy coding!

You can’t perform that action at this time.