RealTimeFluidRendering - GitLite

KO | EN

gitlite — search

#javascript #python #react #ai #go #deep-learning #linux #macos #awesome #kubernetes #pytorch #security #ios #openai

RealTimeFluidRendering

(★ 110)

Implementation of the i3D2018 paper "A Narrow-Range Filter for Screen-Space Fluid Rendering".

파일 탐색기

최종 버전 다운로드 (.zip)

- FluidRenderingWin64.zip
- app.icns
- app.png
- open.png
- refresh.png
- save.png
- Screenshot1.png
- Screenshot2.png
- Screenshot3.png
- Screenshot4.png
- Screenshot5.png
- Screenshot6.png
- composition-pass.fs.glsl
- depth-pass.fs.glsl
- depth-pass.vs.glsl
- filter-bigaussian.fs.glsl
- filter-curvature-flow.fs.glsl
- filter-narrow-range.fs.glsl
- filter-plane-fitting.fs.glsl
- fluid-shadow.fs.glsl
- fluid-shadow.vs.glsl
- mesh-depth.fs.glsl
- mesh-depth.vs.glsl
- mesh-shadow.fs.glsl
- mesh-shadow.vs.glsl
- mesh.fs.glsl
- mesh.vs.glsl
- normal-pass.fs.glsl
- particle.fs.glsl
- particle.vs.glsl
- thickness-filter.fs.glsl
- thickness-pass.fs.glsl
- thickness-pass.vs.glsl
- thickness-shadow.fs.glsl
- thickness-shadow.vs.glsl
- Common.h
- Controller.cpp
- Controller.h
- DataManager.cpp
- DataManager.h
- DataReader.cpp
- DataReader.h
- FRRenderObjects.cpp
- FRRenderObjects.h
- Main.cpp
- MainWindow.cpp
- MainWindow.h
- RenderWidget.cpp
- RenderWidget.h
- - blue_marble.png
  - marble.jpg
  - stone2.jpg
  - stone3.jpg
  - white.jpg
  - wood.jpg
.gitignore
config.ini
FluidRendering.licenseheader
FluidRendering.pro
PlayList.txt
README.md
Resources.qrc

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<p align="center">
<table style="border-collapse: collapse; border: none; width: 80%; margin-left:10%; margin-right:10%">
<tr>
<td><img src="Screenshots/Screenshot1.png" alt="A screenshot of the program" style="width: 95%;"/></td>
<td><img src="Screenshots/Screenshot2.png" alt="A screenshot of the program" style="width: 95%;"/></td>
<td><img src="Screenshots/Screenshot3.png" alt="A screenshot of the program" style="width: 95%;"/></td>
</tr>
<tr>
<td><img src="Screenshots/Screenshot4.png" alt="A screenshot of the program" style="width: 95%;"/></td>
<td><img src="Screenshots/Screenshot5.png" alt="A screenshot of the program" style="width: 95%;"/></td>
<td><img src="Screenshots/Screenshot6.png" alt="A screenshot of the program" style="width: 95%;"/></td>
</tr>
</table>
</p>

This is implementation of my i3D2018 paper "[A Narrow-Range Filter for Screen-Space Fluid Rendering](https://ttnghia.github.io/posts/narrow-range-filter/)". 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](https://github.com/ttnghia/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

* Windows binary and dataset: [https://github.com/ttnghia/RealTimeFluidRendering/releases](https://github.com/ttnghia/RealTimeFluidRendering/releases)

### 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](https://dl.acm.org/citation.cfm?id=2421641)". 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!