Landscape design 3D modeling: why does pool water always look covered by a layer of blue plastic film—change the water material first or check the elevations?

Conclusion first: In landscape design 3D modeling, when pool water looks as if it is covered by a layer of blue plastic film, the common cause is not the water material sphere but inaccurate water surface elevation, bank coping thickness, pool bottom depth and slope set during modeling. Materials can only add surface reflection; they cannot restore geometric relationships. Based on 2026 project delivery practice, fix the water surface height and bank edge treatment first, then discuss water material, and the amount of rework is usually lower. A quick check: turn off materials and keep only the white model. If the junction between water surface and bank already looks like it is “floating,” later material adjustments are mostly wasted.

1. Why are water features more often misjudged as material problems than planting?

The “fakeness” of planting can often still be pulled back with parameters such as leaf color, tree height and density; water features are different. A water surface is a horizontal line, and people are sensitive to horizontal relationships. If the bank and water surface differ by tens of millimeters, in a close-up it may be read as “the water is about to overflow” or “the pool is almost dry.” Such problems cannot be fixed by adjusting exposure or reflectance during rendering; they can only be solved by changing heights back in the model.

Another reason is that the fakeness of water is often misdiagnosed as a material problem, so water materials are repeatedly swapped and normal perturbation added, making the image dirtier and more mottled. A considerable part of the look of real water comes from depth changes in the pool bottom and the dark areas cast by the bank coping. Both live in geometry, not in the shader. In 2026 projects, clients often first say “the water is wrong,” but when asked further, the common disagreement is about water depth and shoreline, not ripples.

• Water surface above coping: visually the water “floats” on the bank, close-ups are hard to handle, and the elevation usually needs to be reset.
• Water surface too far below coping: looks like a dry pool just after draining, more obvious with a dark pool bottom.
• Pool bottom is one flat slab: water color is uniform, lacking the layering of visible bottom near the shore and deepening in the middle.
• Coping too thin: the bank looks like a sheet of paper and cannot support the weight of the water surface; this is also one source of the “plastic film” feel.
• Vertical pool walls with no edge treatment: reflections are hard-cut at the shoreline and look like misplaced textures.

2. First define the four-layer relationship: water surface, bank, pool bottom and reflection

Breaking a water feature into four layers and advancing in order is based on “who constrains whom”: water surface height constrains bank edge treatment, bank depth constrains pool bottom extent, and only after the first three layers are fixed does the reflection have a stable object. The consequences of skipping the order usually surface only at the rendering stage, by which time the cost of changes has already risen. Leave an explicit acceptance criterion for each layer, and get the client to verbally confirm one version before moving on.

1. Set water surface elevation: use the confirmed master plan’s ±0.00 as the datum; where there is an overflow outlet, use the overflow outlet elevation. A common practice is to keep normal water level 80–150 mm below the top of the coping (experience range, depending on the specific detail). Acceptance: the section drawing can show the numerical difference between water surface and coping.
2. Build bank and coping: coping thickness is commonly 150–300 mm (experience range), and solid stone, washed finish and edge trim details should be distinguished. Acceptance: in a close-up view, the side thickness of the coping is visible, not just a line.
3. Build pool bottom and slope: shallow zones are commonly 0.2–0.4 m and deep zones 0.6–1.2 m (experience range; final per design drawings), and the pool bottom should have a drainage slope. Acceptance: from the bank, the water color transitions from shallow to deep.
4. Define the reflection subject: first clarify what the water surface should reflect—trees, pergola, sky or building facade—and the reflected object’s position in the model should be reasonable. Acceptance: under the main viewpoint, the reflection area is not reflecting empty space.
5. Group water surface and pool bottom: water surface, pool bottom and bank should be grouped separately. Acceptance: when changing water depth, only the height of the water surface group is moved, without affecting other geometry.

Step three is often skipped. The pool bottom is almost invisible in renderings, but it determines water color depth. Many “blue plastic film” feelings are caused by a flat pool bottom plus a highly saturated blue material. Step five leaves room for later changes: in 2026 projects, it is not uncommon for clients to change water depth, add aquatic plants or change bank details after a presentation, and grouping can save an entire rebuild.

3. Materials and rendering: what should be reserved during modeling

There are two common routes for water surface materials: one is a plane with water shading (refraction, reflection, normal perturbation), suitable for still water; the other relies on reflection probes or planar reflections calculated in real time, suitable for scenes with wind, people walking and on-site interaction. Which route to take is not a decision to leave until the rendering stage—if the water surface is built as a solid with thickness from the start, the real-time reflection option will basically require rebuilding the geometry, with cost counted by the day.

