Join Lincolnshire Links
Install the client, map and required downloads, then add the server address below.
lincolnshire.depart.cloud:57015
Choose UDP when joining For the best experience, select UDP in the Multiplayer screen’s Join via setting before clicking Join. Choose UDP explicitly, as openOMSI may default to WebSocket. Allow about 15 seconds to connect. Use WebSocket only if UDP cannot connect.
Install what you need
-
01
Have OMSI 2 installed
The Steam copy is fine. openOMSI loads your existing game, maps, buses and everything else, and ships no content of its own.
OMSI 2 on Steam -
02
Grab the latest openOMSI build
Download the latest openOMSI build and point it at your OMSI 2 folder. The client build needs to be close to the server's.
Download openOMSI -
03
Install Lincolnshire V5 and its required downloads
Download Lincolnshire V5 from Fellowsfilm. Install the ‘Required Downloads’ shown at the top of the Fellowsfilm page, and follow the included readme. If it says "Download Disabled", sign in to Fellowsfilm; you can use Google. Open openOMSI’s Mods tab and drag in the map archive, following the readme for its required downloads.
Download from Fellowsfilm -
04
Add the server and take a slot
Add lincolnshire.depart.cloud:57015 in the openOMSI Multiplayer screen. Set Join via to UDP before clicking Join, choose Lincolnshire V5, let it load and pick a free bus.
Sometimes the duty list and the server's clock don't match: the list runs the whole day, first departure to last, even when it's deep evening on the server. If that's how you find it, do it in this order:
- Check the time on the server, in the Day and weather tab.
- Choose the line you like on the next screen.
- In the duty list on the right, scroll down to the server's time: pick a tour leaving in the next few minutes, or one that left a few minutes ago if you're running late. Click it and run that one.
- If that tour has nothing left to catch, choose another tour on the same line.
Troubleshooting
Check the status page first. If the server is online, connect to lincolnshire.depart.cloud:57015 using UDP. If UDP does not connect, use https://lincolnshire.depart.cloud for a WebSocket connection.
Check lincolnshire.depart.cloud:57015 character by character and use the latest openOMSI client. UDP is preferred; if it does not connect, use https://lincolnshire.depart.cloud for a WebSocket connection.
The server runs Lincolnshire V5. Check that you have V5 and the ‘Required Downloads’ shown at the top of its Fellowsfilm page. Follow the included readme and check that openOMSI is reading the correct OMSI 2 folder.
openOMSI takes a little while before it shows a newly added server's name and message of the day: it first works out how it and the server will talk. That pause is normal, so give it a bit of time before you decide it's stuck. If it never joins, or keeps failing, add the server again and connect via WebSocket (prefer UDP though).
A wired connection and connecting with UDP helps more than anything else. Persistent problems belong in a Discord ticket, with your client build number, openOMSI username and roughly when it happened. That's enough to look at logs.
Nothing above fit? Open a Discord ticket with your client build number and what you saw.