Backend Error - Error signing in, during ++Processing Inquisitorial Clearance++

Issue Type (Required):

Error - Backend Error

Issue Description (Required):

Hello,

As the tittle says I’m having issues with Backend Error - Error signing in, during the ++Processing Inquisitorial Clearance++ screen.
I’ve had the game for a few weeks and were able to play just fine. Added a couple mods sometime later. The error occurred some days later.
After trying various “fixes” i found online, finally re-installing the game seemed to do it, only for it to happen a few days later again. This time not even a fresh install helped.

Things I’ve tried so far:
-Purging mods
-Verifying files via steam
-Verifying files via launcher
-Restarting steam
-Clearing steam download cache
-Changing DNS
-Adding firewall exceptions
-Removing the game and Fatshark folder located at %appdata% then doing a clean install
-Connecting to a mobile hotspot network
-Added the entire steam directory to Windows virus protection exclusions

Please note that I am not using a VPN so nothing to do/try there.

Hopefully I’ve provided everything needed. Let me know if otherwise.
Any help would be appreciated!

UPDATE 1: tried different steam account using family share. Issue seems to persist!

UPDATE 2: after leaving home for a few hours and coming back it seems to have fixed itself which is very weird because nothing changed and I didn’t mess with it any further. It would be nice to know what is causing it to prevent it from happening again.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

Player ID (Optional):

[PC] Upload Console Log & darktide_launcher.log (Optional):

darktide_launcher.log (142 KB)
console-2024-10-15-13.20.48-5bb3a044-4b2a-4ddc-b2ee-1c14fe88e18d.log (198.6 KB)
console-2024-10-15-13.53.13-39d5579a-2b00-4bff-8c3d-d7d7ca4547bd.log (107.6 KB)
console-2024-10-15-13.56.22-b9c465db-d699-4155-be2d-5885e05e4d23.log (109.0 KB)

Thanks for the update! I did share your console logs with our developers, but we’re not entirely sure what the culprit is.