Troubleshooting¶

Maps show wrong values¶

Cause: wrong scaling or wrong base address.

Open Map Properties and check factor and offset.
If you imported from A2L, verify the base address — a wrong base opens every map in the wrong place.
Compare a few cells of a map you know by heart.

A map cannot be found¶

Try name patterns in Find ▸ Map (DKAT*, *LDR*).
Scan the whole ROM with Miscellaneous ▸ Auto-detect Maps.
Without an A2L, map boundaries simply are not recorded in a raw dump; if you know the address, define the map through Map Properties.
Find ▸ Similar Files can locate the same map in a similar ROM so you can carry the address over.

Checksum modules do not load¶

On Windows, make sure ChecksumDLL sits next to mtr.exe.
Install the Microsoft Visual C++ 2005 SP1 (x86) runtime.
checksumhelper.exe may be missing; fetch it again.
On Linux/macOS there are no modules; only built-in MED17/EDC17 works.

The ECU rejects the file¶

Check checksum validity.
If CRCs are valid, the ECU's signature/integrity check may have engaged; that has to be verified with an external tool.
Make sure this really is the right ROM variant (the same map name can live at a different address in another software version).
If the A2L base address is wrong, the maps may have been written to the wrong place.

The AI assistant refuses to write¶

Check the permission mode: in Plan mode write tools are locked on purpose. Switch to Ask or Auto for write requests.
Narrow the request: "increase rows 3–7 of map X by 5%".
Is the provider/model reachable? Refresh the model list with ⟳ in Settings ▸ AI.

Cannot connect to the AI (400 / 401 / 403 / 503)¶

Code	Meaning	Fix
400	Request format	Verify the model supports this endpoint
401	Key/validity	Check the key and the base URL
403	Access restricted	Your free-model quota may be exhausted
503	Service unavailable	Try a different model or provider

A file will not open¶

Check the extension: projects must be .mtrp.
If the file is open elsewhere it may be locked — close the program and retry.
Windows Defender or your antivirus may have quarantined it.

Translations come out incomplete¶

The chain Google → Google (Chrome) → MyMemory is tried in order and the results are cached. Clear half-finished translations with Miscellaneous ▸ Clear Translation Cache and try again; you can correct results in the preview table.

The interface feels slow¶

With very large projects (tens of thousands of maps), narrow the Map Selection panel.
Closing the 2d waveform view reduces memory use.
Without a GPU driver the application falls back to a software rasteriser; a driver update makes a noticeable difference.

Preparing a bug report¶

Describe the steps to reproduce.
Give the ROM size and the map name (do not attach the ROM).
State the version and operating system.
Attach the relevant lines from mtr.log.
Never share API keys.