UTTORI ASM · IN DEVELOPMENT

ares runtime

Install a matching ares runtime and connect it to live debugging.

The sidecar requires a separately built ares runtime with the capabilities and hashes declared by its runtime manifest. Stock ares is not a compatible debugger runtime. Native validation has been performed on macOS. Linux and Windows native-runtime validation remains open.

Configure a runtime

In VS Code, run Assembly: Configure Emulator Runtime and select the matching executable, runtime directory, and ares-runtime-manifest.json. Restart debugging after changing the runtime.

Desktop launches honor Paths/Saves in the selected runtime's settings.bml; when unset, ares stores SRAM and numbered save states beside the ROM. When staging a replacement runtime, retain that setting so the same saves remain visible. The launcher does not override the desktop save path or relocate existing files. See the editor guide for launch settings and the sidecar README for standalone invocation.

Keep the executable, required databases/resources, settings, and manifest together. The manifest binds the executable and resource hashes to the source revision, patches, and build configuration. The host verifies them before launch. Capture features require their own negotiated capabilities. An emulator's ability to run a processor does not imply debugger or capture support for it.

Native capture candidates are separate from the default runtime. Select a manifest that explicitly supports the requested capture mode and sink. An unsupported request fails.