Search the Community

Hi everyone, Just a heads-up regarding custom difficulty settings, as specified in the .Arma3Profile, on a Linux dedicated server. Some people out there may have had problems getting these to load. At the very least I had. I did some testing and eventually got the settings to load through the creation of a custom server profile with a new name. It is quite a strange story, so I apologise in advance for approaching this from an entirely empirical perspective. I absolutely can not give any insights as to why this is working. And I am probably embarrassing myself a little with such a superficial post (BIS difficulty programmer guy, are you reading this?) - but perhaps it does help a few people out there. The problem: The Linux dedicated server would routinely ignore changes to the entries made in $HOME/.local/share/Arma 3 - Other Profiles/server.Arma3Profile. The custom difficulty could be enforced through the server.cfg but "default" values for "class CustomDifficulty" were loaded regardless1. The solution: Launched the server under a new name, using the parameter "-name=servername", then replaced the automatically created "servername/servername.Arma3Profile"2 with the user-modified Arma wiki template. Subsequently restarted the server and selected/enforced "Custom" difficulty. Example: Originally, I would launch the server via: ./arma3server -name=server -config=server.cfg -mod=@mod1;@mod2;@mod3; In this case, any user-made changes specified under "class CustomDifficulty" were not used, even when saved in a write-protected .Arma3profile. After some tinkering, the server would be launched under a new name using "-name=" - and, optionally, with the additional "-profiles=" parameter: ./arma3server -profiles=/home/apps/steam/arma3/profiles -name=custom -config=server.cfg -mod=@mod1;@mod2;@mod3; By launching the server a new folder ("/arma3/profiles/home/custom") was created in arma3 root. It contained a tiny "custom.Arma3Profile", ordinarily consisting of 6-10 lines of basic option entries (soundFX=1, etc.)2. The content of .Arma3Profile would now be replaced with a test profile using exclusively the exact example server difficulty profile template, but with all values set to 1 (or 2, if applicable) to easily check for changes. The server would then be restarted, which automatically reformatted the "custom.Arma3Profile" to this: Running a test mission at custom difficulty, all settings were loaded correctly. There was a crosshair, third person mode (yuck!), a stance indicator, and a score table. In previous tests, using the original .local/share/[name].Arma3Profile none of these options were ever loaded3. Repeating this process, a new "freshly"-named server was then created with our desired custom difficulty setup. Is anybody able to reproduce this? I would like to hear some feedback, in particular from people who tried to make changes to their Linux dedicated server .Arma3Profile. Thanks! 1 It is not clear to me where these defaults are coming from. 2 Oddly enough, the number of lines in this file varied each time a new profile is created. 3 However, changing entries within this file a second time and restarting the server would always result in reverting to the reformatted file and its settings. A new server name ("-name=custom_2") had to be created to enforce new custom difficulty settings.

Hello, seems that the dedicated server I'm running (rented from GameServers) is forcing a view distance maximum of 1500 m. I've read that is the default view distance for Arma 3 MP so this is by no means an issue with the server provider. I've come to understand that it should be possible to change the view distance the server is forcing the clients to use from the server's Arma3Profile and this is exactly what I've been trying to achieve but without any effect. Currently I've placed the following lines in the file server.Arma3Profile sceneComplexity=400000; shadowZDistance=100; viewDistance=12000; preferredObjectViewDistance=12000; terrainGrid=50; and then calling this file with the following server startup parameters: c:\path\to\arma3\arma3server.exe -profiles=C:\path\to\arma3\config -name=server -config=server.cfg Then when I join this (dedicated) server as a client the view distance is anyways capped to 1500 m and there's no difference if I as a client have set Overall and Object view distances to 12000 m. Would someone have some pointers to offer here? Is setting the view distance from the server profile supposed to work? Or do I need to begin thinking of setting the view distance on a mission to mission basis?