MOZA Base FAQ
• Q: Can the MOZA base be used with Xbox or PlayStation consoles?
- ○ The available products are only compatible with Windows PC platforms currently. Systems such as Mac OS, Linux OS, PS4, PS5, Xbox One, and Xbox Series X are not officially supported.
• Q: Is the MOZA base compatible with flight sticks from other brands?
- F-16C Viper HOTAS Add-On Grip
- F/A-18C Hornet™ HOTAS Add-On Grip
- Constellation ALPHA [R]
- 16EX Metal Joystick
• Q: Which flight sim games does the MOZA base support?
- ○ Digital Combat Simulator
- ○ War Thunder
- ○ Microsoft Flight Simulator 2020
- ○ Microsoft Flight Simulator 2024 (Unreleased)
- ○ Star Citizen
- ○ IL-2 Sturmovik: Great Battles
• Q: Can the MOZA base be connected to extension rods or other connectors?
- ○ As long as the connectors on both ends have the correct 5-pin data cable interfaces, it should work in theory.
• Q: Is the MOZA base compatible with flight sim hardware from other brands?
- ○ Generally, devices from different brands can only be used via separate USB ports to the Windows PC. Beyond this, they are not typically compatible with each other.
• Q: Can I use third-party cables to connect the base to my PC (USB, RJ11, etc.)?
- ○ Technically, you can use any cable with the correct RJ11 or USB connectors on both ends. However, even if they work, MOZA cannot guarantee full functionality with third-party cables as they are not officially supported.
• Q: The base is not centering
- ○ The MOZA base automatically performs a centering calibration when powered on. However, due to variations in flightstick models and weights, you can perform manual calibration through the MOZA Cockpit software.
• Q: The base fails to power on
- ○ Please confirm the following:
- ▪ Ensure the power cable is properly connected
- ▪ Ensure the switch on the power cable (if applicable) is turned on
- ▪ Confirm the power switch on the rear of the base has been pressed
- ▪ Confirm the indicator light on the rear of the base is on
- ○ If everything seems fine, please check:
- ▪ Is there any damage to the power supply or cables
- ▪ Is there any visible damage to the power port on the base?
- ▪ If the issue persists after troubleshooting, please reach out to our technical support team at support@mozaracing.com
• Q: The base is unresponsive after connecting to power or suddenly loses FFB during gameplay
- ○ Check if the power cable to the base is loose
- ○ Check if the indicator light on the rear of the base is flashing
- ○ If the indicator light is flashing, hold the power button for 3 seconds to turn the device off, then press it again to restart.
- ○ After confirming everything is functioning properly, open "USB Game Controllers" on your Windows PC and check the device connection status.
- ○ If the problematic device appears on the page, select it, right-click the "Properties" button, go to the "Test" tab, and verify that the device is working correctly.
- ▪ If the device works, try reconfiguring it within your game.
- ▪ If the device is not functioning properly, please check that its configuration in the MOZA Cockpit software is correct.
- ▪ If the device does not appear on the "USB Game Controllers" page or is not detected by MOZA Cockpit software, please contact our technical support team at support@mozaracing.com
FFB & Software FAQ
• Q: MOZA Cockpit software or the game doesn't recognize my flight stick
- ○ If you are using a third-party flight stick, first ensure that it appears in the selectable list on the flight stick page of the MOZA Cockpit software.
- ○ If your flight stick is listed as supported, try unplugging and reconnecting it.
- ○ If the issue persists after troubleshooting, please contact our technical support at support@mozaracing.com
• Q: MOZA base can not be recognized by games downloaded from Steam
- ○ Start Steam, tab to "Settings" - "Controller".
- ○ Uncheck the "Enable Steam Input for generic controllers" option in "Controller" Settings.
- ○ If the issue persists, try reinstalling Steam.
Q: If the base is powered off using the power button and then restarted, or if the USB cable is unplugged and reconnected during gameplay the flightstick in-game stops receiving signal and becomes unresponsive?
- ○ Unplugging and reconnecting the USB cable during gameplay will cause the game to register the device as disconnected. Due to this, the game must be completely closed and restarted for the device to be recognized again.
• Q: After successfully mapping the flight stick axis, switches, and related buttons in the game, the assigned controls fail to execute the corresponding actions during gameplay
- ○ This issue is caused by the game misidentifying the controller options. Please exit the game, restart the base, and remap the axis and related buttons before starting the game.
• Q: The force feedback in the game feels too weak or too strong. How to adjust the settings?
- ○ Try the following steps to troubleshoot and adjust settings as necessary:
- ○ 1. Adjust the FFB strength in the game. For example, DCS and War Thunder support FFB adjustments directly.
- ○ 2. If the FFB effect is still unsatisfactory after in-game settings, try the following steps:
- ○ If the overall FFB still feels too weak, you can increase the force feedback intensity in the MOZA Cockpit software settings.
Q: Compatibility with Third-Party Flight Stick
A: To setup a third-party flight stick, click on the flight stick icon in "My Devices" section of the main interface. You can also access the stick page settings by selecting the flight stick icon in the left sidebar.
For HOTAS flight sticks that follow standard protocols, select "MH16" from the "Grip Select" dropdown menu in the flight stick settings to recognize all button inputs.
If you are using a flight stick from the MOZA Flight lineup, after selecting the appropriate option, you will see a schematic on the right side showing the flight stick layout and button number.
For other flightsticks that use standard protocol (5-pin mini DIN connector), please select the option that corresponds to your specific model.
Note: Support for axis inputs from third-party flightstick will be added in a future update.
Q: Purpose of the POV Hat Button Mode?
A: The POV Hat button mode can be configured in the flight stick settings. This mode is designed for flight sticks in the MOZA Flight series that are equipped with an 8-way POV Hat, such as the MH16 and MA3X. When switched to D-Pad mode, the POV Hat can be used to control the hat view.
Q: How to Submit an Error Report / MOZA Cockpit Software Crash / Report Error Fails to Send
A: If you encounter any program errors or crashes while using MOZA Cockpit software, you can submit an error log to us via the "Report Error" feature in the settings. This log will include information about your MOZA Flight firmware and MOZA Cockpit software.
Follow the instructions on the "Report Error" screen to provide your contact information and describe the issue.
Once the error report is successfully submitted, you will receive a report ID. Please make a note of this ID, as our support team may contact you if needed. If you prefer not to be contacted, please indicate this in the report.
If the error report fails to send, try enabling 'Proxy Mode' under Settings - Preferences, then attempt to send the report again. If the error report still fails to send after enabling proxy mode, you can click 'Save Report As' to generate a .zip file containing the error details. Please attach this file and send it to our support email at support@mozaracing.com
For any other feedback or suggestions regarding the software or MOZA Flight devices, feel free to email us at support@mozaracing.com
Q: Do I need to run MOZA Cockpit in administrator mode?
A: No, you don’t. Running the MOZA Cockpit software in administrator mode does not fundamentally differ in functionality from running it as a regular user.
Q: What is the purpose of setting the game path?
A: On the right side of the main interface, you'll see a list of available games. This list serves as quick-launch buttons, allowing you to start games directly through the MOZA Cockpit software.
If you installed the game via Steam, simply hover over the game icon and click to start. If you downloaded the game from the official website, hover over the game icon, click the Windows icon in the top right corner to switch to path mode.
After switching to path running mode, click the “Set Install Path” button.
Then browse to the corresponding game's installation path and select the game’s executable file (.exe). Once set, click “Start Game” to begin playing!
Please note that during the first launch of the game, we will need to perform automatic configuration and script/plugin writing for certain games that require configuration to export telemetry data. If an error occurs during telemetry initialization, please contact us through the error report or other customer service channels.
Q: No force feedback when playing games? (Supported game list)
A: As of early September 2024, the MOZA Flight products support games including (but not limited to) DCS World, X-Plane 11, X-Plane 12, Microsoft Flight Simulator 2020, Star Citizen, War Thunder, and IL-2 Sturmovik: Great Battles. Additionally, the base supports other games that output force feedback using standard HID.
For games that do not natively support telemetry force feedback, MOZA Cockpit employs our self-developed MCLS technology to simulate force feedback. This is achieved by calculating the forces generated in the aircraft using the game's telemetry data output and sending corresponding force feedback signals.
Currently supported games include DCS World and Microsoft Flight Simulator 2020.
Future support for telemetry force feedback is planned for additional games such as War Thunder, IL-2 Sturmovik: Great Battles, X-Plane 11, and X-Plane 12, with updates being gradually rolled out in upcoming versions.
Q: I have launched the game; how do I select the preset file for a specific aircraft?
A: Click on the base icon in the main interface or the left sidebar to access the base configuration page. In the "Basic Settings" tab, you’ll find the "Presets" section. For example, in DCS World, click on the dropdown menu corresponding to DCS World in the presets section, and select the appropriate aircraft model to load the preset.
Please note that presets within the same game can be applicable to multiple aircraft models. The main purpose of a preset is to adjust the handling and force feedback effects for different models by loading the parameters from the preset file.
Note: The auto-matching and switching preset feature will be introduced in a future update.
Q: The base is displayed in the game, but I can't bind keys?
A: The base in the game may appear with multiple HID names for extended devices. Generally, the first one listed is the base itself, while the others represent button extensions.
Q: How do I create a new preset?
You can save all the parameters from the base settings interface as a new preset file. Click the "New Preset" button in the bottom right corner, enter a preset name, and select the corresponding game to save it.
In the current version, if you want to overwrite an existing preset, simply enter the same preset name.
- ● Note: Official presets cannot be overwritten.
Q: What do the sliders in the base basic settings do?
A: The basic settings of the base include Maximum Torque Output, Overall Force Feedback Intensity, Spring, Damper, Inertia, and Friction.
The forces used by the base to simulate feel are divided into two forms: 1. Constant force; 2. Periodic force.
Constant force is a steady force in a specific direction, while periodic force involves vibrations of varying amplitudes and frequencies.
Torque
- ● The "Maximum Torque Output" option in basic settings restricts the maximum torque output on the X or Y axis direction. Any effects exceeding the set maximum will be cut off. For more details, hover over the exclamation mark icon next to the label.
- ● The "Overall Force Feedback Intensity" option in the basic settings proportionally scales the actual output force feedback, including both constant force and periodic force, according to the set percentage. For more details, hover over the exclamation mark icon next to the label.
Mechanical Centering
- ● The "Spring" in basic settings provides a constant centering force unrelated to game output or telemetry force feedback, not adjusting the overall centering force gain.
- ● The Spring intensity is related to the displacement distance of the flightstick. Generally, the further from the center point, the stronger the force. Conversely, the closer to the center point, the weaker the force.
Mechanical Damping
- ● The "Damper" in basic settings provides a constant feel (damping force) unrelated to game output or telemetry force feedback, not adjusting the overall damping force gain.
- ● The damping intensity depends on the displacement speed: faster displacement results in stronger damping; slower the displacement results in weaker damping.
Mechanical Inertia
- ● The "Inertia" in basic settings provides a constant feel that is unrelated to game output or telemetry force feedback, not adjusting the overall inertia gain.
- ● The inertia intensity depends on the acceleration of displacement: more vigorous displacement leads to stronger inertia.
Mechanical Friction
- ● The "Friction" in basic settings provides a constant feel (friction force effect) that is unrelated to game output or telemetry force feedback, not adjusting the overall friction gain.
- ● The friction intensity is constant and does not depend on displacement, speed, or acceleration.
Q: What are the differences between the force feedback output modes that MOZA Flight lineup supports?
The MOZA Flight product line supports three force feedback modes:
- Direct Input: In this mode, the game directly controls the force feedback effects of the input device, making it suitable for games that natively support force feedback.
- Telemetry FFB: This mode retrieves telemetry data from the game and calculates the corresponding force feedback effects through MOZA Cockpit. In this mode, the Direct Input force feedback effects are inactive, making it suitable for games that do not natively support force feedback or have poor quality force feedback output.
- Integrated FFB: In this mode, both the force feedback signals output directly by the game via HID and the telemetry force feedback signals are active. Users can choose to blend these two signals at a certain ratio, which can be adjusted using the "Game Force Feedback Output" slider in the basic settings.
Q: How do I calibrate the base?
A: To calibrate the base, click on the base icon in the main interface or the base icon in the left sidebar to access the base configuration page. On the right side of the settings page, you will see an "Auto Calibrate" button. Each time the base is powered on, it will automatically go through a calibration process, where the base axes will move to the maximum physical travel positions of the X and Y axes and then return to the midpoint.
If the midpoint of the base shifts due to other reasons during use, you can either restart the base or click the "Auto Calibrate" button to allow the base to complete the calibration automatically. After clicking "Auto Calibrate," a pop-up will display the calibration status. You can click the "Cancel Calibration" button at any time to stop the calibration process.
If you only need to calibrate the X or Y axis individually, you can click the "Calibrate" button next to the corresponding axis label. A 10-second countdown will then appear on the screen. Please move the flight stick to the maximum travel position of the corresponding axis 1 to 2 times before the countdown ends, and then return the flight stick to a position near the center.
Q: How do I reset the base?
A: If you encounter abnormal behavior with the base during use or after updating the software and firmware, you can try resetting the base. Click the "Reset Base" button in the basic settings. Before resetting, please move the flight stick to a position near the midpoint, then remove the flight stick head and extension rod, and click confirm to start the reset process. During the reset, do not touch the base to avoid a failed reset. Once the reset progress bar completes, click confirm to finish the reset process.
Q: How do I limit the maximum travel and set soft limits of the flight stick?
A: Go to the base settings and click on the "Axis Travel" tab. Below the curves for the X and Y axes, you will see the movement limits for both the positive and negative directions (soft limits). In our system, the left corresponds to the negative direction of the X axis, the right corresponds to the positive direction of the X axis; the front corresponds to the negative direction of the Y axis, and the back corresponds to the positive direction of the Y axis. When the flight stick reaches the set limits, you will feel significant resistance.
Q: How do I upgrade the firmware?
A: Click the Firmware Upgrade button.
In this section, you can view the firmware versions of all connected devices.
Next, click the "Launch Upgrade Tool" button in the upper right corner. Please note that you need to close the MOZA Cockpit software before launching the upgrade tool; the software will automatically prompt you to close it.
In the opened firmware management tool, you can use the online upgrade feature to update the firmware version of the corresponding device. If you prefer to update the firmware using an offline firmware update package (.bin), uncheck the "Online Upgrade" option, then drag and drop the firmware update file onto the corresponding device icon to start the upgrade process.
Q: What do the green and red dots on the axis position indicator represent?
A: The green dot represents the logical axis value, which is the final axis value output to the game, while the red dot indicates the logical value of the torque output from the base. Similarly, in the display of each axis value below the indicator, the green text represents the logical axis, and the red text represents the torque logical value.
Q: What should I do if the force feedback effect is abnormal, with excessive shaking, large amplitude, or high frequency?
A: If you encounter this situation, please first ensure that you have updated to the latest firmware and software version, and then reselect the presets provided by MOZA Cockpit. If the issue persists, it may be due to abnormal parameters in the telemetry force feedback. You can start by switching to Direct Input mode to see if the abnormality disappears. Then, switch back to telemetry force feedback mode, turn off all telemetry effects, and gradually enable them one by one to help identify any potential issues. If you find that a specific effect is abnormal, you can try adjusting the parameters associated with that effect to resolve the problem.
If the abnormality continues despite adjusting the parameters, please contact our after-sales team for assistance.