Arma 3 Launcher Server browser unable to display required/optional mods after a certain limit
Closed, ResolvedPublic

Description

http://i.imgur.com/rEz4xZF.jpg
Seems to be a limit to how many MODS+KEYS the Arma 3 launcher can receive / process / display.
I have 28 keys on my servers Keys Folder. Loading with 28 mods it fails to display any information about mods on the arma 3 launcher.

With same keys (28) and 27 mods the mods show up all fine, and the ones not loaded show as optional (AS INTENDED):
http://i.imgur.com/QyEeXDb.jpg

I ran 28 mods without any keys and the mods showed up:
http://i.imgur.com/bWKVb0v.jpg

Now I run the SAME EXACT MODS ( same parameters ), but this time with all the keys and the mods don't show up:
http://i.imgur.com/GWHt35e.jpg

Now I remove ALL the mods and run the server with the SAME keys as previously:
http://i.imgur.com/Gv5u6gU.jpg

I feel like the launcher runs into a stone wall and can't display anything if the amount of information about the server mods is too big.
A website (battlemetrics) is able to show the mods and signatures correctly. No matter how many there are.

Details

Severity
Major
Resolution
Not Fixable
Reproducibility
Always
Operating System
Windows 10 x64
Category
Launcher
Steps To Reproduce
  1. Run ~40 mods on a server with signaturechecking enabled and the keys correctly installed.
  2. User Arma 3 launchers server browser to see information about a server.
  3. The required / optional mods don't work
  4. remove keys
  5. The mods show up
  6. remove mods re-add keys
  7. all optional show up
  8. ONLY run 10 mods and half the keys
  9. ALL SHOW UP required and optional
Additional Information

Thanks for the help. I really hope this gets fixed, WORKSHOP can be our future!

nigel created this task.Mar 7 2017, 11:27 PM
nigel edited Steps To Reproduce. (Show Details)
BISWizard changed the task status from "New" to "Acknowledged".Mar 9 2017, 8:42 AM
BISWizard claimed this task.
BISWizard added a subscriber: BISWizard.

Hello,
thank you for reporting the issue. We know about the issue, but unfortunately it can't be fixed. The issue is caused by a limit amount of data transferred from the server to clients, and as the data are transfer is handled by Steam libraries, we can't change it.

However, for the next release (1.68) we've fixed a bug if server protocol handling, that caused a) that all data were lost where there was an overflow and b) the data loss wasn't indicated correctly in the protocol and Launcher couldn't display the warning about missing data properly.

BISWizard changed the title from "Arma 3 launcher Server browser unable to display required/optional mods after a certain limit" to "Arma 3 Launcher Server browser unable to display required/optional mods after a certain limit".Mar 9 2017, 8:42 AM
BISWizard changed Severity from Tweak to Major.
BISWizard changed Resolution from Open to Not Fixable.
BISWizard closed this task as "Resolved".
nigel added a comment.Mar 24 2017, 3:10 PM

Just a small update on the issue and a fix for anyone with the same issue!

It can be bypassed by editing name in mod.cpp for every mod.
Steam seems to have a packet which will fail if it gets filled. By renamining
name = "Advanced Combat Environment 3.9.1";
into
name = "ace3";
etc. we were able to successfully run 30 mods and have the launcher display them correctly http://i.imgur.com/0uEC4YA.jpg

I wonder if it would be possible for the devs to allow for a custom mod list to be added in the server config somewhere, which the launcher would be able to read and translate into mod lists? Possibly a link to a mod preset with steamIDs for the mods together with required / optional values.

For ex, you could name a server setting called launcherMods-"http://myserver.com/mod-list.html"

renaming mods in "mod.cpp" worked for us just in some cases... we still got some missing or unkown addons in A3 launcher.

the SteamID is already listed in "meta.cpp". why the launcher doesnt catch this? and when the launcher cant find the ID, he can try to search the name then. would work much better i think.

Please BIS, dont give up so fast.

@RueLight:
When the meta.cpp file is present in the mod on the server, the steam id is broadcasted together with the mod name and it is the primary method to match the mods in Launcher (actually we've created meta.cpp mechanism only because of Launcher), heuristic matching over mod name is one of the fallback solutions.
As I said before the real issue is the limitation of the amount of data that can be transferred from the server. Renaming the mod to a shorter name reduces the amount of data that has to be transferred from the server and that increases the chance that it will fit in the packet and get through the network from server to client.

Yes, my recommendation is an option to attach an xml link to your server which will allow the launcher to grab the list of mods from the .xml (website)

So I could save a preset with the launcher and have it grabbed from the server browser. http://www.myarmaserver.com/preset.xml is a lot less data than a list of mods. Then the browser would grab the link and convert it into understandable format for the launcher.

Good luck on the issue :)

Add Comment