When a player with latest Developper version from steam joins the server as an JIP player. He first is not able to see any playable slots on the lobby.
Second he must press enter to start loading the mission. While the JIP player is loading mission, everyone else turns into a seagull.
Yes. I used the developer build of the game and have recently been the cause of this seagull bug on the servers I've joined. I tried changed back to normal and I were able to join games as usual.
There is an sollution.
Server host must use the latest dev version and force players to use it also.
requiredBuild=xxxxx; is the command to use in server config.
https://community.bistudio.com/wiki/server.cfg
Then player must also connect using the latest version.
Yeah
As soon as i changed back from developer build it worked fine till someone tried to join every 5 minutes or so and turned us all to seagulls
I can confirm this, as posted in the Arma3 server chat and the BIF.
Alltough I can't confirm requiredBuild as a fix since that won't work for us.
@SGTIce it's not very entertaining, as nearly every server is suffering from this making multiplayer just about entirely broken.
no verifysignatures=2 only applies to mods.
you must use requiredbuild=*working build number*
Well one way of solving this is using the same build as any other when playing MP. It just makes sence... Not all are using devbuild and not all servers are devbuild. You wouldn't be able to play if you had v1.25 and the server had v1.1, now would you?
can someone please make a video on how to fix this problem that I am having! Go to multiplayer and pick a server and then the next page where you pick your class is all blank and can't play multiplayer! I can't play multiplayer at all and can't find a solution and the solution above is to complicated to follow instructions and so it would be easier to be shown in a video how to fix this problem! Thank you!
Aliendistrict51, not everything needs a video. This is a simple problem caused by the server and client not running the same version. Play on servers with the current version. Every time you try play on a server with the old version, the thing you describes happen, plus everyone on the server turns into seagulls (birds).
quote: Bumgie: "Among arma games its very uncommong that beta patches dont work backwards "
Congrats BI forcing everyone through steam...
Maybe I am to stupid, but is there anything I can do as a Steam user to change the version of Arma 3 I am running? Thx for your advice
so best workround is o update the Server to Devbuild and to force everyone connect to the server with a dev build?
Nobody is being forced to do anything...You can choose which one you want by right clicking on Arma 3 and and going to properties and to beta patches.
@76. You really should spent more time focusing on your current customer base instead of coming in here to troll. We all know Origin pales in comparison.
And for future reference. The correct wording is requiredBuild="102980";
And this was tested. IT will not work today as the patch was rolled back.
Sorry for the confusion.
And crashtheface. "no verifysignatures=2 only applies to mods." is not true. This caused players who had the previous version to get a lot of arma3 pbo related errors and be kicked from the server.
Astaroth:
There are still players playing mp using the now removed version called 102980.
This is presumably due to steams offline mode not updating it or something else.
Meanwhile servers are unable to use the requiredBuild="102980"; command to unallow any players from joining because servers have autoupdated to the previous dev version.
What you have effectively done is made all efforts to circumvent this seagull error impossible.
Please fix it quicly.
"Meanwhile servers are unable to use the requiredBuild='102980'"
Why would you want to prevent people from testing newer builds???
Because some people crash when running the dev build. The whole point of the dev build update is to crash test the build before it goes live. It's *supposed* to be unstable.
Well figure this then, if every server (or a majority of servers) restrict to only stable, no clients can be stress tested easily. Hence, the final product will then be subject to (more) bugs not found.
If the bug only crashes the client running the developer build, I see no reason why to restrict them from joining a server.
The rule you presented is not justified. Or, sort of like saying; "I'll spend your money for you, because I'm afraid you might not spend it correctly!" ;-)
A better rule would be, if a client version ever does crash a server, then use a rule to specifically rule-out allowing that specific version. But until then, I would wait until evidence is seen.
Another scenario, I'd love to toss all the stupid people in jail, but some won't let this happen. :-/