Since the last Bis A3 update? (09/03/21) when using forcedDifficulty Custom, on our Dedicated server we no longer see waypoints, personnel markers, & mission task markers. All the other "custom" difficulty settings still seem active & working. & if you host on your own PC with same settings they all show, but NOT on the Dedicated server ?? Also have discovered tactical ping, & Commands, stance, & weapon also not showing???? Yet other settings like no crosshair & no 3rd party do still work, so it must be reading the correct file?
Description
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- N/A
- Operating System
- Windows 7
- Operating System Version
- not sure its a paid for server called Fragnet
- Category
- Dedicated Server
We have turned off the "forceddifficulty" on the server.cfg for now, selecting a default for each mission.
the server is, House Of Clowns [LOL] Connection Info 81.19.208.16:2502
Event Timeline
There are others with the same problem forcedDifficulty settings no longer working on Dedicated servers?
Would appreciate someone taking a look at this. something similar happened a couple of years ago & a bis patch fixed it.
Since the last bis/Steam A3 update on Dedicated servers with forced difficulty set, A3 is not reading the "Users\server\server.Arma3Profile" settings.
Same problem on Ubuntu 20.04. Reinstall the server and change the difficulty does not help.
Still the problem of; Dedicated servers with forced difficulty set, A3 is not reading the "Users\server\server.Arma3Profile" settings. or rather only activating some of them.
No markers showing on Dedicated servers with forcedDifficulty active, even when set to ON
After trying a number of different things I believe the problem is that, on a Dedicated server, the game in NOT reading the "server.Arma3Profile" in the path Users\server\server.Arma3Profile, but using the hard programmed default "Custom" difficulty settings instead.
Two thing would suggest that are;
A/ If you change the settings in the Users\server\server.Arma3Profile, as in, turn ON CrossHair, & first person, nothing happens they stay off.
B/ If you turn off the ForcedDifficulty in the server.CFG & an Admin selects Custom difficulty for a mission the settings are identical. as in;
1st person off, Crosshairs off, Waypoints off, commands off, tacticalping off, weaponInfo off.
stanceIndicator off.
What we are trying to get, & what did work in "Users\server\server.Arma3Profile" before the March update, & now wont was;
class DifficultyPresets
{ class CustomDifficulty
{ class Options
{
groupIndicators=0;
friendlyTags=0;
enemyTags=0;
detectedMines=0;
commands=1;
waypoints=1;
weaponInfo=1;
stanceIndicator=1;
reducedDamage=0;
staminaBar=1;
weaponCrosshair=0;
visionAid=0;
thirdPersonView=0;
cameraShake=1;
scoreTable=1;
deathMessages=1;
vonID=0;
mapContent=0;
autoReport=0;
multipleSaves=0; };
aiLevelPreset=3; };
class CustomAILevel { skillAI=0.8; precisionAI=0.4;
};
};
Got the "Welcome Message" to work or rather show by adding a time delay before the text as in "","","", "then the messages",
Still have the original problem of waypoints etc not showing with forcedcustom difficulty.
Seem to have found a solution; you have to have a named mission selected on the server in the server.cfg with the line difficulty
For example.
forcedDifficulty = "Custom";
class Missions
{
class Mission1 { template = "missionname"; difficulty = "Custom"; };
};