> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shaky-camera-shaky-ship-bug-moving-ships.md).

# "Shaky Camera"/"Shaky Ship" Bug - Moving Ships

If you have experienced a bug on moving ships in which the carrier/camera "shakes" (moving ships only) - Congrats, you have a very powerful PC.

This issue occurs when the simulator runs at a very high and unstable framerate, higher than the rate of update of the ship's position. The violent framerate deviations cause the ship to accelerate and decelerate at uneven intervals, resulting in this flickering bug. 

The refresh rate of the ship is approximately 50 times a second, so to solve this issue, we must limit the framerate just under this figure:

### Solution 1: VSync

1. Verify if you have a GSync-enabled monitor. If you do, disable GSync.
2. On Simulator Graphic Settings menu, enable VSync. Set VSync to 33% or 50% of the refresh rate of your monitor. This will limit your FPS as well - find the best compromise between framerate limiting and reduction of the flickering issue.
3. Launch the carrier. Change the settings until the carriers and the simulator run smoothly.

### Solution 2: Limit your FPS

1. Close the Simulator
2. Launch Nvidia Control Panel or AMD Equivalent
3. Under "program settings", select Microsoft Flight Simulator
4. Under "Max Frame Rate", set it to **exactly 48 FPS**
5. Relaunch the Simulator. Problem should now be fixed.

<figure><img src="https://758643107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGh3w7rlq5fvH9zEMD9OZ%2Fuploads%2FtIVcVU4ifvWNbDAguHB7%2Fimage.png?alt=media&amp;token=351b72ad-d0a2-40f4-a940-39847bf199ba" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

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/shaky-camera-shaky-ship-bug-moving-ships.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.

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.