# C++ Summary

You've got the **UWaterSubsystem**, which handles the intersections, and which actor/component gets which vertices, and that's all handled by the **AWaterZoneActor**, which is the volume that holds all mesh components and divides the rendering into tiles.

You then have the **UWaterMeshComponent** which builds the geometry data for a specific section of the water system (ie, river, ocean, lake, transition piece), which uses a **HActor** as a hit proxy which makes the geometry selectable in the viewport.

This data is then stored in a **FWaterQuadTree**, which is passed to a **FWaterMeshSceneProxy**, which handles the drawing like a primitive, which uses **TWaterVertexFactory** to draw said vertices to the screen.

**TWaterVertexFactory** then uses **FWaterMeshVertexBuffer** and **FWaterMeshIndexBuffer** in a collection of **TWaterInstanceDataBuffers** in a RHI thread.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.oserosuite.com/technical-notes/unreal-engine-notes/water-plugin/c++-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.