Based on common 2026 delivery, a set of comparisons can be checked:

• Rendering route: higher geometry requirements; both pool bottom and bank need to be built solid; experience cycle for a single-scene image is 3–7 working days; changing water depth usually affects only the rendering, not the modeling; suitable for scheme presentations, bids and permit-support packages.
• Real-time engine route (UE5, WebGL/Three.js, etc.): the water surface is better made as a single plane with shading, and the pool bottom can be simplified; experience cycle including interaction and performance optimization is 5–12 working days; changing water depth requires re-baking or adjusting water level parameters, with slightly higher change cost; suitable for showrooms, web pages and VR panorama viewing.

In terms of division of work, water shading, reflection intensity and ripple texture belong to the rendering role; water surface elevation, coping thickness and pool bottom slope belong to the modeling role. At handover, giving a water level section diagram is far more reliable than saying verbally “the water depth is about one meter.” Most divergence in understanding between the two sides comes from that sentence.

4. Delivery experience: what to do first when information is incomplete and the schedule is tight

A common constraint is: the client gives only a colored master plan and a few site photos, water depth and overflow outlet elevation are unconfirmed, yet the schedule has already been compressed to within a week. In practice, we usually first group the water surface separately, set a normal water level based on the experience range, produce a section screenshot for the client to confirm, and then build the bank and pool bottom. The result is usually that the bank and pool bottom only need one round of parameter changes; the cost is half a day to one day spent on confirmation. Conversely, if water surface, pool bottom and bank are combined into one shell from the start, then when the client says “the water is too shallow and the pebbles at the bottom need to be visible,” the whole section has to be rebuilt, commonly costing an extra 2–3 days (experience range), and if it hits a presentation deadline, it means working overnight. The cost is not in the modeling itself but in re-aligning parameters that have already been assumed. In such cases, producing a section before modeling is a relatively common conservative approach we use in landscape projects.

5. Applicable scenarios and boundaries where it does not apply

This approach is suitable for landscape presentation in scheme reports, bids and permit-support packages, as well as water feature shots in cultural tourism promotional films. The criterion is simple: if the client wants to “understand the relationships,” modeling to presentation level is enough; if the client wants “build it exactly like this,” this approach will not help.

• Suitable: scheme comparison, presentation animations, real-time showroom display, VR panorama viewing of gardens and homes.
• No need for fine detail: when only a distant bird’s-eye view is needed and the water surface occupies a very small part of the image, a plane with water shading is enough, and the pool bottom can be omitted.
• Not suitable: projects requiring precise hydraulic calculations, water quality simulation, or setting out pool bottom structure to construction level. These should use construction drawings and engineering models; 3D presentation can only be supporting explanation, not a basis.

Frequently asked questions

How many days does 3D modeling and rendering with a water feature in landscape design usually take?

Based on common 2026 delivery, the experience range for a single-scene water feature from modeling to final image is 5–10 working days; a water feature is usually only one part of the whole garden, and the overall schedule is calculated separately according to scene scale. Later water depth changes usually add 0.5–1 day.

What price range is typical for quoting a pool separately?

There is no uniform price. In the experience range, presentation-level modeling and materials for a single pool commonly cost several hundred to two thousand RMB, depending on the complexity of the bank coping and whether close-up and underwater details are needed; including it in a whole-garden quote is usually more cost-effective.

If modeling and rendering are done separately, what should be handed over?

Small projects are often completed by one person, so handover cost is low; for medium and large projects, separating the roles is more stable, but water level sections, grouping conventions and a reflection subject list must be handed over. Saying only “the water depth is about one meter” increases the probability of rework.

If the client later wants to change water depth, how should deliverable files be provided so that no rebuild is needed?

Common deliverables are source project files plus textures, with FBX or OBJ attached; for real-time projects, an engine project package is provided. As long as water surface, pool bottom and bank are grouped separately, changing water depth usually requires only adjusting the water surface height, not rebuilding.

For the water surface, is a texture or true reflection less likely to be called fake?

For close-ups and shots with an obvious reflection subject, true reflections or planar reflections are more reliable; for distant views where the water surface occupies a small part of the image, a texture with water shading is enough. Judge by whether the reflected object is recognizable in the image.

If your project is stuck at the stage where the water feature looks like plastic film, one thing is worth doing first: produce a water level section and write down three numbers clearly—water surface elevation, coping thickness and pool bottom depth—and have the client confirm one version before continuing. The applicable boundary should also be stated in advance: this approach solves presentation-level realism; it does not replace construction drawings or hydraulic calculations.