Uploaded February 2022 | Updated November 2026, 5 hours ago
How much can the FluidX3D OpenCL raytracer handle in real time? - As much as fits into GPU memory, 108 million voxels.
Real time raytracing of an oblique raindrop impact, 1920x1080 pixel, 1-4 rays per pixel.
FluidX3D is now built entirely on my open source OpenCL-Wrapper, reducing the entire code on the C++ side to about half. If you want to get into OpenCL yourself, look no further: github.com/ProjectPhysX/OpenCL-Wrapper
Raindrop simulations: doi.org/10.1186/s43591-021-00018-8
Volume-of-Fluid: doi.org/10.3390/computation10020021
Esoteric-Pull: doi.org/10.3390/computation10060092
FP32/FP16 mixed precision: researchgate.net/publication/362275548_Accuracy_and_performance_of_the_lattice_Boltzmann_method_with_64-bit_32-bit_and_customized_16-bit_number_formats
FluidX3D: doi.org/10.15495/EPub_UBT_00005400
This is a Volume-of-Fluid lattice Boltzmann method (LBM) simulation of a 7 mm diameter terminal velocity (9.55 m/s) raindrop impact (D3Q19 SRT) at 20° inclination. Velocity, density and fluid mass are solved at 108 Million lattice points (504x504x428). The simulation required 12 GB video memory.
For reproducibility: The dimensionless numbers for this setup are Re = 63618, We = 8864, Fr = 36.44, Ca = 0.1393, Bo = 6.674.
The simulation software used is FluidX3D, an OpenCL implementation of the lattice Boltzmann method. FluidX3D runs at peak hardware efficiency on the worlds fastest data-center GPUs (8799/5232 MLUPs/s on the Nvidia A100/V100 @ D3Q19 SRT FP32), on gaming GPUs and CPUs and it even runs my smartphone.
The rendering is done by FluidX3D as well, now with raytracing. Simulated light rays from the camera traverse the LBM lattice and check for intersections with the triangles that marching-cubes generates on-the-fly from the isovalues. Triangles never leave registers.
The 3D lattice that the LBM provides already is one of the ideal acceleration structures for raytracing. Any ray only has to check for possible intersections with iso-surface triangles contained within the traversed grid cells. This makes it - when the lattice is not too large - even run in real time on non-RTX GPUs.
I am the lead developer of FluidX3D. The implementation is detailed in my Master's thesis, which is freely available on ResearchGate:
researchgate.net/publication/349552856_High_Performance_Free_Surface_LBM_on_GPUs
The Volume-of-Fluid extension is detailed in this research paper:
mdpi.com/2079-3197/10/2/21
Timestamps:
00:00 intro
00:03 setup
00:08 simulation start
00:48 stereoscopic raytracing for left and right eye
01:00 showcasing refraction
02:52 outro
#FluidX3D #OpenCL #Raytracing #GPU #LBM
How much can the FluidX3D OpenCL raytracer handle in real time? - As much as fits into GPU memory, 108 million voxels.
Real time raytracing of an oblique raindrop impact, 1920x1080 pixel, 1-4 rays per pixel.
FluidX3D is now built entirely on my open source OpenCL-Wrapper, reducing the entire code on the C++ side to about half. If you want to get into OpenCL yourself, look no further: github.com/ProjectPhysX/OpenCL-Wrapper
Raindrop simulations: doi.org/10.1186/s43591-021-00018-8
Volume-of-Fluid: doi.org/10.3390/computation10020021
Esoteric-Pull: doi.org/10.3390/computation10060092
FP32/FP16 mixed precision: researchgate.net/publication/362275548_Accuracy_and_performance_of_the_lattice_Boltzmann_method_with_64-bit_32-bit_and_customized_16-bit_number_formats
FluidX3D: doi.org/10.15495/EPub_UBT_00005400
This is a Volume-of-Fluid lattice Boltzmann method (LBM) simulation of a 7 mm diameter terminal velocity (9.55 m/s) raindrop impact (D3Q19 SRT) at 20° inclination. Velocity, density and fluid mass are solved at 108 Million lattice points (504x504x428). The simulation required 12 GB video memory.
For reproducibility: The dimensionless numbers for this setup are Re = 63618, We = 8864, Fr = 36.44, Ca = 0.1393, Bo = 6.674.
The simulation software used is FluidX3D, an OpenCL implementation of the lattice Boltzmann method. FluidX3D runs at peak hardware efficiency on the worlds fastest data-center GPUs (8799/5232 MLUPs/s on the Nvidia A100/V100 @ D3Q19 SRT FP32), on gaming GPUs and CPUs and it even runs my smartphone.
The rendering is done by FluidX3D as well, now with raytracing. Simulated light rays from the camera traverse the LBM lattice and check for intersections with the triangles that marching-cubes generates on-the-fly from the isovalues. Triangles never leave registers.
The 3D lattice that the LBM provides already is one of the ideal acceleration structures for raytracing. Any ray only has to check for possible intersections with iso-surface triangles contained within the traversed grid cells. This makes it - when the lattice is not too large - even run in real time on non-RTX GPUs.
I am the lead developer of FluidX3D. The implementation is detailed in my Master's thesis, which is freely available on ResearchGate:
researchgate.net/publication/349552856_High_Performance_Free_Surface_LBM_on_GPUs
The Volume-of-Fluid extension is detailed in this research paper:
mdpi.com/2079-3197/10/2/21
Timestamps:
00:00 intro
00:03 setup
00:08 simulation start
00:48 stereoscopic raytracing for left and right eye
01:00 showcasing refraction
02:52 outro
#FluidX3D #OpenCL #Raytracing #GPU #LBM





![PhysX3D [GRAVITY SIMULATION] Active Galaxy on a notebook GPU
aparapi has really cranked up the capabilities of PhysX3D. Most of the n-body-calculation process is outsourced to the GPU which can handle the highly parallelizable task 7x faster than the CPU, so the CPU can focus more on the graphics.
The galaxy in this simulation contains 3k stars. My Nvidia GeForce GTX 960M calculates 58 RK4-steps per second.
More information at: http://www.projectphysx.de
Music: Huma-Huma - Nevada City PhysX3D [GRAVITY SIMULATION] Active Galaxy on a notebook GPU](https://i.ytimg.com/vi/LDz4lRK8nNg/mqdefault.jpg)



![PhysX3D [GRAVITY SIMULATION] Stereoscopic 3D Graphics Preview
Ich habe in meine hocheffiziente Java-Grafikausgabe stereoskopisches 3D Rendering integriert. Jeder Frame wird dabei aus zwei leicht unterschiedlichen Kameraperspektiven berechnet, was in Sachen Framerate etwa doppelt so lange dauert, wie das Rendern eines normalen 2D -Frames. Beide Bilder werden nebeneinander auf dem Display ausgegeben. Der Effekt ist wirklich atemberaubend, gerade eben bei so dreidimensionalen Dingen, wie den Umlaufbahnen von Planeten, Monden und Asteroiden. Und weil ich alles selbst programmiert habe, kann ich einstellen, wie weit die Kameras auseinander sind, also wie stark der 3D-Effekt ist, und wie weit die beiden Frames von einander verschoben sind, d.h. wie weit das Bild aus der Displayebene herauskommt oder wie tief es im Display erscheint.
Mehr Informationen auf: http://www.projectphysx.de
Song: Disfigure - Blank [NCS Release] PhysX3D [GRAVITY SIMULATION] Stereoscopic 3D Graphics Preview](https://i.ytimg.com/vi/N9gWOj8UVTU/mqdefault.jpg)
