# Page Not Found

The URL `fullview-for-ndi/ms-settings:display` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [About FullView for NDI 6.2](https://tractus.gitbook.io/tractus-tools-for-ndi/fullview-for-ndi/about-fullview-for-ndi-6.2.md)
- [Diagnosing Performance](https://tractus.gitbook.io/tractus-tools-for-ndi/using-multiview-for-ndi/diagnosing-performance.md)
- [Output Multiview to NDI to a Web Browser using Central Control Connect](https://tractus.gitbook.io/tractus-tools-for-ndi/using-multiview-for-ndi/output-multiview-to-ndi-to-a-web-browser-using-central-control-connect.md)
- [Release Notes - FullView for NDI](https://tractus.gitbook.io/tractus-tools-for-ndi/release-notes-fullview-for-ndi.md)
- [NDI Tally](https://tractus.gitbook.io/tractus-tools-for-ndi/getting-started/ndi-tally.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tractus.gitbook.io/tractus-tools-for-ndi/fullview-for-ndi/about-fullview-for-ndi-6.2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://tractus.gitbook.io/tractus-tools-for-ndi/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://tractus.gitbook.io/tractus-tools-for-ndi/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/tractus-tools-for-ndi/fullview-for-ndi/about-fullview-for-ndi-6.2.md`).

You may also use `Accept: text/markdown` header for content negotiation.