Jump to content

Clients Can Hear Sound & Move But Stuck On Loading?


Stoney

Recommended Posts

We can't really help without you posting your server and client rpt files, anything we do/may suggest might be in the completely wrong direction. :)

 

Please use pastebin or equivalent to post rpt files thanks :)

Link to comment
Share on other sites

One of my players pointed out something interesting. My server is running BE and when his failed to update etc he could not connect. When it updated and worked properly he could connect fine. It seems when BE is unable to update etc players cannot connect to servers running BE. Just theory but maybe this is correct?

Link to comment
Share on other sites

I had that problem. You may need to update the battleye files on your server. I did that and the fialed update message has not appeared since.

 

Just updated the arma 2 and arma 2 oa be dll files on the server and still some clients get stuck on the loading screen hearing sound etc. It's weird because it doesn't happen to everyone and the people it happens to it doesn't happen all the time. Very strange!

Link to comment
Share on other sites

At this point, I've learned this problem is related to the database being given a second ID for a player when he joins the server for a 2nd time. I just built a fresh vanilla epoch server and tried to join it twice. As expected, the 2nd time I joined it I got the loading screen with sounds only. I checked the database for player_data and saw this:

 

2d0gkza.jpg

 

So a 2nd ID is being generated for the same player when he joins the server for a 2nd time. My guess is this is what's causing this problem. My best guess.

 

For me, this problem continues to happen until both my IDs are wiped from the database and I'm able to start fresh. Otherwise, I can never play on the same server twice. It doesn't just happen to me sometimes...it happens 100% of the time.

Link to comment
Share on other sites

Yes, it's the steam community ID of the player. And yeah, I'm using the latest beta patch that only steam provides.

 

And yep, when you remove those player IDs, you lose everything and have to start fresh, but currently it's the only way to keep playing on the same server if you have to reconnect for any reason.

Link to comment
Share on other sites

When using the new updates from Steam, it changes you over to the SteamID regardless of whether you had a BIS PlayerUID already.  This causes you to start fresh with a new player.

 

If the admin knows your old BIS PlayerUID and your new SteamID they can give your old player the SteamID and delete the new SteamID entry therefore making your old character compatible with the new version of OA.  Linking the old BIS PlayerUID and SteamID to a user is not easy but BIS have now released a new command with the 125548 Beta called getplayeroldUID although no info has really surficed from them on exactly what it does and there are reports of people getting stuck on loading the mission if the server is using this command and the connecting client is not on 125548.

 

If all the clients are on 125548 then, as part of the solution, you could put a line in the player login script to getplayerUID and getplayeroldUID and dump them to the RPT file via a diag_log command but you would still have to manually change the character_data table.

 

Personally I am waiting to find out a bit more on getplayeroldUID and for 125548 to become more mainstream.

 

On the blank screens with sound but no picture, I have also got this now and then.  It seemed to sort itself out but I have been debugging my Plot for Life mod and so had realigned my character to the SteamID manually (removed the new Steam character) and a few other things so sorry but no real pointers on how I fixed it for me other than check your client and server versions match (and the clients of your userbase who are getting the issue) and try aligning their old character to the new SteamID and removing the newly created character.

 

As always, test on a non-live server first.

Link to comment
Share on other sites

Just had the issue a couple of times today.

 

In my case, looking at the client RPT file I saw the message "Mission ended".

 

In my case there was a bug in the server_monitor.sqf (part of my own code) and the errors were not reported.  Once the code was fixed the login worked fine.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Advertisement
×
×
  • Create New...