Jump to content

Demetrios-fbcafa4682d1462f

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Demetrios-fbcafa4682d1462f

  • Rank
    On the Coast

Recent Profile Visitors

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

  1. Demetrios-fbcafa4682d1462f

    Server Not Advertising - No not for the typical reasons

    We figured it out, but we don't know how to fix it. When we remove the mods in the net logs we get [2024-08-25 10:14:28] [Connecting, 4, 0] [A:1:0:0] CM Directory list says 97% of connections should be websockets, we rolled 5 - using WebSockets as default. But when we add them we get [2024-08-24 21:10:31] [Connecting, 4, 0] [A:1:0:0] CM Directory list says 97% of connections should be websockets, we rolled 99 - using UDP as default. So basically its the game decided whether to use TCP or UDP as the default protocol. When it uses UDP it won't advertise out, but when it uses TCP, it works fine. We also verified this with other servers being used, they are only connecting via Websocket/TCP and not UDP. I submitted a ticket with Bohemia, hoping they respond.
  2. Demetrios-fbcafa4682d1462f

    Server Not Advertising - No not for the typical reasons

    Gents, this isn't a simple config or mod issue. I'm at a loss for what the issue might be. Currently hosting a few DayZ servers dedicated here on my local network. For the purposes of describing well just say Server1 and Server2. Server1 is setup dedicated locally (currently has 48 mods at ~25GB) and we've setup the exact same server, mods, configs, etc. on another network/machine we've been testing with. With server1 setup here it will show in steam game servers but will not advertise to either the vanilla or dzsa launcher. With server1 at the other location, it advertises out no issues. Here's where it gets weird, server1 at the first location locally that won't advertise, if I remove 6 or so mods, it advertises on both launchers. I've tried including steamProtocolMaxDataSize = 8196; in the server config and no change. but this doesn't change anything. It seems to be a mod limit, but it clearly works on another network just fine. I've scanned the UDP packets and it isn't a packet size limit (they're right around 1400 bytes, so no cap there.) My MTU settings on the network are fine and set to 1500. I'm also running another server (Server2) that has 78 total mods, totaling 75 GB with no issues on the same network. Anyone have any ideas?
×