Smart Tool keymap import 'failed' on first attempt — Restore DB sequence
When importing a keymap file (.txt) via the Smart Tool, the operation fails with a generic "failed" message. Reimporting the same file produces the same error. This blocks the user from playing because TAC's stock keymap doesn't match Smart Tool's customised layouts.
- "It did import failed for me / it keeps failing import" — caesarsalad.
- "Failed diyor" — hawkjrdossantos (TR).
- Reinstalling the emulator doesn't help.
- Re-downloading the keymap file from a fresh source doesn't help.
Root cause: TAC's keymap database has a corrupted state from a previous failed launch or a partial Apply that left lock files behind. The next Apply Keymap operation runs but TAC's DB rejects the new entries.
Solutions
solution #537
Run "Restore DB" before applying the keymap. Per leonmaxitv1's canonical fix sequence:
- Open the Smart Tool.
- Click Restore DB (this resets TAC's keymap database to the bundled defaults).
- Wait for the success log line: "Settings have been replaced with the bundled defaults."
- Click Apply FPS.
- Click Apply Keymap again — it should now succeed.
The Restore DB operation clears the corrupted DB row that was rejecting the import. After restore, the apply path runs cleanly.
solution #538
Make sure the keymap file matches the game mode. TAC's keymap files are per-mode (.txt files for Multiplayer / Battle Royale / DMZ — they don't share the legacy GameLoop's monolithic XML format). Importing a "DMZ" keymap into the Multiplayer slot fails silently with the same "failed" message. Match the file to the mode you're applying it to.
solution #539
Kill all TAC processes before retrying the import. Smart Tool's Apply Keymap can fail if a CODM process is still running and holds the keymap file open. Open Task Manager → end every "tac", "gameloop", "AndrowsConnect" process → retry import.
Comments (0)
Sign in to_leave_comment