Getting started

Supported software

• Source: Blender 5.2 LTS and 4.5 LTS.
• Targets: Unreal Engine 5.8, 5.7 and 5.6; Godot 4.7 and 4.6; Unity 6.3 LTS and 6.0 LTS, through FBX.
• Other versions of Blender: FixMyMesh still runs, on a best effort basis, and the start screen tells you plainly that the results are untested. Blender older than 3.5 is refused.
• Other versions of a target engine: they cannot be tested yet. The application tells you which version it found and which ones to install instead.
• System: Windows 10 or 11, 64 bit.
• Interface languages: English and French, for now.

FixMyMesh drives the engines already installed on your machine. It does not bundle Blender, Unreal, Godot or Unity, and it does not install them for you.

Tell FixMyMesh where your engines are

FixMyMesh never searches your computer on its own. Open Settings: the Engines section has one row per supported version.

• For each version you use, give its folder: type it, or click Browse. FixMyMesh says what it found there, for example "Found: 5.8.2".
• Or click Search this machine: FixMyMesh then looks in the usual places (Epic Games Launcher, Unity Hub, PATH, Program Files) and fills the empty rows. Check them.
• Click Save.

You do not need every engine: the application only offers targets for the engines you configured.

Your first test

1. On the start screen, choose a .blend file, or a whole folder of them.
2. Tick the targets you deliver to.
3. Keep the default preset, or pick the one that matches your trade.
4. Click Test my asset. Your asset is exported, then really imported by each engine, and progress shows per object and per target.
5. Wait. A first run is slower, because the engine has to start and build its own caches.
6. Read the report.

Nothing is sent anywhere: the whole run happens on your machine.

Reading results

The result screen is a matrix: your assets down the side, your targets across the top, each cell showing the worst finding for that pair. Click a cell for the detail. From least to most serious:

• PASS: nothing to report.
• INFO: a fact worth noting, with no consequence for the delivery.
• WARNING: something changed. It may be harmless, and the report says what changed, by how much, and the likely cause.
• ERROR: a real defect.
• CRITICAL: a blocking defect, such as an import that failed outright.

Blocking issues, when there are any, come first. The fidelity score is never shown alone: each category is listed with its own percentage and weight. Source advisories, problems already present in your .blend whatever the target, have their own panel. Switch between Simple, Detailed and Expert at any time; Expert also shows the raw measured values. Export HTML report writes the whole report as one file.

Every number is a measured difference between the Blender source and what the engine actually imported, not a prediction made from the scene.

Presets, folders and the visual check

• Presets decide what counts, how strictly, and what blocks a delivery. Eight are shown first, from the everyday check to a strict technical artist profile; the others are behind "More presets".
• Folder mode: drop a folder instead of a file. Each engine is started once for the whole folder, and one asset that fails does not stop the others.
• Visual check: optional, off by default. It renders the source and each target under the same conditions and compares them. It is the only check that uses the graphics card.

Repair and retest

When a known cause has a known fix, FixMyMesh proposes a repair plan in three parts:

• Safe fixes: nothing else changes in the delivered result.
• Fixes that need your confirmation: each one is applied only if you tick it.
• Settings to change on the target side: they live in the engine project, so FixMyMesh never changes them; it gives you the text to pass on.

Repairs are always applied to a copy of your Blender file, never to the original. A repair that makes things worse is rolled back. Then test the repaired copy against the same target: the point of the loop is the confirmation, not the suggestion.

Licensing

Your license key looks like FMM-XXXXX-XXXXX-XXXXX-XXXXX and is emailed at purchase. Enter it once in the application: it is activated over the internet and kept in the Windows Credential Manager. The application then keeps a signed offline certificate, valid 30 days and refreshed silently in the background whenever you are online, so it keeps working without a connection.

• Free trial: 3 real tests against an engine, no credit card. A test counts only when an engine actually runs.
• Individual: one user, up to 2 machines.
• Studio: 5 seats, up to 10 machines.
• Moving to a new machine: in Settings, License, click Deactivate this device (this needs a connection), then activate the new one.

Command line

The installer can add the fixmymesh command to your PATH. It runs the same tests as the application (fixmymesh test, fixmymesh repair, fixmymesh report), prints JSON with --json, and returns exit codes a script or a continuous integration pipeline can use. It follows the same license rule as the application.

Troubleshooting

An engine shows as missing

Give its folder on the row of that version in Settings, or click Search this machine, then Save.

The engine does not start

Check that the engine launches normally on its own first, and that the folder given in Settings is the right installation.

The first run is very slow

Expected. Engines build caches on first use. Later runs are much faster.

One target failed, the others look fine

By design, a target that fails never takes down the others. Its own detail says what the engine reported.

A result looks wrong

Use Export for support in the application and send us the package. By default it holds the report and the logs, not your .blend, and your Windows user name is replaced by a placeholder. A measurement we cannot reproduce is a bug we want to see.

Lost your key?

This page is the short guide. The full user guide ships with the application, and what changes in each release is listed in the changelog.