Mercenaries 2: World in Flames Switch Port Hits v0.2.0 with CPU and Render Tweaks
Mercenaries 2: World in Flames on Switch gets CPU helper optimizations, PGO builds, and fixes for slowdowns in one tested interior.
Developer penettrator released version 0.2.0 of Mercenaries2-NX, a native static recompilation port of the Xbox 360 game Mercenaries 2: World in Flames for the Nintendo Switch.
The release focuses on CPU and renderer performance. Two CPU helper routines now have startup equivalence checks and the original code as a fallback. In isolated CPU-workload tests their time dropped by 20.7% and 28.6%. These are not whole-game FPS gains. The update also combines renderer upload and ZCULL improvements, adds bounded image and material caches, reuses staging memory, and switches to PGO (profile-guided optimization) builds.
On a Switch running Atmosphère, the port no longer applies an extra 30 FPS cap, which had slowed camera, movement and animation in the tested interior. Loading now waits for requested textures to finish before drawing, and recorded shader and pipeline variants warm up before gameplay. Unknown variants may still compile on first use, and the public ZIP contains no game cache.
How to Try It
- Use a Switch running Atmosphère with at least 8 GB of free SD card space (FAT32 works) and DBI or another NSP installer.
- Download the release files from the Mercenaries2-NX Releases page and extract the ZIP to your SD card root, so that
SD:/switch/Mercenaries2/is created. - Extract your official Xbox 360 copy of the game with extract-xiso, name the output folder
game_rootand copy it intoSD:/switch/Mercenaries2/.default.xexmust sit insidegame_root. The README lists the supporteddefault.xexchecksum. - Install the included four-core forwarder NSP (
Mercenaries2-forwarder.nsp) via DBI and launch the game from the HOME menu without holding R.
Known limitations include brief building flicker and frame drops when transitioning into new areas. The final console test of this exact release NRO is still pending, and no old/new comparison has been run. The update is available now, and the author accepts support via Boosty.
