# Page Not Found

The URL `product-information/known-bugs-updates-and-product-roadmap/shimmering-vertical-lines-behind-the-ship-broken-wake-effects` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Shimmering "Bounding Box" on Arrestor Cables](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shimmering-bounding-box-on-arrestor-cables.md)
- ["Shaky Camera"/"Shaky Ship" Bug - Moving Ships](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shaky-camera-shaky-ship-bug-moving-ships.md)
- [Multiplayer Sync freezing screen after Restart](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/multiplayer-sync-freezing-screen-after-restart.md)
- [Osprey/Harrier Sliding on the Deck](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/osprey-harrier-sliding-on-the-deck.md)
- [Aircraft Jitters/Jerky movements on Deck & Elevators](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/aircraft-jitters-jerky-movements-on-deck-and-elevators.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://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shimmering-bounding-box-on-arrestor-cables.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 `build a script that syncs our docs to a CMS` 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://docs.miltechsimulations.com/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.miltechsimulations.com/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., `/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shimmering-bounding-box-on-arrestor-cables.md`).

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