FatsharkJulia

IMPORTANT! We have released an experimental branch in Steam, which includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

...

IMPORTANT! We have released an experimental branch in Steam, which includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

...

IMPORTANT! We have released an experimental branch in Steam, which includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

...

NOTE: The experimental branch in Steam has been updated to include logging for other issues. The experimental branch now includes:

• POTENTIAL Backend Error FIX. We understand this hasn’t worked for everybody, and are continuing to investigate
• Additional logging for internal_error (Error Code: 2007)
• Additional logging for nonexisting_channel (Error Code: 2001)
• Additional logging for various GPU-related crashes, AND A POTENTIAL FIX!

Please note that the additional logging supports our investigation and will not necessarily solve the underlying issue for you at this time. We encourage anybody with these issues to use this branch, so we can continue work on addressing these issues as quickly as possible.

...

Super! Seems we’re making some progress.

Thank you for trying, and for the detailed account. I’ve let our developers know.

Is this still occurring for you?

As above, console logs, please!

I’ve been able to look up the crash with the GUID, and can confirm it’s in our database to be investigated.

We’re looking in to this. Thank you.

IMPORTANT! Our developers are asking if anybody with the Backend Error (NOTE: NOT the internal_error (Error Code: 2007) or any other error) can try the experimental branch in Steam, and see if that resolves their issue.

PLEASE READ THE INSTRUCTIONS BELOW FULLY! THANK YOU.

1. Open the Steam client
2. Right-click Darktide in your Steam library
3. Select ‘Properties’
4. Select ‘Betas’
5. Enter the password cTYPtKTsfMDsLHAV
6. Select ‘Check Code’
7. Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
8. Se...

We hear you. Closing this post as it has derailed somewhat.

I suspect this is already on our radar. But please include the crash report produced so we can double-check.

There is some confusion around players being unable to refresh their Weekly Contract Tasks.

This is because there is a cap on how many times you can refresh, which appears to be 4 times in a week.

This is not explained in the UI. At all. We’re working on that!

Please include the crash report produced. Thank you!

We’re working on it. Thank you!

This is in your console log and may point you in the right direction:

Hardware-accelerated GPU scheduling in Windows OS needs to be enabled - please see https://devblogs.microsoft.com/directx/hardware-accelerated-gpu-scheduling/

This is usually the result of an underlying driver or hardware instability. Please see: https://support.fatshark.se/hc/en-us/articles/360038965013--PC-How-to-Resolve-PC-Crashes-Loss-of-Responsiveness-or-Blue-Screens-BSOD-

The most likely culprit here is a driver or hardware instability. Please see: https://support.fatshark.se/hc/en-us/articles/360038965013--PC-How-to-Resolve-PC-Crashes-Loss-of-Responsiveness-or-Blue-Screens-BSOD-

This is a very unique issue and unfortunately it’s not likely to be something we can reproduce on our end.

Do you have another mouse you could try with?

Also, try a ‘Selective Startup’ to rule out any background applications interfering with your input:

1. Press the Windows key
2. Type ‘msconfig’ and select ‘System Configuration’
3. On the ‘General’ tab, select ‘Selective Startup’
4. Deselect ‘Load Startup Items’
5. Reboot your PC
6. Launch as normal, and see if the issue persists