Def Jam Recomp troubleshooting
Symptoms matched to fixes from the release notes and guides, the known issues of the current release, and the reports still open.
- 20 fixes
- 15 open PC reports
- Updated for v1.1.1
Many problems reported on the trackers have been fixed in a later release, so the first step is always to update to PC v1.1.1 or Android v1.4-FG. The table maps symptoms to the README, the install and input guides and the release notes.
Common errors and fixes
| Symptom | Cause and fix |
|---|---|
| “Windows protected your PC” (SmartScreen) | The app is not code-signed yet. Check the SHA-256 on the download page, then More info → Run anyway. |
| macOS says the app cannot be opened | Choose Done (not Move to Trash), then System Settings → Privacy & Security → Open Anyway. Once only. |
| Update or repair stops with “Access is denied” on Windows | Fixed in v1.1.1 (#207). If an old shortcut still blocks it, close the app and any background DefJamLauncher.exe, open DefJamRecompiled.exe directly and choose Repair / Update game. |
| The app refuses my copy | Only the USA Xbox release in the supported dump manifest works; PS2 and GameCube copies cannot. Drop your default.xbe into the SHA-256 checker to see whether it is the supported one. |
| Setup says there is not enough space | It needs about 12 GiB working space plus your copy and 1 GiB (up to 15 GiB more for textures). Free space or Change locations, then Recheck space. |
| Setup cannot build on Windows | Microsoft’s C++ Build Tools are missing: tick the offer to install them in the last setup step, and allow the Windows prompt. |
| Linux or Steam Deck never offers an update | Installs from 1.0.0 or the v0.13.0 Linux setup look for old file names. Download the current AppImage once and open it. |
| A gamepad is not seen | Look for [INPUT] … pad(s) found in logs/run-*.log.err; close Steam’s controller layer, which can hide pads. |
| The keyboard is an extra controller | Set keyboard_player = off, or merge into player 1. |
| No rumble | If the pad does not buzz on connect, try backend = xinput or another cable; if it does, raise rumble_floor and rumble_min_ms. |
| Stick drift | Raise left_deadzone / right_deadzone. |
| Fights judder like 30 fps | Fixed in 0.12.3 (#140). Update. |
| Crackling sound | Fixed in 0.9.3 (#30). Update. |
| Widescreen menus flash black side bars | Fixed in 1.0.0 (#141): the texture memory setting reaches the game again (2048 MiB by default). |
| Combo call-out splits apart in widescreen | Fixed in 1.0.0 (#196). |
| Original Xbox saves show “Damaged game” | Imported profiles were rejected by the save signature check; closed on the tracker (#154). Update to the newest release. |
| The disk keeps filling up | Each Update or Repair keeps another ~600 MB build in the install folder (open, #180). |
| Android: “default.xbe not found” | The extracted disc must sit in Internal storage/DefJamFFNY/game/ with default.xbe directly inside, and the app needs storage permission. |
| Android: black screen with sound | Try the launcher’s Fix Mali / PowerVR options, then the hakuX mode (v1.4). Black screens on Helio G25 and P22 are still open (#21, #22). |
| Android: online lobby rejects the client | Open (#19): the outside server may require a newer client. Online is not guaranteed. |
Known issues in v1.1.1
- The Story Learn Moves list draws grey and light bars behind its rows (#181), which may or may not match the console.
- When the Story map pans to the gym or the barber, the Shop District heading can sit behind MAP or move off the top.
- Memory growth over long sessions is under investigation (#166), as are plain fight replays that differ on the Steam Deck (#98).
- Each Update or Repair keeps another ~600 MB build (#180).
- Network multiplayer is not supported; frame rates above 60 fps are future work.
Open PC reports
Issues open on github.com/vyanhursky/DefJamFFNY-recomp/issues among the most recent on November 9, 2026 (21 open issues and pull requests in total). Several are the maintainer’s own work items. If yours matches, add to it instead of opening a new one.
| Issue | Title | Opened |
|---|---|---|
| #189 | Windows setup: build without Microsoft's Build Tools (toolchain spike) | November 5, 2026 |
| #188 | Setup: say what a wrong dump file is, and what to do, as soon as it is chosen | November 5, 2026 |
| #187 | Setup: cache compiled files (ccache) so updates, repairs and retries rebuild only what changed | November 5, 2026 |
| #181 | Learn Moves: move rows now draw grey/light background bars (story-tour 13s/23s baselines differ) | November 4, 2026 |
| #180 | Reduce disk space used by the game install, data folder and HD textures | November 4, 2026 |
| #178 | Brazilian Portuguese pack: which PS2 translation does language-packs.md mean, and who is the author? | November 3, 2026 |
| #175 | test(reports): record the compiler/toolchain used for the tested build | November 3, 2026 |
| #173 | test(scenarios): report existing identity checks and final menu transition | November 3, 2026 |
| #172 | test(harness): validate the intended Story profile before running routes | November 3, 2026 |
| #169 | Music modifications | November 2, 2026 |
| #167 | very difficult to update | November 1, 2026 |
| #166 | Investigate cross-platform regression memory-growth limits and HD scene-transition allocations | November 1, 2026 |
| #165 | My Controller PC Ucom controller doesn't work in-game, yet the game detects it. | November 1, 2026 |
| #157 | quiver setup box for the def jam game | October 31, 2026 |
| #120 | Add "Quick Rematch" capability to pause menu or key binding | October 26, 2026 |
How to report a problem well
- Update to the newest release and try once more.
- Note your version, system, CPU/GPU and controller, and the exact steps.
- Copy the relevant log lines (setup log or
logs/), with personal paths removed. - Open an issue with the form at
github.com/vyanhursky/DefJamFFNY-recomp/issues/new/choose, or atgithub.com/contatg/Def-Jam-Android-Native-Port/issuesfor the Android port.
Never attach game files, saves, memory dumps or F9 bug bundles, and do not ask for game files on the trackers.
Frequently asked questions
What do I attach to a Def Jam Recomp bug report?
Your version, operating system, CPU and GPU, controller, the steps to reproduce and the relevant log lines, with personal paths removed. The project asks you not to attach F9 bug bundles, game files, saves or memory dumps. For setup problems, include the setup log (Open log).
Where are the logs?
Use Open Logs on the app’s Home screen, or Maintenance → Copy path. Input problems are written to logs/run-*.log.err. On Android the log is DefJamFFNY/defjam-native.log, replaced on each launch, so copy it right after a failure.
How do I rebuild the game from scratch?
Help → Repair or rebuild. Rebuild builds the game again from nothing; saves and settings are kept.
Will updating break my saves or mods?
No. Update game rebuilds from your copy and keeps saves, settings and mods, and the previous build stays playable until the new one is ready. Saves made with 1.1.0 stay readable by earlier versions and the original game.
Where do I ask for help?
Bugs go to the GitHub issue tracker of the project concerned. The PC project also has a Discord for conversation and setup help, linked from its README; never share game files or dumps there.