Monster Hunter Rise on Mac: nxnative build & settings

Prepare the 16.0.2 game files

Required for this profile

Your base-game cartridge dump (.xci).
The matching 16.0.2 update (.nsp), package v2228224.
Your matching prod.keys.

Sunbreak and extra DLC

The profile’s 16.0.2 update contains the Sunbreak content data. DLC NSPs are entitlement licenses; the 252 DLC entries in the source are not 252 required content downloads just to start the game.

Add the licenses you own for the content you intend to use. Installing update data does not grant an expansion entitlement.

~/Games/MonsterHunterRise/
├─ base.xci
├─ update-16.0.2.nsp
└─ optional-owned-dlc.nsp

~/keys/prod.keys

The names illustrate the folder layout. Keep only this game’s selected update here. The source matches the base title ID and module build IDs, rather than trusting a file named “16.0.2”. A different regional ID or update needs its own verified profile.

Exact identity, build and graphics keys ↗

Build and open the Mac app

Prepare the nxnative build environment

Use an Apple silicon Mac with macOS 26.6+, full Xcode 27.1 and the Metal toolchain. Follow the nxnative prerequisites for arm64 Python 3.12+, .NET 10 and the other tools.

Use a local workspace with room for extracted data and shaders. The upstream space estimate is roughly twice the game size plus 10 GB; the actual build depends on the files and cache already present.

Use the guide source and the Rise input folder

After the fixed-source checkout, activate that build’s Python environment and run from the repository:

Rise 16.0.2 · run in the nxnative-guide checkout

source "$HOME/.venvs/nxnative/bin/activate"
python scripts/build_ipa_from_nsp.py "$HOME/Games/MonsterHunterRise" -k "$HOME/keys/prod.keys" --platform mac-app

--platform mac-app creates the Finder app. The shorter mac target is a developer host; leaving out the platform builds an iOS IPA.

Extract & mergeBase +16.0.2 update→Rewrite & shadersRegistered profile and Metal tools→Mac appIn the input folder by default

Open the completed app in Finder

Open the finished .app, choose the launch settings and press Play. You can move the whole app after completion. Keep the original input/build folders for future rebuilds.

If the build stops, use its first error and the log path it prints. If the completed app exits, open the runtime log; reinstalling build dependencies does not resolve every rendering failure.

Start with the profile, then adjust one setting

The 16.0.2 profile sets fps_target=60 and present_interval=display. Together these raise the RE Engine cap from 30 and avoid the game’s original present interval keeping it there. Keep those source keys together rather than copying only a frame-rate change.

Frame-rate target

Try the offered 60 target first. Choose 30 for a lower-power comparison or when your actual scene cannot keep a consistent 60.

Render scale

Keep the profile default for a baseline. Lower it in one step if the same scene is GPU-limited; compare image clarity and responsiveness.

Console mode

Docked and handheld can change the game’s internal workload. Record this separately from render scale when comparing runs.

Open the app’s settings window before play. If hidden, hold Option while opening the app.
Keep the initial render scale and console mode. Start a repeatable village or quest scene.
Change only frame rate or render scale, then repeat that scene.
Use Reset to tested defaults to undo window changes. Remove a conflicting env.txt override separately.

Use a reversible 30 FPS comparison

Quit the game. Keep a copy of its existing env.txt and add or change this one line in the title-ID folder below. Relaunch and repeat the same scene.

One optional env.txt line · lower target comparison

DM_FPS_TARGET=30

Remove that line to return to the profile target. A process environment value can take precedence; avoid setting the same option in several places.

Launch window, defaults and environment precedence ↗

Connect and confirm your controller

Connect the controller to macOS before opening Rise. Check the system connection first if no buttons respond.
Open the game. Confirm the left stick moves the character and the right stick moves the camera.
Use the D-pad for the item bar. The profile selects the full-controller layout; it is not the TOTK controls.txt system.
If a button feels wrong, compare the game’s own prompts and controller settings. Disconnect a second controller and retry one device before changing mappings.

