Service information
Joining the network
Three things to install, one address to type, and a duty to run. If you've driven Westcountry 3 in single player, the only new step is the address.
westcountry.depart.cloud
Connect with WebSocket, and give it about 15 seconds.
You will need
Before you travel
-
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 Westcountry 3.03a
Download the base 3.03 and the 3.03a patch, both files, and follow the enclosed install guide. Older map folders need deleting first if you've modified them.
Download from Fellowsfilm → -
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
In the openOMSI client, open Multiplayer, add a server, and enter westcountry.depart.cloud. Choose Westcountry 3, let it load, then pick a free bus.
On the day
Connecting
-
01
Start the openOMSI client
The launcher opens like OMSI 2 does, and finds your game the first time. It doesn't modify the OMSI 2 installation itself.
-
02
Add the server
Open the multiplayer menu, choose add server, and paste in the address from the board above. It's saved for next time.
-
03
Choose Westcountry 3
The server is on Westcountry 3.03a. Let the map load, then keep going.
-
04
Take a free bus
Late is fine; early isn't. New drivers usually start on the 100: it's short and forgiving. The dark box above says how to land on a tour near the server's time.
When it doesn't work
Trouble on the route
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, and try connecting via WebSocket if it keeps failing.
The server runs Westcountry 3.03a exactly: base 3.03 plus the 3.03a patch. If you've modified an older Westcountry 3 install, delete the map folder and reinstall both files clean.
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.
A wired connection helps more than anything else. Persistent problems belong in a Discord ticket, with your client build number 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.