# Real-time Rendering

Rendering games with large decision trees will mean the possibility of zooming into the image, exploring all the possible ways to play it. However, there will be too much information to simply create a high enough resolution image. If you wanted to print a single high-res image of noughts and crosses, rendering the whole of the game tree, you would need an area of \~$$1.66m^2$$ or \~$$65in^2$$ ( $$= 3^9pixels \* 300pixels/in$$ )

Instead, we can filter the game tree by keeping track of only the parts that are being displayed within the viewport, collecting only the data for possible games within that sub-tree.

![Real-time pipeline](https://2502734374-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdM8iXEiSa6vIC3EFqT%2F-MdbkOI0-xVxw7B9hyCn%2F-MdbtftVpYhzbTqpNTIG%2Fpipeline-real-time.svg?alt=media\&token=29fdfdb4-85db-47ef-92ba-7c8b39ff1591)


---

# 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://b-hub.gitbook.io/faze/v2.0.0/concept/real-time-rendering.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.