Issue Description:
Keep getting warnings abaout the response from fatshark servers being slow.
I have no problems with my network. All games run fine, darktide included, with ping ingame <70ms.
This has been going on for a week or so.
Steps to Reproduce:
N/A
Mission Name (If Applicable):
Login and morningstar
Platform:
[Steam]
Player ID:
Approx. Time of Issue & Timezone:
Reproduction Rate:
Unusual (<25%) - Common (<50%)
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
I sometimes get that mid game randomly and nothing is really affected. Hopefully it’s just the off chance that the servers are taking a dump at that moment.
Unfortunately I don’t know the specificities of the issue.
Unless you havent changed a thing in settings for the past 2 weeks, then last thing to chalk is up to is a faulty 1.11-12 patch and youre just unluckily it doesnt mesh well with your system.
Issues caused by DT updates are kind of normal seeing as they test their systems just enough to be passable, then repatch it later down the road. So your issue could only be helped with either changing Full to borderless window/resolution changes, or plug a completely separate monitor to see if the pc transmits the data in a different way.
If for some reason the image comes out normally in the regular additional monitor and not the original, then somethings wrong with the original monitor where its communicating with the pc in a weird way.
Its rly jus trial and error. Change little things about the PC and hope for a difference or an answer.
You could also use Geforce Experience with NVIDIA cards so that the application can set the game’s system preferences the best way it sees fit for your PC, maybe it might change something.
edit:tldr:all my visual problems with games are usually fixed with changing the fullscreen/windowed/borderless so if it doesnt change or help with that then might rly mean your pc has an issue with translating Fatshark data seeing as you just recently uninstalled and reinstalled.
might not be local file
also check logs on the time of the occurrence, compare to previous “normal” logs, what changed.
Check when it changed, might be just before update, maybe internal error caused it right at the moment