Jump to content
Bohemia Interactive Forums

Dwarden

BI Developer
 View Profile  See their activity

  • Content Count

    10617

  • Joined

  • Last visited

  • Medals

  • Medals

Everything posted by Dwarden

  1. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    test of 96 players Warlords : 5.62.127.2:2302
  2. Dwarden
    1.92.145690 new PROFILING branch with PERFORMANCE binaries, v04, server and client, windows 32/64-bit, included linux 32-bit server + more crash fixes (not included in 1.92.main yet) https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMclient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-184-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  3. Dwarden
    @Axebeard 2 posts above yours is exactly explained what and where in server.cfg to set
  4. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    alongside with new 1.92.145681 profiling branch binary build https://forums.bohemia.net/forums/topic/160288-arma-3-stable-server-192-performance-binary-feedback/?do=findComment&comment=3356367
  5. Dwarden
    1.92.145681 new PROFILING branch with PERFORMANCE binaries, v03, server and client, windows 32/64-bit, included linux 32-bit server + crash fixes (not included in 1.92.main yet) + new default timeout values votingTimeOut = 600; // was 60 s for voting //vote phase to 10 minutes roleTimeOut = 900; // was 90 s for lobby //role selection phase to 15 minutes briefingTimeOut = 600; // was 60 s for briefing //pre-game briefing to to 10 minutes debriefingTimeOut = 600; // was 45 s for debriefing //post-mission briefing to 10 minutes lobbyIdleTimeout = 1500; // was 300s (+5 seconds vs any of above)>defined value // lobby idling to 25 minutes + lobbyIdleTimeout supports now value of 0 to turn off timeout kicks e.g. in server.cfg : LobbyIdleTimeout = 0; //disable lobbyIdleTimeout kick + fix for kickTimeout kick due onHackedData/onDifferentData/onUnsignedData where timer from kickID 0 was used instead of kickID 3 + kickTimeout supports now value of 0 to disable kick e.g. in server.cfg : kickTimeout[] = { {0,0},{1,0},{2,0},{3,0}} ; // disable kickTimeout for all four kickID types https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMclient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-184-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  6. Dwarden
    as i explained that -1 was wrong and bugged ...
  7. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    this took longer explain https://forums.bohemia.net/forums/topic/160288-arma-3-stable-server-192-performance-binary-feedback/?do=findComment&comment=3355535
  8. Dwarden
    some update on what's being worked on ... 1. managed to find the edge case of kickID being type 0 instead of 3 it was related to https://community.bistudio.com/wiki/ArmA:_Server_Side_Scripting on* kicks WIP to get it fixed asap 2. increased the default timeouts to those values vote phase to 10 minutes votingTimeOut = 600; // was 60 s for voting role selection phase to 15 minutes roleTimeOut = 900; // was 90 s for lobby pre-game briefing to to 10 minutes briefingTimeOut = 600; // was 60 s for briefing post-mission briefing to 10 minutes debriefingTimeOut = 600; // was 45 s for debriefing lobby idling to 25 minutes lobbyIdleTimeout = 1500 ; // was 300s (+5 seconds vs any of above)>defined value server.cfg settings votingTimeout/roleTimeout/briefingTimeout/debriefingTimeout are server-side timeouts which say how long a server stays in a specific state (role selection, briefing, in-game, debriefing) before it moves to another one. Don't mistake them with "lobbyIdleTimeout" which says how long players can stay in lobby, briefing or role selection (no matter the server's state). note: - those were soft-coded prior 2016 and until recently weren't exposed via server.cfg settings - value of -1 was wrong leading to other issues, will be fixed to and not possible anymore - value 0 or lower for votingTimeout, roleTimeout, briefingTimeout, debriefingTimeout, lobbyidleTimeout will disable those settings 3. added new value to correctly switch off lobbyidleTimeout LobbyIdleTimeout = 0; //to turns off the timeout kicks yet, completely new and different usage has server.cfg setting lobbyIdleTimeout which covers how long client can stay in certain state on server e.g. covers when server has already active mission as someone JIP in to idle in lobby, roles etc. summary, the lobbyIdleTimeout is completely separate to the other timeouts, it's also agnostic to state of server, works for JIP users too
  9. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    @Anthony Mackiw cheaters report to me
  10. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    official Warlords servers were updated with server-side patch to solve some function scripting issues
  11. Dwarden
    @fourjays from what i gathered that are unforeseen consequences values 😉 it may work but who knows what those breaks (i hope they work, saves me headache)
  12. Dwarden
    @Dedmen , @LSValmont , @churrofighter , @Bosenator , @Farantis , @fourjays , @.kju in server.cfg just increase the votingTimeOut , roleTimeOut , briefingTimeOut , debriefingTimeOut , lobbyIdleTimeout beyond default values of 60, 90, 60 ,45, 300 e.g. to 65535 or 604800 seconds then also disable the kickTimeout (atm. i'm unsure if value of 0 works, needs to be tested) kickTimeout[] = { {0, 0}, {1, 0}, {2, 0}, {3, 0} }; or use 1 second timeout kickTimeout[] = { {0, 1}, {1, 1}, {2, 1}, {3, 1} }; those settings are also documented on the BIKI https://community.bistudio.com/wiki/server.cfg
  13. Dwarden

    1.90 update - Troubleshooting

    Dwarden replied to Homesick's topic in ARMA 3 - TROUBLESHOOTING

    fix what, creating any global objects in such excessive amount at same moment will cause similar problems
  14. Dwarden
    as i said before just set the *timeout values to e.g. 259200 (72 hours) or more... (note: not the kickTimeout as that're value preventing the return after kick)
  15. Dwarden
    well that workaround is unforeseen consequences (aka not what is supposed to work) so please update to the latest profiling branch / performance binaries with build >=45469 which have engine fix and recognize HC correctly
  16. Dwarden

    1.90 update - Troubleshooting

    Dwarden replied to Homesick's topic in ARMA 3 - TROUBLESHOOTING

    there is no ban for that ... he just got kicked because each launcher creates 14 global mine objects in short, stop using excessive amount of dispensers, it causes server / mp performance issues
  17. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    1.92.145649 new PROFILING/PERFORMANCE binaries https://forums.bohemia.net/forums/topic/160288-arma-3-stable-server-190-performance-binary-feedback/?do=findComment&comment=3353419
  18. Dwarden
    1.92.145643 new PROFILING branch with PERFORMANCE binaries, v00, server and client, windows 32/64-bit, included linux 32-bit server + sync with 1.92.main branch v01 skipped 1.92.145649 new PROFILING branch with PERFORMANCE binaries, v02, server and client, windows 32/64-bit, included linux 32-bit server + crash fixes (not included in 1.92.main yet) + no more headless-client kick due to idleTimeout + fixed waitUntil (performance regression) and many commands errors improved for this fix https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMclient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-184-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  19. Dwarden
    1.92.145963 is sync with 1.92.main @Farantis @fourjays it's known bug, resolved internally (will be in upcoming profiling) vs HC atm. you can set some high values in seconds those 4 (as long as you need for the session) note: something what may interest server admins, official Arma 3 servers use : Warlords: votingTimeOut = 240; //60 s for voting //alternative syntax : votingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady roleTimeOut = 360; // 90 s for lobby //alternative syntax : roleTimeOut[] = {90, 120}; // 90 seconds for ready, 120 for notReady briefingTimeOut = 240; // 60 s for briefing //alternative syntax : briefingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady debriefingTimeOut = 180; // 45 s for debriefing //alternative syntax : debriefingTimeOut[] = {45, 60}; // 45 seconds for ready, 60 for notReady lobbyIdleTimeout = 300; // (+5 seconds vs any of above)>defined value //no alternative syntax //Warlords idle set all other servers votingTimeOut = 360; //60 s for voting //alternative syntax : votingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady roleTimeOut = 540; // 90 s for lobby //alternative syntax : roleTimeOut[] = {90, 120}; // 90 seconds for ready, 120 for notReady briefingTimeOut = 360; // 60 s for briefing //alternative syntax : briefingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady debriefingTimeOut = 300; // 45 s for debriefing //alternative syntax : debriefingTimeOut[] = {45, 60}; // 45 seconds for ready, 60 for notReady lobbyIdleTimeout = 480; // (+5 seconds vs any of above)>defined value //no alternative syntax //COOP idle set combined with kickTimeout[] = { {0,-1},{1,181},{2,182},{3,183}} ; // {kickID, timeout} //kick ID (type to determine from where the kick originated e.g. admin or votekick etc.) // 0 - manual kick (vote kick, admin kick, bruteforce detection etc.) // 1 - connectivity kick (ping, timeout, packetloss, desync) // 2 - BattlEye kick // 3 - harmless kick (wrong addons, steam timeout or checks, signatures, content etc.) // timeout = in seconds how long until kicked player can return // >0 seconds // -1 until missionEnd // -2 until serverRestart? tho, for test some servers may use -2 or high value in seconds for the manual kick
  20. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    official Warlords server idleTimeout settings: kickTimeout[] = { {0,-1},{1,181},{2,182},{3,183}} ; // {kickID, timeout} //kick ID (type to determine from where the kick originated e.g. admin or votekick etc.) // 0 - manual kick (vote kick, admin kick, bruteforce detection etc.) // 1 - connectivity kick (ping, timeout, packetloss, desync) // 2 - BattlEye kick // 3 - harmless kick (wrong addons, steam timeout or checks, signatures, content etc.) // timeout = in seconds how long until kicked player can return // >0 seconds // -1 until missionEnd // -2 until serverRestart? votingTimeOut = 240; //60 s for voting //alternative syntax : votingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady roleTimeOut = 360; // 90 s for lobby //alternative syntax : roleTimeOut[] = {90, 120}; // 90 seconds for ready, 120 for notReady briefingTimeOut = 240; // 60 s for briefing //alternative syntax : briefingTimeOut[] = {60, 90}; // 60 seconds for ready, 90 for notReady debriefingTimeOut = 180; // 45 s for debriefing //alternative syntax : debriefingTimeOut[] = {45, 60}; // 45 seconds for ready, 60 for notReady lobbyIdleTimeout = 300; // (+5 seconds vs any of above)>defined value //no alternative syntax //Warlords idle set some servers may run -2 or high manual kick values (in seconds) while observing the effects note: you most likely got votekicked if can't rejoin (unless proved otherwise that there is bug)
  21. Dwarden
    there were some questions about the recent #perf_prof_branch 1.90.145620 build fix of waitUntil it fixes the situation when waitUntil statement returns nil, it got stuck on that and cluttered the script scheduler now waitUntil is aborted and the error message is displayed to the user like some examples below: `Error Type Bool expected Bool` `Error Type Any expected Bool` `Error Type Nothing expected Bool` `Error Type Obj expected Bool` etc.
  22. Dwarden
    1.90.145620 new PROFILING branch with PERFORMANCE binaries, v11, server and client, windows 32/64-bit, included linux 32-bit server + crash fixes + fixed waitUntil (performance regression) https://www.dropbox.com/sh/582opsto4mmr8d8/3BSy9PdRGm https://drive.google.com/folderview?id=0B03-H4YIbhkFMUt5RzNqZjFlNGs available via STEAMclient/STEAMcmd as branch too, read https://community.bistudio.com/wiki/Arma_3_Steam_Branches#Arma_3_Server BIForum feedback: https://forums.bistudio.com/topic/160288-arma-3-stable-server-184-performance-binary-feedback/?do=getLastComment Arma anything discord: https://discord.gg/arma
  23. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    playerID is still there just based off steamID ... anyway the wlbicu2 bans were lifted with 'benefit of the doubt' because ... (aka manual bans are always prone to possibility of false positive due to static logs limit so don't be worried much about...) feel free to continue share feedback here and if you can join us on Discord too https://discord.gg/arma
  24. Dwarden

    Warlords

    Dwarden replied to Jezuro's topic in ARMA 3 - OFFICIAL MISSIONS

    those with ban ending 'wlbicu2' best contact me via direct message on Discord (if you can, should be faster than using messages at forum)
  25. Dwarden
    @.kju while it depends on mission and server setting this is to prevent players to occupy slots in lobby such situation may lead to blocked mission-selection or mission-start or prevent those slots to be usable by active players etc. note: there's no visualization in UI of how much time the player has left. about the syntax, two integers array for setting different timeouts when players are ready or not. They can also have single integer value, both Ready and notReady parameters are then set to single given value
×