Guides

Engine Simulator Load Community Engines

Pull engines from the catalog, wire imports correctly, and recover from common load failures.

Last updated:

Load Community Engines

Hundreds of player-made engines exist for Engine Simulator. The easy part is downloading a file; the hard part is matching the script’s era to your Community Edition build. Early workflows forced everyone to edit assets/main.mr. Newer CE versions (document tutorials from v0.1.12a upward, with players on builds such as v0.1.14a) prefer the Load Script button and self-contained run(...) calls. This guide covers both paths and the failure modes you will actually see.

New to the app? Finish Getting Started first.

Step 1 — Use the official catalog

Browse catalog.engine-sim.parts. Pick an engine, read the author’s notes, and download the .mr (and any companion files). Place downloads somewhere obvious, such as assets/engines/community/author_name/.

Exercise normal caution with files from the internet. There are no widely known malicious engine exploits, but you should still download from the catalog and known creators when possible. Community hubs are linked from Links.

Step 2 — Prefer Load Script on modern CE

  1. Launch Engine Simulator.
  2. Click Load Script.
  3. Select the downloaded .mr file.
  4. Wait for compile/settle; watch RT/DT and retune with N + scroll if needed (Performance Tuning).

If the engine starts (or at least loads without a console/script error), you are done. Ignition is still A, starter S—see Controls.

Step 3 — When Load Script fails: diagnose the entrypoint

Open the .mr in a text editor and search for how it boots.

Pattern A — already correct

The file ends with something like:

run(
    engine: eng(),
    transmission: trn(),
    vehicle: veh()
)

or explicit set_engine(...) calls. If those nodes exist in the file, Load Script should work. If names differ, call the nodes the author actually defined.

Pattern B — missing set / run

Some catalog pages show main.mr snippets separately. The modern advice is to transplant those commands into the downloaded script (often at the bottom) rather than relying only on the global main.mr. Minimum legacy style:

set_engine(eng())
set_transmission(trn())
set_vehicle(veh())

Preferred modern style when nodes exist:

run(
    engine: eng(),
    transmission: trn(),
    vehicle: veh()
)

Replace eng, trn, and veh with the real node names from the file.

Pattern C — legacy public node main

Older packs expose main() that internally sets the engine. You can call main() after import, but updating that block to an explicit run(...) is clearer and matches current tutorials.

Step 4 — The classic main.mr import method

Still useful for banks of local engines or tools that swap imports:

  1. Copy the engine under assets/engines/....
  2. Open assets/main.mr.
  3. Add import "engines/yourfolder/yourengine.mr" among the other imports.
  4. Ensure theme/library imports such as engine_sim.mr and themes/default.mr remain intact.
  5. At the bottom, call the engine’s public node via set_engine(node_name()), run(...), or the file’s main() depending on design.
  6. Save, launch, or press Enter to reload if already running.

You need both the file path (for import) and the node name (for the call). Open the engine file and look for public node ... near the engine definition.

Built-in video / demo engines

CE ships example content under folders like assets/engines/atg-video-1/ and atg-video-2/. Use those as known-good Load Script targets when a community file misbehaves—they validate that your install works before you debug someone else’s syntax.

Common errors and fixes

ProblemFix
Script loads but nothing to simulateAdd set_engine / run(...) pointing at a real node
Node name not foundMatch parentheses call to the exact public node spelling
Import path failsCheck relative path from assets/ and filename case
Engine loads then audio diesLower simulation frequency; heavy community engines are costly
Conflicting mainsDo not stack three different entry methods; pick one clear boot path
Old tutorial vs new CEPrefer Load Script + in-file run(...); treat pure main.mr-only guides as partial

Organizing a personal library

  • One folder per author or theme (engines/jdm/, engines/v8/).
  • Keep original filenames when possible for catalog support threads.
  • Note CE version in a text file beside huge packs.
  • Zip working sets before experimental edits.

When you are ready to modify a downloaded engine, shift to Create Engines. Validate power claims with Dyno Testing.

CE vs Steam expectation setting

Community Edition remains the compatibility target for most catalog scripts today. The Steam product (app 2381500, release TBA) is the actively developed line with a newer editor and core. Some CE-era assumptions will change; follow Community Edition and Steam Status. Wishlist Steam if you want the successor workflow, but keep CE for catalog playback now.

Etiquette

Credit authors when you reshare. Do not pretend a broken port is the original. If you publish fixes (for example adding run(...)), say so in the description so the next player skips an hour of pain.

Loading engines is a solved problem once you can identify which boot pattern a file uses. Master that recognition and the catalog turns from a pile of mystery scripts into a garage.

FAQ

Frequently Asked Questions

Quick answers about setup, controls, dyno testing, and builds.

Where do I download community engines?

Use https://catalog.engine-sim.parts/ and read each author’s install notes before loading the script.

Should I edit main.mr or use Load Script?

On modern CE, try Load Script first. Edit main.mr for permanent local libraries or when a pack still expects imports.

The engine file loads but the sim has nothing to run. Why?

The script likely never calls set_engine or run(...). Transplant the author’s main.mr instructions into the file or add the correct node call.

What is the difference between node name and file name?

The file name is what import and Load Script browse on disk. The node name is the public node you instantiate inside set_engine or run(...).

Will catalog engines work on the Steam release automatically?

Do not assume perfect compatibility. CE is what catalog scripts target today; watch Steam Status for migration guidance after release.