Settings

Miscellaneous ▸ Settings manages language, theme, AI providers, paths and advanced options.

Language

The interface language changes instantly from Miscellaneous ▸ Language. Six language packages ship in the repository:

tr · en · es · nl · th · zh_CN

The interface language and map-name translation are different things: the interface comes from the settings, map names from Miscellaneous ▸ Translate Map Names.

Themes

The default theme is the MRC palette: dark background with green and orange accents. Other palettes are available in the ColorThemes list.

A theme change is applied immediately: window chrome, waveform view, curve colours, chat bubbles/panels (including the guided-workflow cards) and map rows are repainted. Labels such as From hexdump cursor are re-coloured as well.

Colours

Every theme colour under Settings ▸ Colours/Theme is editable with a visual colour picker. A new Comparison Delta Colors group selects the increase (warm) / decrease (cool) delta colours. The background colour of the Overview / minimap strip right of the hex view is set in the same dialog.

User themes can be saved, renamed, deleted and exported/imported as .mtrtheme files.

To create a custom palette, edit mrcSignature() in appconfig.cpp and rebuild.

Map heat display

The map-editor grid and both 3D surface views share one heat palette, chosen under Settings ▸ Map heat display:

Palette	Character
MRC	Default: navy → teal → green → amber → coral
Viridis	Perceptually uniform, colour-blind friendly
Turbo	High-contrast rainbow
Grayscale	Grey tones for print / e-ink
Classic OLS	Classic blue → green → yellow → red

The delta threshold sets what fraction of the map's largest change the 3D delta view should ignore (0 % shows everything). While the delta view is active a red/blue difference scale (Δ Mod−Ori) is drawn in the corner.

Keyboard shortcuts

The Settings ▸ Keyboard Shortcuts… dialog edits QAction shortcuts: a conflict warning appears when a key is already taken, Reset to defaults restores factory values. Preferences are persistent.

The new grid and navigation keys ship as defaults and can be changed in the same dialog:

Shortcut	Action
M / W	Widen / narrow the columns in Text and 2D
Ctrl+← / Ctrl+→	Shift the origin one byte left / right
F / Shift+F	Next / previous map
P / T	3D Preview / Text view
K	Selection → Map
Ctrl+B	Optimize value range

Column layout (shared Text / 2D grid)

The Text and 2D views share a single column layout: M/W change the column count and Ctrl+←/Ctrl+→ change the origin. In 2D the column boundaries are drawn as line-break guides (every 4th is major), and you can drag a guide to change the column count directly. The layout is kept for the session; Selection ▸ Support map selection finds the most likely column + origin for a selected range.

The 2D curve style is set by the Style selector in the map editor: Classic (default), Columns or WinOLS; Reset to defaults restores Classic. The Column guides button in the workspace 2D view shows/hides the shared column guides; the preference is kept between sessions.

Toolbar customisation

Right-click a toolbar and choose Customize Toolbar… to pick which actions are visible; preferences are persistent.

3D preview theme

View ▸ 3D Preview Theme selects the render theme of the floating 3D Preview window: Dark, Blue Mesh, Green and White. The choice is persistent and independent of the map heat palette (a separate surface colouring).

ECU presets and workspace layouts

• ECU presets: Project ▸ Apply ECU preset… reads the JSON presets under data/ecupresets/; the MTR_DATA_DIR environment variable can point at a custom data root. Presets fill empty project fields only, show a checksum hint and flag unverified entries with a warning.
• Layout presets: Window ▸ Save Layout as… stores the current dock arrangement as a named preset (key ui/layouts/<name>); restore it from the Restore Layout submenu and remove it with Delete Layout….

Data root, knowledge base and offline translation

• Data root: the files under data/ (ECU presets, ecukb/, tuningops/) are read next to the application; the root can be relocated with the MTR_DATA_DIR environment variable. data/ecukb/mtr_ecu.db (ECU/vehicle/DTC knowledge base) and data/tuningops/*.json (maintenance operations) are optional; when the file is missing, DTC Lookup and Maintenance mode silently disappear.
• Local AI knowledge base (RAG): when data/ecukb/mtr_rag.db (SQLite FTS5) is present, the assistant appends the knowledge-base excerpts closest to your latest message to the prompt and offers the model a read-only kb_search tool. It is entirely local and uses no network. Without the database the assistant behaves exactly as before.
• Offline map-name glossary: map-name translation first consults the built-in automotive acronym glossary (e.g. egr, lambda, ivvt, n_max); the Fast engine uses the glossary + Google chain, the Smart engine uses the selected AI model. Results are cached in the mapnames database.

Checksum (export)

With Project ▸ Correct checksums on export enabled, the checksum blocks detected when exporting a ROM are corrected automatically on the exported copy only (the project ROM is unchanged). The preference is stored under checksum/autoCorrectOnExport and persists between sessions; when it is off the correction asks before writing.

AI providers

Field	Meaning
Provider	Chosen from the list
Key	Provider-specific, stored locally (on Windows encrypted with DPAPI, bound to your user account)
Base URL	Optional, for OpenAI-compatible endpoints
Model	Chosen from the list, ⟳ refreshes it
Effort	Thinking budget sent to the model

Models are fetched live from the provider's /models endpoint. A warning is shown for free/trial models.

Paths

Application data lives in the operating system's standard location:

Platform	Location
Windows	%APPDATA%\MRC\MRC Tuner Studio
Linux	~/.local/share/MRC Tuner Studio
macOS	~/Library/Application Support/MRC Tuner Studio

That folder holds projects, autosaves, themes, the translation cache (mapnames.db) and the chat history. You can open it from the settings.

Auto save

With Auto Save enabled, edits are written after a configurable idle time. Temporary files go to autosave/, so data survives a crash.

Advanced

• UI scale — interface scaling on high-DPI displays.
• Defaults for byte order and data width.
• Clear translation cache.
• Debugging: builds with MTR_DEBUG_RPC=ON enable an in-app TCP channel and a file log; you can quote the relevant section in a bug report.

Configuration file

Settings live in the QSettings store under MRC / MRC Tuner Studio. If you have to edit them by hand, close the application first; the file is read on the next start.