How Game-Engine Water Rendering Is Redefining Architectural Visualization

An architect stands before a screen showing a water feature — a plaza fountain, a reflecting pool beside a glass facade, a waterfall cascading down a stone wall. In the world of architectural visualization, the client doesn’t ask about Navier-Stokes equations or ray-tracing algorithms. They ask: “Will it look real?” That simple question hides a decades-old dilemma: real-time water simulation has always been a trade-off between speed and truth. Screen-space techniques inherited from video games deliver 60 frames per second but break when you look from the edge of the pool. Ray tracing gives physically correct results but was, until recently, too slow for interactive walkthroughs. Today, with RTX hardware and hybrid approaches, we’re at an inflection point that changes how we design and present spatial water in architecture.
Water That Only Breaks at the Screen Edge
Screen-space techniques work by a clever but limited logic: render the scene first, then project it onto the water surface via UV coordinates perturbed by normal maps. Refraction is calculated by a simple pixel offset based on surface angle. This approach amazed players in “Crysis” (2007) and remains the backbone of engines like Unreal and Unity. But the fundamental flaw appears when an architect tries to show a pool reflecting a towering building — the tower simply doesn’t exist in screen-space memory because it’s outside the frame. The result: truncated reflections, fake refraction, realism that collapses at the first camera move. The two-phase method (broad phase for underwater objects, narrow phase for screen-space correction) proposed by Iwasaki, Dobashi, and Nishita (2001) and refined by Liu, Han, and Fei (2020) reduces error but doesn’t eliminate it. An architect relying solely on these techniques delivers water that looks real only from specific angles — and in architectural visualization, that means an unfaithful presentation.
Ray Tracing: Physical Truth at a Steep Price
On the other side, ray tracing simulates actual photon paths: a ray hits the water surface, refracts per Snell’s law, continues through the water volume, may strike the pool bottom or a submerged object, then exits toward the camera. The result is physically correct — multiple reflections, caustics on walls, volumetric light scattering in water. Kinakh (2016) showed GPU ray tracing produces ground-truth results, but at 55 fps versus 362 fps for the two-phase method. In games, 55 fps is acceptable. In interactive architectural walkthroughs where the client controls the camera freely, any stutter breaks immersion. Recent studies by Macedo, Serpa, and Rodrigues (2018), Walewski, Gałaj, and Szajerman (2019), and Andrade, Sabino, Clua, and Pagliosa (2014) all converge on one path: hybrid. Use screen-space for the majority, invoke ray tracing only for pixels where approximations fail — object edges, multiple reflections, regions where screen-space depth is missing.
Caustics: The Fingerprint That Doesn’t Lie
There’s one detail that separates “water that looks like water” from “water that convinces the engineer”: caustics. Those dancing light patterns on pool walls and floors aren’t decoration — they’re water’s physical signature. Iwasaki, Dobashi, and Nishita (2003), followed by Podee, Max, Iwasaki, and Dobashi (2021), developed methods to render caustics via illumination volumes and sample planes, avoiding per-photon tracing. These techniques reached modern game engines as “Screen Space Caustics” and “Ray Traced Caustics.” The architectural difference is fundamental: a public plaza fountain without caustics reads as a static blue mirror. With caustics, the ground dances with light, walls catch the rhythm of waves, the space breathes. An architect who ignores caustics isn’t saving time — they’re losing material truth.
From Particles to Surfaces: When Water Becomes Volume, Not Skin
Most architectural visualizations treat water as a surface — a flat plane animated with Gerstner waves or fractal noise, as in Kinakh’s 2020 study. But real water is volume: spray, bubbles, currents, interaction with solid bodies. Chan, Ke, and Im (2017) coupled smoothed particle hydrodynamics (SPH) with finite element method (FEM) for deformable bodies, rendering multi-pass screen-space refraction (up to four refraction bounces). This means architects can now simulate a waterfall striking rocks and throwing spray, or a fountain interacting with real wind, and view the result in real time. The line between “simulation” and “visualization” dissolves. The designer no longer chooses water’s shape — they define its physics (viscosity, surface tension, wind velocity) and let the engine compute the form. This shifts the architect’s role from “form designer” to “behavior designer.”
The Client Who Walks Inside Water
The end goal of architectural visualization isn’t an image — it’s an experience. When a client puts on a VR headset and walks around the pool, then leans down to see their reflection in the water, then reaches out to touch the virtual surface — that’s when every technique gets tested at once. Temporal and spatial anti-aliasing for reflections on waves (Podee et al. 2021) isn’t academic luxury — it’s the difference between a client who feels nausea and one who feels awe. Water in architecture isn’t a decorative element; it’s a spatial material that defines light, sound, humidity, movement. The techniques we’re borrowing from games today — hybrid screen-space and ray tracing, computed caustics, particle-based fluids — don’t just improve “graphics.” They restore the architect’s ability to design spatial water as a spatial tool, not a backdrop. The next time a client asks for “realistic water,” the answer isn’t a prettier shader. The answer is choosing the technique that holds up when someone walks inside the water.
### ✦ ArchUp Editorial Insight
The research reviewed reveals that the shift from pure screen-space techniques to hybrid ray tracing isn’t merely a graphical upgrade — it’s a transformation in the design contract between architect and material. For decades, water in architectural visualization was a “skin” laid over geometry: an animated texture, a normal map, an approximate refraction. This skin sufficed for still renderings but collapses the moment the viewer moves freely, because screen-space doesn’t know what lies beyond the frame edge. Ray tracing, with its computational cost, forces the engine to “know” the entire space — geometry, materials, light sources — because every ray asks: what did I hit? That simple question restores water’s reality as a physical volume with depth, multi-bounce refraction, caustics dancing on walls, interaction with spray and bubbles. The architect adopting hybrid rendering today isn’t choosing “higher quality” — they’re choosing a material that withstands free scrutiny.
What strikes as counterintuitive is that research focused on “caustics” (Iwasaki et al. 2003, Podee et al. 2021) treats these light patterns as a performance optimization problem — how to render them fast — while in architecture they’re a “truth certificate.” The trained eye (and the untrained client’s eye) registers the absence of caustics instantly as an unconscious signal: “this isn’t real water.” Engines that ignore caustics or approximate them crudely produce water that “looks like water” in static images, but in VR walkthroughs reveals itself as a blue mirror. The paradox: techniques developed for games — where water is a gameplay backdrop — have become the standard of truth in architecture — where water is a spatial material.
The implications extend beyond shader selection. Particle-based water simulation (SPH-FEM coupling, Chan et al. 2017) moves the architect from “drawing water’s shape” to “designing water’s behavior.” The designer defines viscosity, surface tension, wind velocity, basin geometry — and the engine computes the resulting form. This means a public plaza fountain can be virtually tested: how does spray disperse at 20 km/h wind? Where do droplets land? Do benches get wet? Water becomes an environmental analysis tool, not a decorative element. Firms adopting this path (Unreal Engine 5 with Niagara, Unity with DOTS/ECS, Twinmotion with Lumen) offer architects a virtual hydraulics lab. Those who don’t design by intuition; those who do design by physics.
The question left hanging: are we witnessing “simulation democracy” where every architect owns a fluid lab, or “realism tyranny” where the perfect rendering becomes a substitute for lived experience? The client who walks in VR around a perfectly refracting, fully caustic, wind-responsive virtual pool — will they accept the real pond with its algae, evaporation, and unpredictable wind? The tools don’t lie, but the perfection they offer may be the most dangerous lie. The conscious architect uses these tools not to sell fantasy, but to understand how water truly behaves — then designs for reality with its mess and truth.
**References:**
1. Iwasaki, Keiichi, Dobashi, Yoshinori, Nishita, Tomoyuki. “Efficient rendering of optical effects within water using graphics hardware.” Proceedings Ninth Pacific Conference on Computer Graphics and Applications, 2001.
2. Kinakh, Roman. “Realistic water modeling and GPU-based rendering.” IEEE 15th International Conference on Advanced Trends in Radioelectronics, Telecommunications and Computer Engineering (TCSET), 2020.
3. Liu, Hao, Han, Hong, Fei, Gang. “Two-phase real-time rendering method for realistic water refraction.” Virtual Reality & Intelligent Hardware, 2020.
4. Imai, Takashi, Kanamori, Yoshinori, Mitani, Jun. “Real-time screen-space liquid rendering with complex refractions.” Computer Animation and Virtual Worlds, 2016.
5. Chan, Ka, Ke, Wei, Im, Sung. “Particle–mesh coupling in the interaction of fluid and deformable bodies with screen space refraction rendering.” Computer Animation and Virtual Worlds, 2017.
6. Iwasaki, Keiichi, Dobashi, Yoshinori, Nishita, Tomoyuki. “A Fast Rendering Method for Refractive and Reflective Caustics Due to Water Surfaces.” Computer Graphics Forum, 2003.
7. Macedo, Danilo D., Serpa, Yuri R., Rodrigues, Marcelo A. “Fast and Realistic Reflections Using Screen Space and GPU Ray Tracing—A Case Study on Rigid and Deformable Body Simulations.” Computers in Entertainment, 2018.
8. Walewski, Pawel, Gałaj, Tomasz, Szajerman, Dariusz. “Heuristic based real-time hybrid rendering with the use of rasterization and ray tracing method.” Open Physics, 2019.
9. Andrade, Paulo, Sabino, Tiago, Clua, Esteban, Pagliosa, Priscila. “Ray-Traced Reflections in Real-Time Using Heuristic Based Hybrid Rendering.” 2014 Brazilian Symposium on Computer Games and Digital Entertainment, 2014.
10. Podee, Natthawut, Max, Nelson, Iwasaki, Keiichi, Dobashi, Yoshinori. “Temporal and spatial anti-aliasing for rendering reflections on water waves.” Computational Visual Media, 2021.






