FatsharkLev

FatsharkLev



03 Jan

Comment

I’ve responded to your Support Ticket :slight_smile:

Comment

I’ve responded to your Support Ticket :slight_smile:

Comment

I’ve added this crash to our database for investigation - we’re on it!

Apologies for the inconvenience.

Comment

I’ve added this crash to our database for investigation - we’re on it!

Apologies for the inconvenience.

Comment

There is a known issue with cosmetics randomly disappearing, and subsequently re-appearing for some players. We implemented a fix but it wasn’t robust enough - so we’re looking into it again.

Please be assured that your cosmetics haven’t been deleted. We’re working on it, and this will hopefully be resolved in one of our upcoming patches soon.

Apologies for the inconvenience in the mean time.


23 Dec

Comment

@hawkoflight_g

Thank you, I’ve passed this on to the team and we’ll investigate.

Due to the time of year, many sharks are now out of office, and this may not get looked at immediately.

I’ll update you when I hear anything :slight_smile:

Apologies for the inconvenience in the mean time.

Comment

Hi @hawkoflight_g,

Sorry to hear that. Usually enabling the Steam Overlay should resolve this. :thinking:
I’ve let our team know, and we’ll have to look into it.

Could you please provide me with your Steam profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/), a...

Read more
Comment

This crash is on our radar - thank you for the report, and apologies for the inconvenience.


22 Dec

Comment

Glad to hear that!

I’d be keen to hear if the new workaround setting ‘Reset Key Bindings on Start’ resolves the issue for others here too? Please let me know :slight_smile:

Comment

Yep, thank you!

All of these crash reports show GPU hang crashes. I’ll merge this with the Known Issue topic.


21 Dec

Comment

@duppskoen @acfan4ever and for anyone else reading this.

Just to keep things more manageable, please can you submit a support ticket to us, here:
https://support.fatshark.se/hc/en-us

Thank you!

Comment

Hi @Exmatrix,

This is pretty strange. Can you double-check and ensure that you have the Steam Overlay enabled? As this is required for in-game purchases.

  1. Open the Steam client
  2. Click ‘Steam’ in the upper left-hand corner
  3. Select ‘Settings’
  4. Select ‘In-Game’ in the sidebar
  5. Ensure the ‘Enable the Steam Overlay While In-Game’ option is enabled
  6. Click ‘OK’
  7. Re-launch Darktide
Comment

Hi @ConorOepkes,

This error indicates a GPU related crash. It’s possible it could be a local issue and we do have some suggestions, here:

Read more
Comment

Thanks both! I’ve added this to our database and we’ll look into it.

Comment

This one is on us - I’ve added it to our database for investigation. Apologies for the inconvenience!

Comment

Hi @ToxSynTV,

Sorry about that - the account reset service is now back up! :slight_smile:

Comment

Hm okay. I use UserBenchmark for system spec comparisons.

Read more
Comment

@Berossus,
A developer was able to take a deeper look at this, and has suggested if you can try installing Darktide on another disk? as this may be due to faulty sectors. It’s an odd crash, and something that appears to have no reason that it should reoccur after reinstalling.


20 Dec

Comment

Thanks for sharing your findings - I’ve let the team know.

The 10 minute load definitely seems like a bug - and we’ll look into it.

You’re correct, that loading into Missions you are subject to the slowest players loading time. We are exploring options here, like potentially adding a “Waiting for other players” message.

For the Mourningstar hub, we have ‘loading groups’ - you should mostly not end up in a group with other players, but if you do, you can still be subject to having to wait for others in your loading group to join. Also, when loading into the hub the hub matchmaking is included, so some additional time can be taken to find an appropriate hub to join.

Though, 40+ seconds on an NvMe does sound excessive :thinking:

The developer I’m discussing this with also shared this information:

...
Read more
Comment

I actually haven’t received a 100% definite confirmation about this. All I’ve been told is that it should have been included.

What I’ve done is reopen the issue in our database and make some noise regardless, as either it needs to be revisited for a new fix, or the fix needs to be included for our next update.

I’ll keep on it!