Jump to content

Dwarden

BI Developer
  • Content Count

    10577
  • Joined

  • Last visited

  • Medals

  • Medals

Community Reputation

1063 Excellent

About Dwarden

  • Rank
    BI Developer

core_pfieldgroups_3

  • Occupation
    Major minion in empire of Bohemia Interactive

Contact Methods

  • Yahoo
    testhandle
  • Skype
    david_foltyn-dwarden
  • Biography
    Motto: Ideas are like ocean without borders!
  • Twitter
    FoltynD
  • Google+
    110932288521681156421
  • Youtube
    FoltynD
  • Vimeo
    foltynd
  • Xfire
    Dwarden
  • Steam url id
    Dwarden
  • Raptr
    Dwarden
  • MySpace
    TestName
  • Linkedin
    TestName
  • Tumblr
    dwarden
  • Flickr
    TestName
  • XBOX Live
    Dwarden0
  • PlayStation PSN
    Testname
  • Origin
    Dwarden
  • PlayFire
    Dwarden
  • SoundCloud
    Dwarden
  • Pinterest
    FoltynD
  • Reddit
    Dwarden
  • Twitch.Tv
    Dwarden
  • Ustream.Tv
    Dwarden

Profile Information

  • Gender
    Male
  • Location
    Brno, Czech Republic

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dwarden

    Warlords

    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
  2. 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 note: no dedicated linux server binary atm. (logistical issues) 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. as i explained that -1 was wrong and bugged ...
  4. Dwarden

    Warlords

    this took longer explain https://forums.bohemia.net/forums/topic/160288-arma-3-stable-server-192-performance-binary-feedback/?do=findComment&comment=3355535
  5. 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
  6. Dwarden

    Warlords

    @Anthony Mackiw cheaters report to me
  7. Dwarden

    Warlords

    official Warlords servers were updated with server-side patch to solve some function scripting issues
  8. @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)
  9. @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
  10. Dwarden

    1.90 update - Troubleshooting

    fix what, creating any global objects in such excessive amount at same moment will cause similar problems
  11. 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)
  12. 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
  13. Dwarden

    1.90 update - 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
  14. Dwarden

    Warlords

    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
  15. 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
×