WolfenswanFA

We're experiencing an issue where settings modified on the server (ASR in this case) aren't properly stored server-side and reset after every mission change. Should the settings be written directly into the server's profile file? I'm not sure where to start to pin down this issue.

Hm as I assumed. Then it's def. not being written properly. Guess I'll best head to the CBA thread for further help.

Then other options would be reset as well, no? But yeah, it's possible that something isn't set up properly wrt the profile. In which file should the CBA/ASR settings be written?

@Twakkie In the ARMA3 main menu, at the bottom right, which version of ASR_AI3 is shown? For some reason I still had ASR 0.9.29.00 for a while despite using the latest steam version, I had to do a manual purge to get it working. @Robalo We're now running into an issue where the server-ASR settings reset after changing mission. Filepatching is allowed on the server.

Did you get my PM regarding the steam version? It seems to have been a steam caching issue, after manually purging my local copy and forcing a reinstall it works fine. Regarding the userconfig I asked as those values are still there but commented, without further comment whether they are legacy or can still be used. Cheers for the update wrt to CBA, that'll help a lot. As for the logged in admins: It doesn't concern me much as we are a closed community, but I can see it creating a headache for public servers. That's why I think a way to enforce settings via userconfig would be appreciated. Anyway, thanks for the work you're doing.

I'm only getting an empty addons field when logged in: Using latest CBA & ASR, both on server and client. Difficulty is Custom (forced). Edit: Found the issue, apparently the steam workshop version I have is still 0.9.29. I'm not sure if this is an error on Robalo's end or steam's. Further question: Do the commented lines in asr_ai3_settings_ss.sqf still affect ASR_AI3 settings when uncommented? While I think the new in-game menu is nice, I'd much prefer to have an editable server-side file as in prior versions.Having to use the in-game menu adds several hoops to what used to be a simple & straightforward process and, most importantly, it allows logged-in admins to fuck with your settings.

This is preference of course, but I think the green/olive hellcat suits (paramilitary) Syndikat very well. Furthermore, Syndikat should be given armed offroads in a suitable color. Most of the FIA colorings are a bit too bright for Tanoa.

https://docs.google.com/spreadsheets/d/19bQPTj6_AGbehZGVd4AoxtWgpXmS60mKelLgHu_zkZA/edit

Did you consider that this might be a hardware issue? Maybe try running a MemTest. How are the SMART values of your HDD? Tried installing it to a different drive? This only happens if you try to do anything multiplayer related? Only hosting or joining as well?

This isn#t directly APEX related but given that weapon mass is being tweaked: Is the Cyrus supposed to be so heavy? It has 360 mass compared to the 160-220 of most other DMRs. That makes it heavier than the SPMG .338 and almost as heavy as the Navid.

Weapons, Magazines, Items, Armor, etc.: https://docs.google.com/spreadsheets/d/19bQPTj6_AGbehZGVd4AoxtWgpXmS60mKelLgHu_zkZA/edit?usp=sharing

It appears that using #missions to return to the mission lobby reverts disableChannels[]= settings to default values until the server is restarted. Nope, that's not it either. I'm still seeing either all or only a few players being able to use disabled channels but no good reproduction yet.

The autoreport issue seems to have made a comeback. In short: We are using the "custom" difficulty with autoreport set to 0. However, player characters are still calling out spotted enemies. All other values work as expected.

This feature went live with APEX but I can't find any documentation on how to enable it. Is it a server.cfg setting, a difficulty value... etc? Cheers

So, how do you enable the new indicator for who's placing markers?