> 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.md).

# Known Bugs, Updates & Product Roadmap

## Frequent Answered Questions

<details>

<summary>How to remove Chocks/Covers on Moving Carriers (FS24)</summary>

To remove pitot covers/chocks/etc in FS24 Moving Carriers, just use the “Quick Preflight” keybind (configure on your MSFS Controls settings and map to one key). This will remove everything on preflight, even on moving ships. Unfortunately, there is a hardcoded simulator limitation preventing walkarounds on moving ships.

</details>

<details>

<summary>Quick Taxi not Working (FS24)</summary>

Quick Taxi requires engines to be running in certain specific aircraft.&#x20;

One of such aircraft is the stock FA18. This is due to how hydraulic systems have been set up and how the joystick input is being detected, engines must be started before using Quick Taxi.

We are looking into other solutions to this problem.

</details>

## Known Bugs

As with any revolutionary piece of software, there will be some bugs at the beginning. We have acknowledged and fixed the following bug&#x73;**:**

* [Supercarrier Pro CTDs - On Spawn or when Flying to Carrier](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/supercarrier-pro-ctds-on-spawn-or-when-flying-to-carrier.md)
* ["Shaky Camera"/"Shaky Ship" Bug - Moving Ships](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shaky-camera-shaky-ship-bug-moving-ships.md)&#x20;
* [Multiplayer Sync freezing screen after Restart](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/multiplayer-sync-freezing-screen-after-restart.md)
* [Misplaced Crew/Teleport not functioning/Quick Taxi not functioning](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/misplaced-crew-teleport-not-functioning-quick-taxi-not-functioning.md)
* [Shimmering "Bounding Box" on Arrestor Cables](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/shimmering-bounding-box-on-arrestor-cables.md)
* [Osprey/Harrier Sliding on the Deck](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/osprey-harrier-sliding-on-the-deck.md)
* [Loaded in a Carrier and my aircraft is invisible/partially loaded](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/loaded-in-a-carrier-and-my-aircraft-is-invisible-partially-loaded.md)
* [Aircraft Jitters/Jerky movements on Deck & Elevators](/supercarrier-pro/product-information/known-bugs-updates-and-product-roadmap/aircraft-jitters-jerky-movements-on-deck-and-elevators.md)


---

# 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.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.
