Installing OMSI 2 freeware maps and buses by hand

This guide is for OMSI 2 players who want to add freeware maps and buses beyond the paid DLC available through Steam. By the end you will know how to find your game folder, place add-on files correctly, and work out why a map sometimes loads as empty scenery.
Two different ways content arrives
OMSI 2 has no Steam Workshop. Paid add-ons from Aerosoft or Halycon install automatically through Steam like any other DLC. Free community maps and buses are different: they come as downloadable archives, and you are responsible for putting the files in the right place yourself.
Find your OMSI 2 folder
Before installing anything, locate the main game folder. In Steam, right-click OMSI 2, open Properties, go to Local Files, then Browse. This usually opens a folder such as steamappscommonOMSI 2. Keep this window open or note the path, because every add-on folder needs to land inside it.
How a typical add-on is laid out
A single freeware add-on rarely sits in one folder. Open the archive and you will often see several folders with names that match folders already inside your OMSI 2 installation, such as maps, Vehicles, Sceneryobjects, Splines, Texture, Scripts, Fonts, TicketPacks and Trains. Each of these has to merge into the folder of the same name in your main OMSI 2 directory, not replace it.
Installing with 7-Zip
The OMSI-WebDisk community wiki describes a straightforward method for this. Follow it step by step:
- Open the downloaded archive with 7-Zip rather than extracting it blindly.
- Look inside for a folder called “OMSI 2”, or for subfolders such as vehicles or maps sitting at the top level.
- Drag only those matching folders into your main OMSI 2 folder, letting them merge with the existing ones of the same name.
- Close OMSI 2 completely if it was running, then start it again so the new content is recognised.
Do this one add-on at a time. If several archives are open at once it becomes much harder to spot which files came from where.
Read the readme first
Always open the readme before dragging any folders across. Community maps are frequently built on scenery objects and splines made by other authors, and these cannot legally be bundled inside the map’s own archive. The readme is where the author lists exactly what else you need, including any paid add-ons the map was built around. Skipping this step is the single most common reason a map fails to look right.
When a map loads as empty scenery
If a map opens but shows a flat, empty area, or large sections of missing buildings and track, the cause is almost always a missing or misplaced dependency. This happens often when a separate installer for required objects defaults to the standard Steam path while your actual OMSI 2 installation lives on a different drive. The installer reports success, but the files never reach the folder OMSI 2 is actually reading from. Check the install path of every dependency against your real OMSI 2 folder, not just the default suggestion.
Keep original folders untouched
Leave stock folders such as mapsBerlin-Spandau or vehiclesMAN_SD200 exactly as they are. When an installer or archive asks whether to overwrite a file, read the prompt rather than clicking through it automatically; overwriting the wrong file can quietly break an add-on you already have working. Also remember that Steam’s file verification can reset files inside the main folder back to their original state, which will undo changes you made to an installed add-on without warning. If you use Steam’s “Verify integrity of game files” option, check your freeware add-ons still work afterwards.
If something goes wrong
If a bus or map disappears from the menu after installation, go back to the archive and confirm each folder genuinely merged with its matching folder in the main OMSI 2 directory rather than sitting one level too high or too low. If a map shows gaps, recheck the readme for a list of required scenery packs and install those first. To undo an add-on, simply delete the specific files it added; since nothing runs through Steam’s own content system, removing the files is enough to remove the add-on.
Back up your save folder before testing anything new, and keep a copy of each add-on archive so you can reinstall or compare files if a future update to OMSI 2 moves things around.



