FatsharkJulia

FatsharkJulia



28 Jun

Comment

Hello! I’ve moved your post to Technical Support and we’re looking in to this. Sorry for the inconvenience.

Comment

Could you try now our latest patch is live, and let me know if the issue persists please?


27 Jun

Comment

We’re looking in to this now. Thank you for letting us know!


26 Jun

Comment

This should be addressed with our next patch. If problems persist, please let us know.

Comment

This is a backend-related issue and should be resolved with our next patch. If problems persist after the update, please let us know!

Comment

Thank you for keeping us updated. I believe the underlying issue on Steam’s end is now resolved, and you should be able to reenable Steam Cloud should you so wish to.

Comment

Hello Archaon, is this now resolved for you?

Comment

This is an unfortunate side effect of anything that hooks in to the Darktide client, and not something we can resolve. I don’t have any experience with Bandicam, so perhaps somebody else can chime in, but is there a way to disable hooking whilst still being able to record?

Comment

Thank you for the console log, it would be really helpful to have a darktide_launcher.log though, which is accessible by:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide
  4. Locate the darktide_launcher.log in this directory
Comment

That would be a console log but I’ve been able to pull the darktide_launcher.log from the GUID you provided, so no worries! :slight_smile:

I’ve been able to locate and raise your crash to our database for our developers to look in to. In the mean time I recommend using the ‘Verify Integrity of Game Files’ option, which is accessible via the Steam client using the instructions below:

  1. Right-click Darktide in your Steam library sidebar
  2. Select ‘Properties’
  3. Select the ‘Local Files’ tab
  4. Select the ‘Verify Integrity of Game Files’ button
  5. When complete, close and reopen Steam

22 Jun

Comment

I apologise, I’m still waiting on a response. With tomorrow being a public holiday in Sweden, I’m unlikely to hear anything until Monday.

If you would prefer, I can help with processing a refund for you.


21 Jun

Comment

One of our developers say you may need to experiment with window modes.

You may also wish to try disabling your mods, to see if that could be related.

Comment

Sorry for the delay here - I’ve asked our developers for their opinion on this.

Comment

My apologies for the delay, could you include your darktide_launcher.log here please?:

Read more

20 Jun

Comment

Whilst it is possible to disable the sending of crash reports by changing SendCrashReports to false in your launcher.config, it won’t completely disable the sharing of hardware information that is used to support performance optimisation.

Comment

It depends on your screen set-up what the correct value will be, but to start with you could try changing fullscreen_output in your user_settings.config to 0.


19 Jun

Comment

This is a backend-related issue, and should be resolved with our upcoming patch. :slight_smile:

Comment

Could you also include your darktide_launcher.log, please? :slight_smile:

Comment

This was, unfortunately, not intended and has since been patched up.

Comment

There is always an underlying driver or hardware-related explanation for cases where the PC loses responsiveness or BSODs. Please see:

Read more