Ace Combat 8 PC HOTAS setup: Joystick Mapper and reported alternatives

Choose the route that matches the symptom

The publisher’s September 30 flight-stick update acknowledges missing configuration options compared with AC7 and says improvements are being investigated. That announcement is not a released compatibility patch.

The Joystick Mapper project is a community option for hardware the game does not read as intended. Its Windows installer is described by the maintainer as unsigned; review the project and release before deciding to install it. This site has not audited the executable. A HORI device with constant left yaw has a separate model-specific mode report.

Create a profile and verify the output

1. Read the maintainer’s installation instructions and obtain the appropriate release from the project’s own Releases page if you choose to use it.
2. Connect the stick and throttle; open Profile → New profile and choose Ace Combat 8 as the starting point. The built-in Default profile leaves the stick unmapped.
3. Select each device in the top bar. Check its assigned role before changing its controls.
4. Map axes/buttons to Xbox inputs and watch the on-screen controller output.
5. Save the profile. Keep the mapper running during the game.
6. Use a training flight to check steering, throttle and weapons before a difficult mission.

Steam replies #4–5 report VKB Gladiator/STECS success and profile setup. Reply #8 says this route needs the mapper running, rather than the other method’s launch-command chain. That does not prove an arbitrary old launch argument is safe to delete.

When the output is wrong

The project documents Recenter for drift, axis inversion, and separate axis tuning. For a twist mapped to LB/RB, its press point controls when movement becomes a button press. Change the relevant setting and check the displayed output before retrying the game.

If it works in the mapper but not in-game, retain your model, profile and exact input symptom for the maintainer’s issue form. The source documents a universal layout for unlisted devices and beta status for several named layouts; a picture in the app is not proof of a fully tested AC8 setup.

The older multi-tool report and its limits

MapleVortex’s separate Steam setup reports WinCtrl stick/throttle and Moza pedals using Gremlin, vJoy, HidHide and x360ce v4. Its forward/reverse throttle split near 38% is that device’s calibration, not a percentage to copy onto every throttle.

For that route, physical devices are hidden while Gremlin and x360ce remain allowed to read them; the virtual devices remain visible. Nefarius’ HidHide guide explains application access and device cloaking. x360ce’s v4 documentation uses a virtual controller and says to keep the application running. It differs from v3 DLL-in-game-folder instructions.

Do not combine both routes’ settings by default. Keep a record of the method and profile that actually works so an unwanted mapping can be paused or reversed. This Windows guide does not establish console HOTAS support, TrackIR support or Linux Online compatibility.