Having to revert to 1.5.6 to load in

[ravilakhani.e@gmail.com 20]

Myself and 3 of my friends are having an issue related to the eternal Waiting For Server bug that was recently fixed by Rocket. Every now and then we will still get stuck, unable to ever load in, until we revert to 1.5.6. At that point, we can load in, but are obviously out of date. Updating the game allows us to continue playing.

This process is a little tedious, so hopefully it can be investigated.

Thanks for everything, devs.

[Azelbaum 2]

Confirmed. I was able to get the same results.

Connect to Dallas 6 (and many other US servers, endless WFSR screens)

Exit Game (1.5.7)

Copy over v1.5.7 files with old 1.5.6 files

Start Game

Connect to Dallas 6

Advance into game, recieve notice of out of date files.

Abort>Disconnect>Exit Game

Copy over v1.5.6 files with current 1.5.7 files

Start Game

Connect to Dallas 6

Short WFSR screen and then right into game.

Looks like there's something for you guys to investigate here.

**Update**

Disconnect from Dallas 6

Connect to Dallas 8 - Endless WFSR screen.

Are files being updated locally from the server on connecting to a server?

**Update_2**

I repeated the process when I started running into the WFSR screens again.

Connect to Dallas 8 (and many other US servers, endless WFSR screens)

Exit Game (1.5.7)

Copy over v1.5.7 files with old v1.5.6 files

Start Game

Connect to Dallas 8

Advance into game, recieve notice of out of date files.

Abort>Disconnect>Exit Game

Copy over v1.5.6 files with current v1.5.7 files

Start Game

Connect to Dallas 8

Short WFSR screen and then right into game.

With the added step, this time, of:

Abort>Disconnect>Exit Game

Start Game

Connect to Dallas 8

Short WFSR screen and then right into game.

So, I couldn't replicate what was happening the first time, though installing the v1.5.7 files fresh seems to help. Hopes this helps someone get to play for the night or gives the devs an inroad into what might be wrong, besides getting hammered due to population.

[ravilakhani.e@gmail.com 20]

Your persistent data has to be retrieved from the hive when you connect to any server, and it's probably getting hammered (thanks Reddit) due to all the new players. Give them time to find a solution.

[Azelbaum 2]

Your persistent data has to be retrieved from the hive when you connect to any server' date=' and it's probably getting hammered (thanks Reddit) due to all the new players.[/quote']

Thanks for the info. I was asking because perhaps something is being written to your machine locally, that's causing reconnecting to servers to be an issue, or perhaps something is being written to the server off of our local machines that's doing the same.

Give them time to find a solution.

I'm not complaining, I'm trying to troubleshoot along with you. You presented evidence that suggested that simple server load isn't the only problem and decided to test out your evidence to verify what you're saying. It does look like something is there, in that installing the the v1.5.7 files fresh provides quick access onto servers that were previously hanging at the WFSR screen. If your suggestion and my testing of that suggestion helps them find a problem that's being obscured by main server load, GREAT! So my posting here isn't because I'm complaining its because you presented something interesting and trying to test it out was better than staring at a black screen.

[Misanthrope 0]

I don't believe it to be a capacity issue, as Rocket himself stated in a recent interview that the persistence server has only seen a theoretical half of the maximum concurrent connections. It does seem to be 1.5.7 related though, since the issue coincides with the release. I'm not complaining though, what Rocket has achieved single-handedly with this alpha is beyond reproach. And even though he's a BIS employee, his ruthlessness as a designer is so refreshing that BIS has definitely secured a customer in ArmA 3, and they should plaster Mr. Hall's name all over the product to take advantage of his almost limitless goodwill with the hardcore PC gamer right now. Hmm, might have come off slightly fanboyish.

Will try the 1.5.7->1.5.6->1.5.7 reversion trick though. Will report back with findings.

UPDATE: Holy hell I don't even want to understand why this works, but it does. I went from having to deal with 'waiting for server response' all day since about 8 hours ago, to jumping right in. Reverted to 1.5.6, got in game, got the waiting for server response, backed up, installed 1.5.7 code again, and got in my first server, first try. Thank you.

[ravilakhani.e@gmail.com 20]

I only meant give them time in regards to the server load.

The proposed fix was not working for my friends and I yesterday, though it seemed that everyone on every server was locked out at the same time.

[rocket 16567]

1.5.6 handled errors that it encountered very well. This was removed to an extent in 1.5.7 because it was aiding hackers. A new method has been rewritten in 1.5.8 that will help with this. We are regularly purging the database of "bad data" the constant stuck at loading is likely to be because the server didn't sync your model type properly. As I noted, in 1.5.6 where your client detected it had bad data it was acting under its own influence. This was being exploited by hackers to do a number of things, so it was removed.