Wrong geographic server region auto-selected for the Mourningstar instance after logging in
Issue Description:
After selecting my character and entering the Mourningstar, the game sometimes places me into a Mourningstar instance in the wrong region.
When playing a mission, I can get much better latency (sub 100 ms) by selecting the correct region that is closer to me instead of the one that was auto-selected during login. Matchmaking using the auto-selected region will often have 300 to 400 ms of latency instead.
However, when I return to the Mourningstar after the mission, the loading time is long (and is sometimes stuck forever), possibly because of the higher latency of the Mourningstar instance’s region.
I understand that there may be no way for Darktide to automatically detect when my ISP or VPN is reporting unreliable ping latencies, so being able to manually select the region during character selection would be enough to resolve this problem for those who have it.
Steps to Reproduce:
Start the game and select a character.
This occasionally happens to me on my regular internet connection, located in the Philippines. It happens more often when I use a VPN and select an Singaporean exit node (which is sometimes necessary when my ISP has bad peering).
Mission Name (If Applicable):
Mourningstar.
Platform:
Steam
Player ID:
ORYLY
Approx. Time of Issue & Timezone:
N/A
Reproduction Rate:
Common (50%)
Upload Supporting Evidence:
I took this network traffic scan while in the Mourningstar, right after selecting my character. It says I’m connected to 18.133.240.143, which is in London. The closest server for me geographically is in Singapore (“Asia & Pacific Central”, in game). There have also been times when I’ve been placed in Oregon or Frankfurt instances, which are nowhere near Asia!
[PC] Upload Console Log & darktide_launcher.log:
console-2023-11-03-07.54.50-37087c97-0ba1-49a8-aff9-6a3903b1d98c.log (129.6 KB)
darktide_launcher.log (600.1 KB)