The profile documents camera and item-bar roles. Its scripted Mac benchmark key sequences are development inputs, not a player keyboard-mapping tutorial. Keep motion-control assumptions separate from basic controller input.

Rise controller layout · Project input support ↗

What the 60 FPS report actually measures

Upstream 16.0.2 profile notes
Condition	Recorded result or limit
Run	180-second headless Mac runs; no displayed gameplay window.
Result	60 FPS with frame p95 around 17.5 ms, no hang in those runs.
Hardware	The report does not identify a Mac model or memory configuration.
Meaning for a player	Evidence for that test route, not a guarantee of M1/M2/M3/M4 performance or complete quest coverage.

Frame p95 is the frame-time value below which 95% of the sampled frames fell. It describes pacing in that run; it cannot identify how a different Mac or a busy hunting scene behaves.

To make a useful comparison, record your Mac chip/memory, macOS, source revision,16.0.2 build, render scale, docked/handheld mode and exact scene. Keep a 60/30 target change separate from a resolution change.

Original frame pacing and remaining work ↗

Keep saves safe before rebuilding

Finder → Go → Go to Folder · Rise core Mac-app data

~/Library/Application Support/nxnative/0100B04011742000/

Saved progress

save/ holds progress. env.txt sets optional overrides; pso_user.tsv is pipeline data. Quit the app and duplicate the whole title-ID folder to a dated backup outside the active folder.

Launch log

The latest log is below; .prev.log keeps the previous run. Keep the first failure and the scene that triggered it.

Runtime log

~/Library/Logs/nxnative/0100B04011742000.log

Keep the working app, source revision and backup before replacing anything.
Build an updated app separately. Do not combine a new game version with unrelated settings changes.
Open it and check the expected character/progress before continuing play.
For a restore, keep the current folder under another name, put a copy of the backup at the original location, and test it. Keep both until the result is clear.

These paths belong to seedds/nxnative’s core Mac app. The NX2Apple managed library has its own storage controls; do not blindly paste this path into that route.

Common problems, in the order to investigate

Wrong update, unknown build or profile mismatch

Compare title ID 0100B04011742000 and 16.0.2 / v2228224 with the selected inputs.
Keep the base XCI and only the intended update NSP together; move unintended newer updates elsewhere.
A different executable build can miss source patches even if the script derives a profile.

DLC or Sunbreak is unavailable

Separate update content from the license that unlocks it.
Confirm the installed update is 16.0.2 and add only the matching owned entitlement packages.
Do not collect all 252 listed DLC files as a boot prerequisite.

Metal, Python or .NET fails during build

Return to the nxnative requirements and the first failed dependency check.
Confirm full Xcode 27.1, native arm64 Python and .NET 10.
Retry the same input command after correcting that one failed tool.

An IPA appears instead of a Mac app

Read the exact build command.
Rebuild using --platform mac-app.
Look in the input folder or the explicit -o output path.

The game stays near 30 FPS

Confirm the 16.0.2 profile and the pair of fps_target / present_interval keys.
Look for DM_FPS_TARGET=30 in env.txt or your launch environment.
If the target is 60 but the scene is slow, compare render scale; a target does not force measured 60.

Textures, geometry or menu rendering are wrong

Retry the profile defaults and keep a screenshot of the exact scene.
The source still lists 53 geometry shaders and 121 fully dynamic handles as unsupported, plus CPU conversion for small integer formats.
A recent texture-layout change was not rerun in the recorded notes. Keep these as source limitations rather than claiming a settings-only fix.

Controller or camera does not respond

Check macOS pairing and use one connected controller.
Test movement, right-stick camera and D-pad item selection separately.
Do not install TOTK controls.txt for this profile.

The app hangs or exits after a successful build

Keep the app/source/game versions and read the title-ID runtime log.
Record the first failing scene and whether it reproduces from the same save.
Return to defaults without extra overrides; a successful package build does not establish a complete playthrough.

Back to nxnative setup and game profiles → · Browse the native Mac game directory →