Repository navigation
msr2ds 2.0.7
Windows, Linux (x86_64), macOS (Apple Silicon) and Android (arm64).
What changed since 2.0.6
Several of these come from comparing the game's renderer with Azahar's (the emulator our 1.x releases were built on), which has years of fixes for phone graphics drivers.
- Android: phones with Mali graphics (#52, #54: Unisoc T820, Helio G99 and others), where the screen stayed black while the game played on. Mali's driver sometimes ends a wait for the GPU early with an error. The game ignored that and reused memory the GPU was still drawing with. It now waits again, as Azahar does. It also no longer stalls for good when the next frame's image can't be had, and on Mali it sets the depth and stencil state the way Azahar does there. This hasn't been confirmed on a Mali device yet: please try it and attach
msr-native.logto #52, whether it works or not. - Android: Adreno 6xx phones closing a few seconds into the game (#53). Until a vertex program's translation is ready, the phone's GPU ran it through a large general-purpose shader that older Adreno drivers can't handle. On Android those draws are now shaded on the processor instead, as Azahar does. Effects may take a moment longer to appear the first time.
- Android: when the app closes while starting (#58). If a start ends while opening the graphics, the next start opens them in a simpler, safer way, one step further each time, and stays that way until the next version. The log of the start that failed is kept as
launcher-crashed.logormsr-native-crashed.logbeside the new one: please attach both. - Android: less work for phone graphics (#37). A frame's work is no longer sent to the GPU in the middle of a pass, which made a phone's GPU save and reload the whole picture an extra time: 11 passes a frame in gameplay instead of 13. Textures also skip a check most of them don't need. A read past the end of a buffer can no longer crash the GPU (
robustBufferAccess, as Azahar turns on). - PC: smoother frame pacing (#59, #49):
- With V-Sync on, frames now wait for the display unless the game runs faster than its refresh rate, as in 1.x. At 120 FPS on a 120 Hz display, a frame that arrived a little late was replaced by the next one, a visible jump when running back and forth. It is now shown a refresh later instead.
- 60 FPS on a 120 or 240 Hz display now follows the display's refresh too, instead of slowly drifting against it.
- With several monitors, the game only follows the timing of the monitor its window is on.
- Windows: PCs without a Vulkan driver (#57). The program no longer needs
vulkan-1.dllto start, so OpenGL works on graphics like Intel HD 4600 without adding one. If you copied avulkan-1.dllbeside the program, delete it. On those older Intel drivers the launcher also no longer stays white: one of the upscaler's shaders broke every shader compiled after it. - Laptops with two GPUs (#56). The game now uses the NVIDIA or AMD GPU rather than the processor's graphics, on Linux too.
PWR_VK_DEVICE=<number or part of the name>picks another. - Small rendering accuracy fixes, as Azahar does them: the alpha test compares whole 8-bit values (exact matches now pass), and the first colour combiner stage's "previous" input follows the hardware.
- Better logs when something goes wrong. If the game or the launcher stops responding for 5 seconds, or crashes, the log now says what it was doing, where the game's threads were waiting, and, for a crash, where it happened. Every 2 seconds it also says how long presenting waited.
- After the update, your graphics driver rebuilds the game's shaders once in the background at start. Effects may pop in for a moment the first time.
Planned for 2.0.8
More of what we found in Azahar, for phone graphics (#37) and Mali:
- Lighting worked out per material in advance. The world's lighting is the biggest per-pixel cost left. It currently reads its whole setup every pixel; Azahar builds a shader for each lighting setup instead.
- Clears done by the pass that follows. Phone GPUs then don't write and read back the whole picture before drawing.
- The depth format phone GPUs handle best (24-bit depth with 8-bit stencil, the 3DS's own), and full-screen effects without a depth buffer at all.
- Cheaper drawing on Mali with how Azahar reuses descriptors there.
The logs from 2.0.7 decide the order. On a phone, a log from a run at 4x (and at 1x) helps most.
Getting it
- Already have 2.0 or later: open msr-native. The Game tab offers 2.0.7: click Update now.
- Windows (x64): download
msr2ds-2.0.7-windows-x64.zip, unzip it anywhere you can write to and startmsr-native.exe.msr-native-direct.exestarts the game without the launcher, for a shortcut, Steam or a frontend. - Linux / Steam Deck (x86_64): download
msr2ds-2.0.7-x86_64.AppImage, make it executable (chmod +x) and start it. - macOS (Apple Silicon): download
msr2ds-2.0.7-macos-arm64.zip, unzip it, movemsr-native.appto Applications (or anywhere) and open it. The app is not notarized: the first time, macOS refuses to open it; choose Open Anyway in System Settings → Privacy & Security (or runxattr -dr com.apple.quarantine msr-native.app).
Native code you already built with 2.0 to 2.0.6 stays valid, the Android app's included: no rebuild needed. New players: choose your game file on the Game tab, click Build the native code, then Play.
Android (experimental)
msr2ds-2.0.7-android-arm64.apk installs over 2.0.6 and keeps its user folder (your game file, native code and saves). Everything in 2.0.2's notes still applies: Android 10 or newer on 64-bit ARM with Vulkan 1.1 or newer, the native code built on a PC with Build for Android, signed with a debug key, and no in-app update. If it runs slowly or not at all on your device, please attach msr-native.log (and launcher.log, and any -crashed.log) from the app's user folder to an issue.
Requirements for PC and Mac are as in 2.0 (Apple Silicon, macOS 13 or newer on a Mac), and since 2.0.5 a PC with OpenGL 3.3 graphics also runs the game. You need your own decrypted dump of Metroid: Samus Returns (USA).