This will solve only ONE problem at the loading screen. If this fix doesn’t work for you, then check the log files to see if there is another problem occurring that is to do with the connection itself.
So this fix won’t work FOREVER because Garry will eventually take down the webclient. However, here is the fix:
- Open up the client (for the webclient, open the browser you want to use), we will call this the “play” client
- Open up a web browser (if you are using Chrome for step 1, open up Firefox, and vice versa, if you are using the Steam client then Chrome or Firefox will work choose whichever one you want) and make sure that it’s cache for PlayRust.com is clear (you will be wanting to have to redownload the packages), we will call this the “dummy” client.
- Go to the server list for both clients.
- With your “dummy” client from step 2, click on whichever server you want to join and let the Unity webclient start up and start downloading the Rust packages
- With the “play” client you want to play in, click on the same server which you clicked on in step 4
- Wait for your “play” client to load up and get in game, then close the “dummy” client.
This should fix your problem. What the problem ends up being is that ONCE you have downloaded the Rust packages and go to “connect”, the game client opens up a socket but the connection gets terminated at some level but the game fails to realize the connection is gone.
By using a “dummy” client that redownloads all the packages, it maintains the connection which allows the “play” client to piggyback data through the connection until it has loaded into the server, at which point the “play” client’s connection is stable and won’t hang up on its own. That is when you can close the “dummy” client (which cancels the download of the Rust package into the dummy browser).
I am not really sure why this type of problem occurs but it happens in a LOT of places around the internet. I am not sure how to solve the issue as I don’t do internet programming at the application level well enough to know. Hopefully Garry has a better solution or can fix it but this is a work around for those who have had this issue.