docs(troubleshooting): reorganize troubleshooting section and modernize logging docs

- Add Standard Modes / external flight mode troubleshooting page (Fixes #14890)
- Move actuators troubleshooting from setup docs to troubleshooting section
- Move Console Logging page from settings to troubleshooting section
- Update stale UI names to App Log Viewer / Categories
- Update log category names to current dotted runtime names
- Replace outdated console logging screenshot, remove orphaned assets

Author: DonLakeFlyer

docs/assets/support/app_log_viewer.jpg

@@ -65,7 +65,6 @@
   - [Plan View](qgc-user-guide/settings_view/plan_view.md)
   - [ADSB Server](qgc-user-guide/settings_view/adsb_server.md)
   - [Comm Links](qgc-user-guide/settings_view/comm_links.md)
-  - [Logging](qgc-user-guide/settings_view/console_logging.md)
   - [Maps](qgc-user-guide/settings_view/maps.md)
   - [NTRIP / RTK](qgc-user-guide/settings_view/ntrip_rtk.md)
   - [PX4 Log Transfer](qgc-user-guide/settings_view/px4_log_transfer.md)
@@ -82,12 +81,15 @@
   - [MAVLink Inspector](qgc-user-guide/analyze_view/mavlink_inspector.md)
 - [Reference](qgc-user-guide/reference/index.md)
   - [Troubleshooting](qgc-user-guide/troubleshooting/index.md)
+    - [Console Logging](qgc-user-guide/troubleshooting/console_logging.md)
     - [Setup Problems](qgc-user-guide/troubleshooting/qgc_setup.md)
     - [Usage Problems](qgc-user-guide/troubleshooting/qgc_usage.md)
       - [Connection problems](qgc-user-guide/troubleshooting/vehicle_connection.md)
       - [Parameter Download failures](qgc-user-guide/troubleshooting/parameter_download.md)
       - [Plan Upload/Download failures](qgc-user-guide/troubleshooting/plan_upload_download.md)
       - [Resume Mission failures](qgc-user-guide/troubleshooting/resume_mission.md)
+      - [Standard Modes / External Flight Mode failures](qgc-user-guide/troubleshooting/standard_modes.md)
+      - [Missing Actuators Page (PX4)](qgc-user-guide/troubleshooting/actuators.md)
   - [Privacy Policy](qgc-user-guide/reference/privacy_policy.md)
 
 - [Developer's Guide](qgc-dev-guide/index.md)

docs/assets/support/console.jpg

@@ -30,16 +30,16 @@ Linux Terminal:
 
 The options/command line arguments are listed in the table below.
 
-| Option                                                    | Description                                                                                                                          |
-| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `--clear-settings`                                        | Clears the app settings (reverts _QGroundControl_ back to default settings).                                                         |
-| `--logging:full`                                          | Turns on full logging. See [Console Logging](../qgc-user-guide/settings_view/console_logging.md#logging-from-the-command-line). |
-| `--logging:full,LinkManagerVerboseLog,ParameterLoaderLog` | Turns on full logging and turns off the following listed comma-separated logging options.                                            |
-| `--logging:LinkManagerLog,ParameterLoaderLog`             | Turns on the specified comma separated logging options                                                                               |
-| `--unittest:name`                                         | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests.                                                |
-| `--unittest-stress:name`                                  | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests.                                |
-| `--fake-mobile`                                           | Simulates running on a mobile device.                                                                                                |
-| `--test-high-dpi`                                         | Simulates running _QGroundControl_ on a high DPI device.                                                                             |
+| Option                                                                 | Description                                                                                                                       |
+| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `--clear-settings`                                                     | Clears the app settings (reverts _QGroundControl_ back to default settings).                                                      |
+| `--logging:full`                                                       | Turns on full logging. See [Console Logging](../qgc-user-guide/troubleshooting/console_logging.md#logging-from-the-command-line). |
+| `--logging:full,Comms.LinkManager:verbose,FactSystem.ParameterManager` | Turns on full logging and turns off the following listed comma-separated logging categories.                                      |
+| `--logging:Comms.LinkManager,FactSystem.ParameterManager`              | Turns on the specified comma separated logging categories.                                                                        |
+| `--unittest:name`                                                      | (Debug builds only) Runs the specified unit test. Leave off `:name` to run all tests.                                             |
+| `--unittest-stress:name`                                               | (Debug builds only) Runs the specified unit test 20 times in a row. Leave off :name to run all tests.                             |
+| `--fake-mobile`                                                        | Simulates running on a mobile device.                                                                                             |
+| `--test-high-dpi`                                                      | Simulates running _QGroundControl_ on a high DPI device.                                                                          |
 
 Notes:
 

docs/assets/support/console_dialog.jpg

@@ -114,7 +114,7 @@ The following file forces the video decoder setting to a specific value and hide
 
 ## Debugging
 
-Enable the `SettingsManagerLog` logging category ([Console Logging](../../qgc-user-guide/settings_view/console_logging.md)) to see which override files are loaded and which overrides are applied at startup.
+Enable the `Utilities.SettingsManager` logging category ([Console Logging](../../qgc-user-guide/troubleshooting/console_logging.md)) to see which override files are loaded and which overrides are applied at startup.
 
 ## Related Mechanisms
 

docs/en/SUMMARY.md

@@ -73,6 +73,7 @@ This tool is only visible if the vehicle firmware supports ROI mode.
 ### Return / Land
 
 Adds a return or land command to the mission. The label varies by vehicle type:
+
 - **Multicopters:** _Return_
 - **Fixed-wing:** _Land_ (or _Alt Land_ if a land item already exists in the mission)
 
@@ -193,6 +194,4 @@ The loss rate should be in the low single digits (i.e. maximum of 2 or 3):
 - Higher loss rates often lead to 100% failure.
 
 There is a much smaller possibility that issues are caused by bugs in either flight stack or QGC.
-To analyze this possibility you can turn on [Console Logging](../settings_view/console_logging.md) for Plan upload/download and review the protocol message traffic.
-
-
+To analyze this possibility you can turn on [Console Logging](../troubleshooting/console_logging.md) for Plan upload/download and review the protocol message traffic.

docs/en/qgc-dev-guide/command_line_options.md

@@ -28,7 +28,7 @@ Use the **search bar** at the top of the settings sidebar to find any setting by
 **[Comm Links](comm_links.md)**
 <br>Manually create communication links and configure auto-connect options.
 
-**[Logging](console_logging.md)**
+**[Logging](../troubleshooting/console_logging.md)**
 <br>Capture application logs for help with diagnosing problems.
 
 **[Maps](maps.md)**

docs/en/qgc-dev-guide/file_formats/settings_override.md

@@ -29,48 +29,4 @@ Dynamic action buttons (e.g., beep, identify, 3D mode) are shown based on the ve
 
 ## Troubleshooting a Missing Actuators Page
 
-The Actuators page is shown when QGroundControl receives and initializes the
-vehicle's `COMP_METADATA_TYPE_ACTUATORS` component metadata. The firmware
-version alone does not determine whether the page is available. If the
-metadata is unavailable, cannot be initialized, or its top-level `show-ui-if`
-condition evaluates to false, QGroundControl uses the legacy Motors page
-instead.
-
-### Capture Diagnostic Logs
-
-1. Open **Application Settings > App Log Viewer**.
-2. Click **Categories** and enable these categories:
-   - `Vehicle.Actuators.PX4AutoPilotPlugin`
-   - `Vehicle.Actuators.Common`
-   - `ComponentInformation.RequestMetaDataTypeStateMachine`
-   - `Vehicle.FTPManager`
-3. Connect the vehicle. If it is already connected, disconnect and reconnect
-   it so that QGroundControl requests the component metadata again.
-4. Open **Vehicle Setup** and check whether **Actuators** or **Motors** is
-   available.
-5. Return to **App Log Viewer** and click **Save**. Keep the saved app log
-   unchanged when attaching it to a support request.
-
-The metadata URI can use MAVLink FTP (`mavlinkftp://`) or HTTP. QGroundControl
-tries the primary URI first and then the fallback URI advertised by the
-vehicle.
-
-### Read the Diagnostic Messages
-
-| Log category | Message or pattern | Meaning |
-| --- | --- | --- |
-| `Vehicle.Actuators.PX4AutoPilotPlugin` | `Vehicle did not provide actuators metadata via component information` | No actuator metadata was received from the vehicle. |
-| `Vehicle.Actuators.PX4AutoPilotPlugin` | `Actuators initialization failed` | Metadata was received but could not be parsed or initialized. |
-| `Vehicle.Actuators.PX4AutoPilotPlugin` | `Condition 'show-ui-if' evaluated to false` | The vehicle's metadata indicated the page should not be shown. This can be intentional for your configuration, or a firmware/metadata mismatch. Attach the saved log to a support request. |
-| `ComponentInformation.RequestMetaDataTypeStateMachine` | `primary failed, requesting metadata (fallback) from ...` | The primary metadata URI failed and QGroundControl is trying the fallback URI. |
-| `ComponentInformation.RequestMetaDataTypeStateMachine` | `FTP download failed` or `HTTP download failed` | The selected transport could not download the metadata. An HTTP status such as `404` identifies a missing or incorrect URL. |
-| `ComponentInformation.RequestMetaDataTypeStateMachine` | `failed to load metadata (primary and fallback)` | Both metadata URIs failed, so the Actuators page cannot be initialized. |
-| `Vehicle.FTPManager` | `Download fromCompId`, `Nak - ...`, or timeout messages | Details of the MAVLink FTP request and any vehicle-side error. |
-
-### Include This Information in a Support Request
-
-Include the QGroundControl version and build, PX4 firmware version, vehicle
-type, connection type, whether the legacy Motors page appears, and the saved
-app log. If the log contains a fallback or download error, include the full
-line with the URI and error text. Also mention whether reconnecting the vehicle
-changes the result.
+If the Actuators page does not appear (the legacy Motors page is shown instead), see [Missing Actuators Page](../../troubleshooting/actuators.md).