FatsharkLev

Hi @PathofChaos,

I’m sorry to hear that.

We’re actively investigating and working to resolve connectivity issues resulting in the error codes mentioned. Apologies for the inconvenience in the mean time whilst we tackle these!

As for crashes, can you please provide additional crash reports or console logs so we can take a look?

Hi @paulwoods,

Regrettably, we are unable to move progress from one account to another due to limitations in our backend.

Please accept our apologies for any disappointment.

Hi @jeandeaux,

I’ve passed this issue on to our development team.

I’ll update you when I have any response.

Sorry to hear this. Can you please provide your console log from the session this happened?

We’re looking into this. Apologies for the inconvenience!

I’ve passed this information on to the development team. Thank you for the report!

Hi @TheSovietChef,

I’m wondering if this was a temporary connectivity issue. Can you sign in now or are you still experiencing this issue?

Hi @MonsieurGrumme,

This issue is on our radar and under investigation.

Hi @wesleyshaver,

Well that’s odd! Can you please provide me with your console log from the session this happened?

Thank you in advance!

Hi @BoBo,

Please try verifying your game files to see if the culprit file can be reacquired.

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

If this does not work in fixing the file, I’d then recommend to try reinstalling Darktide.

Let me know how you get on!

Queue is clear again

Queue is clear again

@orvis25
Thank you for detailing your findings with FSR. I’ve passed this on to the development team, and we’ll be investigating as it definitely sounds off that we see higher memory usage with FSR 2 on than off.

Regarding 2.2, at this time I can’t speak to any future plans. I’ve mentioned this internally though, and it’s a discussion point for sure.

After the new patch, the Texture Resolution setting may allow you to run the game better. Though, you are still treading a very thin line memory-wise. Unfortunately, as we are not actively supporting your setup with an integrated GPU and 8GB RAM you will likely continue to experience issues with running out of memory every now and then, for example during some levels that might be more memory heavy.

Glad to hear the performance has improved!

Hmm, really the only thing to set for Steam is the Download Region, which is one of solutions in the article - which you may have already done.

@Angelos001

All sorted When you next sign in you’ll find a level 30 Pysker, and some credits to spend along with some crafting resources to help get you equipped suitably again.

@Angelos001

No problem - our humblest apologies again that we can’t restore your old character as it was, but we’ll ensure another Psyker is levelled up to 30 again for you so you can jump back in!

If you can please create a new Psyker, choose your backstory, appearance etc. and reach the hub. After that, please give me a shout and we’ll sort the rest from there for you.

Hi @Angelos001,

Apologies for the delayed reply!

We’ve taken a look at your account in the backend and can see that several characters were deleted in a very short period of time. The level 30 Psyker character was deleted inbetween deletion of two level 1 characters. Could this have happened by accident when deleting the lower levels?

I am very sorry to say that due to limitations in our backend we aren’t able to restore a deleted character at this time. I can understand that this is very disappointing, however, I can boost a newly created character to level 30 for you. The character will be without the equipment and currency you previously had, but some currency can be added to the character to get you equipped and started off again.

Is this something you’d...

@BoBo, sorry for the delayed response!

Two of the crashes posted above are Deadlock type crashes. Which unfortunately we’re unable to determine the cause from the crash data alone. For these, we recommend running through our general crash solutions to see if there’s any improvement:

Have you tried the potential solutions in the article linked above?

Queue fixed once again