Join the Yorkshire server
Install the client and map, then add the server address below. This guide will help you connect and choose your first bus.
yorkshire.depart.cloud:47015
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
Install Yorkshire Counties 3.0
You’ll need the paid Yorkshire Counties add-on, rather than the older free 2.0 map. Install it and its updates through your retailer, then follow the included manual. openOMSI will load it from your existing OMSI 2 folder.
Yorkshire Counties on Steam -
03
Grab the latest openOMSI build
The client build needs to be close to the server's. Pick the newest release and you'll be fine.
openOMSI releases -
04
Add the server and take a slot
Add yorkshire.depart.cloud:47015 in the openOMSI Multiplayer screen, set Join via to UDP before clicking Join for the best experience, choose Yorkshire 3.0, 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 yorkshire.depart.cloud:47015 using UDP. If UDP does not connect, use https://yorkshire.depart.cloud for a WebSocket connection.
Check the address character by character, and that your client build is close to the server's. OpenOMSI moves fast: an old client is the most common cause. If it's still missing, restart the client. UDP is preferred; if it keeps failing, use https://yorkshire.depart.cloud for a WebSocket connection.
The server uses Yorkshire Counties 3.0. Check that the paid add-on and its updates are installed, and that openOMSI is reading the correct OMSI 2 folder. The map should be at maps/Yorkshire/global.cfg. An older free release or a modified map folder will not match.
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. UDP is preferred; if it never joins, or keeps failing, use https://yorkshire.depart.cloud for a WebSocket connection.
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.