> 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/supercarrier-pro-ctds-on-spawn-or-when-flying-to-carrier.md).

# Supercarrier Pro CTDs - On Spawn or when Flying to Carrier

{% hint style="warning" %}
**THIS BUG IS UNDER INVESTIGATION FOR A DEFINITIVE SOLUTION.**
{% endhint %}

We have identified that **REX Real Global Airport Textures may trigger Crash to Desktops** with our Supercarrier Pro product. We have been unable to identify what is the source bug resulting on these CTDs, but we are in communication with the team at REX to provide a solution to this issue.

In the meantime, please **uninstall REX Real Global Airport Textures.** 

### On AMD Graphics Cards:

We are aware of issues with AMD Graphics Cards that may result on Crash to Desktops. This issue is not unique to Supercarrier Pro, but rather a generalized MSFS Issue with stock arresting gear. This issue has been raised to Asobo for further investigation.

Luckily, we have found a workaround for those customers who own an AMD Graphics Card: 

* delete ***reference\_points.cfg*** on both 
  * miltechsimulations-supercarrier-pro\SimObjects\Boats\Miltech CVN78 
  * miltechsimulations-supercarrier-pro\SimObjects\Boats\Miltech USS76. 

**Do keep in mind that if you decide to do that, you must use “Modern Arrestors” on all landings - regardless if the aircraft has a tailhook or not.**

For more information on Modern Arrestors, click here: [Arrestor Cables](/supercarrier-pro/supercarriers/approach-and-landing-equipment-and-operations/arrestor-cables.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/supercarrier-pro-ctds-on-spawn-or-when-flying-to-carrier.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.