The November 2 FlightStick.ini report places the file under %LOCALAPPDATA%\BANDAI NAMCO Entertainment\ACE COMBAT 8\Saved\Config\Windows. Open that directory and back up the actual file before editing. The author reports a new format and an unresolved Warthog throttle-range problem; the post does not supply a verified full-range conversion setting.
On this page

Open the reported configuration folder
- Close the game before copying or editing its configuration.
- Paste
%LOCALAPPDATA%\BANDAI NAMCO Entertainment\ACE COMBAT 8\Saved\Config\Windowsinto Windows File Explorer’s address bar. - Look for FlightStick.ini. Show file extensions if needed so that you can identify the actual filename rather than a similarly named text file.
- Copy it to a backup location and label the copy with your game version and input device.
- Record the existing values before considering any device-specific change.
This is a configuration-file locator. Your campaign save and Steam Cloud backup are a separate task; do not remove either to troubleshoot an axis.
What the Warthog report does not solve
Chaoskaos identifies their device as a Thrustmaster Warthog and reports that a Z-axis assignment with the default axisInputOption: ReverseConvert produced a 0-to-1 range where they expected -1-to-1. At the observation time, the thread had no demonstrated corrective configuration.
Do not turn that question into an instruction to set a guessed conversion value. Nor does the existence of a similarly named AC7 file prove that an AC7 profile can be copied unchanged into this newer format. A useful successful report would include the device, exact before/after entries, game build and observed idle/full-throttle output.
Choose the correct input path
If a keyboard acceleration key instead deploys the airbrake, use the combined-binding check. If you deliberately use a virtual Xbox controller, use the mapper’s own profile and output checks. Those sources do not verify every native INI field.
If the file is absent, confirm the directory, device and installed version rather than creating an invented template. The publisher acknowledges peripheral connection changes and directs operation questions to the respective manufacturer. Preserve your original configuration so a failed edit can be reversed.
Sources & limits
Community reports are attributed, not tests performed by this site. Builds are unspecified unless stated.
- Reddit: Chaoskaos’s FlightStick.ini location and Warthog question ↗
Original and author’s device reply read November 2. No successful axis-range answer was present.
- Bandai Namco: peripheral connection changes ↗
Publisher acknowledges changed connections and manufacturer support; it does not provide this INI schema or a Warthog fix.