Jump to content

Dwarden

BI Developer
  • Content Count

    10617
  • Joined

  • Last visited

  • Medals

  • Medals

Everything posted by Dwarden

  1. 1.94.145986 new PROFILING branch with PERFORMANCE binaries, v02, server and client, windows 32/64-bit, included linux 32-bit server + sync with 1.94.main + merge of all 1.92.profiling fixes which aren't in 1.94.main (dozens) + waitUntil undef expression handling is now error only (instead of break on error) (beware that if you get the error, then your script code most likely ends in infinite loop) + getResolution extended with topFOV, leftFOV, tripleHead, added forgotten array resizes + getFuelCargo, getRepairCargo, getAmmoCargo will return -1 when the vehicle is not capable of using cargo/repair/ammo + fix for #monitor / #monitords to work correctly with missionsToServerRestart + improved work with command-line arguments (including for linux) manual downloads: 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
  2. just remember you can manually disable the automatic 1:2 (the threshold in new UEFI bios is 1833) so if you lucky you can run uCLK/fCLK at 1833 or 1866 or 1900 in sync also i recommend Ryzen DRAM calculator 1.6 (or newer) for tweaking memory timings https://www.overclock.net/forum/28064156-post4887.html
  3. not bad at all i must say , even with that latency
  4. @oldbearwhat are the timings on that memory ?
  5. These are atm. active official ZEUS servers 109.236.82.30:2302 109.236.82.30:2402 217.23.2.20:2302 217.23.2.20:2402 217.23.14.20:2302 217.23.14.20:2402 23.229.5.146:2302 23.229.5.146:2402 172.245.1.58:2302 172.245.1.58:2402 23.229.5.154:2302 23.229.5.154:2402
  6. 1.92.145918 new PROFILING branch with PERFORMANCE binaries, v18, server and client, windows 32/64-bit, included linux 32-bit server - reverted fixes back to ~145886 (script caching, object stutter, known issue of failure to auto-restart instance, linux commandline vs mods) note: no eta on when script caching , stuter fixes gunna be resolved those known issues remain to be solved (some resolved internally already): - bug with the #monitords retaining the value after instance autorestart (fails to restart) - issue with the commandline parsing (side-ffect vs linux ) - the #monitords reporting negative memory values manual downloads: 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
  7. 1.92.145899 new PROFILING branch with PERFORMANCE binaries, v15, server and client, windows 32/64-bit, included linux 32-bit server + fixed issues with attachTo objects and simpleObjects causing stutter + possible performance / smoothness improvement related to moving objects (due to fixes from previous line) known issues (wip to resolve): - the memory leak in caching as edge case - bug with the #monitords retaining the value after instance autorestart (fails to restart) - issue with the commandline parsing (side-ffect vs linux ) - the #monitords reporting negative memory values manual downloads: 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
  8. skipping v11 to v13 (due to various issues) 1.92.145888 new PROFILING branch with PERFORMANCE binaries, v14, server and client, windows 32/64-bit, included linux 32-bit server + resolved a lot of crashes (e.g. audio, AI related etc.) + improved command-line arguments handling (e.g. for linux dedicated server) + extended #monitor , #monitords commands with more details (networking, players) - for players info L = lobby , R = role selection , B = briefing , G = in-game , D = debriefing - for new traffic info NG = non guaranteed , G = guaranteed (?-BE means BattlEye traffic) + fixed debriefing after missionEnd - when using server.cfg settings (missionsToServerRestart,missionsToServerShutdown) - when using admin command #shutdownaftermission , #restartserveraftermission + fix for freeze related to SAM/LOAL missiles + script caching is back with more performance and no memory leaks manual downloads: 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
  9. Dwarden

    Warlords

    it's unfortunate, yet known bug which went unnoticed for long time as server used higher values than 1,2 cycles when the server uses missionsToServerShutdown / missionsToServerRestart feature (automatic process end) instead of triggering this after DebriefingTimeout it proceed with the operation instantly at missionEnd will try get this fixed as soon as possible
  10. Dwarden

    Warlords

    note: large official Warlords servers (44 and 52 players atm.) may run slightly modded/improved variant of above to provide more enjoyable experience
  11. 1.92.145773 new PROFILING branch with PERFORMANCE binaries, v10, server and client, windows 32/64-bit, included linux 32-bit server + fixed crash in dynamic simulation 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
  12. 1.92.145767 new PROFILING branch with PERFORMANCE binaries, v09, server and client, windows 32/64-bit, included linux 32-bit server - reverted changes from builds 145755 / 14542 which added attempt for 'safe' CreateVehicleLocal different approach needs to be made, to cause less headache, such revision will take time (so not sooner than for 1.96) 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
  13. samatra already told me, if you run the unsafeCVL=0; (aka safeCVL enabled) then there is issue which needs to be addressed in the normal (legacy) unsafeCVL it all shall work fine
  14. Dwarden

    Warlords

    that's fixed already and btw. endless teamkilling is history (after finishing update cycle of all servers)
  15. 1.92.145755 new PROFILING branch with PERFORMANCE binaries, v08, server and client, windows 32/64-bit, included linux 32-bit server + more crash fixes (not included in 1.92.main yet) + Fixed: Headless clients are no longer taken into account when voting nor when switching server states + Default values for timeout changed back to original values before lobbyIdleTimeout introduced: votingTimeOut=60; roleTimeOut=90; briefingTimeOut=60; debriefingTimeOut=45; lobbyIdleTimeout=0; //turned off by default note: all the fixes are still in place and server.cfg settings are still available + unsafeCVL turned ON by default e.g. unsafeCVL=1; //legacy mode active (this is in reverse compared to 1.92.145742) note: no linux server yet (next week) 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
  16. WARNING: this is HIGHLY experimental build may break scripting which depends on createVehicleLocal (which could be insafe for multiplayer) please update your scripting accordingly (either to use createSimpleObject or CreateVehicle for correct multiplayer global sync) 1.92.145742 new PROFILING branch with PERFORMANCE binaries, v07, server and client, windows 32/64-bit, included linux 32-bit server + more crash fixes (not included in 1.92.main yet) + scripting command createVehicleLocal was restricted in multiplayer enter-able vehicles, shots, explosions and similar are no longer possible to spawn (the legacy behavior can be turned on via "unsafeCVL=1;" in the description.ext or server's config) + new optional parameter added to scripting command createSimpleObject createSimpleObject [par1, par2. local]; // as bool, to enable local only effect 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
  17. Dwarden

    Warlords

    my reaction was to the comments which were leaning toward feel that the issue being the server performance or client-server sync (FPS tie was decoupled ayears ago) also i was trying to point out the server FPS wasn't below 20 which is the critical threshold too server performance for majority of tests even with 80+ players was just fine btw. if you not noticed the corpses and vehicles and wrecks (those to degree) are cleaned up ... but i discussed with @Jezuro some optimizing and will look into that in future ...
  18. Dwarden

    Warlords

    for now i made drastic step of anyone trying to deploy SAM gets battleye kicked ... that's only until it gets fixed or @Jezuro comes with workaround
  19. Dwarden

    Warlords

    done plus all Warlord servers now run 1.92.145735 profiling branch build https://forums.bohemia.net/forums/topic/160288-arma-3-stable-server-192-performance-binary-feedback/?do=findComment&comment=3360678 note: the freeze @CaptainDawson is for sure related to some issue with SAM , someone managed to get exactly the same effect with Zeus scenario
  20. 1.92.145735 new PROFILING branch with PERFORMANCE binaries, v06, server and client, windows 32/64-bit, included linux 32-bit server + more crash fixes (not included in 1.92.main yet) + lobbyIdleTimeout kicks now registered as kickTimeout's type 1 issue, rather than type 0 + Added "#exec clearkicks" and "#exec unkick" commands for server admins 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
  21. Dwarden

    Warlords

    the stall freeze is investigated well the 'lag' is definitely not the server itself the server fps stayed above 30 fps and memory usage is still small but i agree that 96 is too much, i will drop it to 80 and move the 64 player servers to 48 also will be deploying new profiling branch build sometime soon today
  22. Dwarden

    Warlords

    that's why you need to give constructive feedback to @Jezuro so he can attempt to insert order into the chaos :)
  23. Dwarden

    Warlords

    that CPU is even faster than the fast CPUs used for the 64 player ones not many server CPUs faster than this one ...
  24. so it came to my attention that there is still bug in `kickTimeout` vs `lobbyIdleTimeout` and it keeps using the typeID 0 for the timer after kicked for idling :frowning:
×