Jump to content

Yaga

Members
  • Posts

    111
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

3048 profile views
  1. From what I've been able to reproduce, this is the issue exactly. If anyone on the server uses the unavailable range, it interferes with Link 16. Interestingly, it also appears that it effects both teams. If anyone, on either team is using the unavailable range, everyone within line of sight to that player experiences Link 16 interference, even if they are on the other team. This is likely why the original poster reported that during a match, everyone on the server reported the problem after takeoff. We experienced an identical situation during a match recently, and while nobody on our team had set an a2a tacan, the opposing team did have an A2A tacan set in the unavailable range. Edit: to clarify, A/A channels (1-36, 64-99) cause Link 16 and PPLI interference. T/R channels seem to have no effect.
  2. You might be pleased to know that this completely solved my disconnect issue. It even seems like the game runs more smoothly in MP now. :thumbup: Thank you!!!!!!!!!
  3. I own the very same nefarious router! I will set QoS on and give it another run.
  4. As far as I can tell, it's all servers for me. And as stated, like clockwork after a 125 minute connection. I just can't find any evidence to suggest what's happening.
  5. I just disconnected again after ~125 minutes. Both my local and public IP addresses have remained the same before/after the disconnect. No errors in the DHCP events that would correspond to the disconnect time either.
  6. Interesting, I'll call up my ISP. Thanks again for helping me diagnose this issue. Edit: I've also enabled the DHCP logging, and have noted my current public IP. I'll check to see if it changed after my next disconnect.
  7. No luck. Full log attached from 2 hour server disconnect. dcs.log
  8. Power management has already been disabled. I just went ahead and disabled IPv6 and set the autoexec to have DCS create full logs. Testing now.
  9. Most of the servers I fly on don't use these units. There doesn't seem to be any effect not having them. Also, page file increase had no effect. Most recent log attached. First disconnect the timeout issue, second disconnect intentional. Again, right at the 2 hour mark. I recall a autoexec.cfg line that someone said would enable "full logs". Can't find the post now though. Do you know anything about this command? Seems useful to get whatever additional data it might provide. dcs.log
  10. I tried this, and it doesn't seem to have any effect. Good find, though, it sounded promising. I still reliably lose connection after 2 hours, every time, on any server. Recent log attached. First disconnect is connection time out, second disconnect is intentional. I've increased my pagefile size, we'll see if that has any effect. 20201112.log
  11. I don't see anything obvious. The only error that gets thrown is when my jetseat shuts itself down (happens after DCS.exe terminates, so this isn't the disconnect issue). Is there something specific I should be looking for? Seems like in the DCS log, the disconnect from net event always occurs shortly after a "DCS World simulation is taking 100.0% of CPU" event.
  12. Issue seems to have returned, not sure if related to most recent OB patch. After about 2 hours server connection times out reliably. Log attached. dcs.log
×
×
  • Create New...