What this is

mapcreator turns a stretch of real road into a track for Assetto Corsa on PC. You pick the road on the map; a build server snaps it to OpenStreetMap, lays it over a terrain model, adds verges, trees, buildings, timing gates and an AI line, and packs it as a zip you can install with Content Manager or by hand. It's free, and it uses open data only.

Roads in Tasmania use the state's 2 metre terrain model, tree heights and building outlines. Elsewhere in Australia, a road uses Geoscience Australia's 5 metre LiDAR model where it covers the whole road, then (in Victoria) the state's 10 metre model, and the 30 metre national model otherwise, so roads away from towns come out smoother than the real thing.

Where the data comes from

mapcreator changes all of this data to build a track: it resamples, filters and smooths it, and turns it into 3D geometry. Every track carries an ATTRIBUTION.txt naming exactly the sources it was built from and how its OpenStreetMap data was selected. It also carries the road's centreline, with its heights and widths, as centreline.geojson under the ODbL, and any OpenStreetMap power lines it used as power.geojson. If you share a track, keep those files with it.

No Google, Esri, Bing or Mapbox data is used anywhere in a build.

Using the tracks

Install with the Content Manager link on your job's page, or unzip the download into assettocorsa/content/tracks. Each road can come with a layout for each direction. The tracks need Custom Shaders Patch (CSP), which most Content Manager users already have. CSP draws the trees and the water, and the tracks aren't built to work without it. They're tested with CSP 0.2.11. The tracks are generated, not hand-made: expect the odd rough edge, especially where the map data is thin.

mapcreator is not affiliated with or endorsed by Kunos Simulazioni. Assetto Corsa is a trademark of its owner. The service never runs the game; it only writes files that the game can read.

Privacy

There are no accounts, no analytics and no advertising, and mapcreator sets no cookies. Here is everything it keeps:

The server keeps no access log: it doesn't record your address or which pages you load. It logs each job's id as it's queued, built and finished.

Anyone with your job's link can see its status and download its track. If someone else asks for exactly the same road with the same options, they're given the same job rather than a second build, so they see the track name you typed.

Three other services see your request when you use the page:

Those services receive your address the way any website you load does.

Back to the map