I’ve queried this with our developers, and hope to have an update for you soon.
I’ve queried this with our developers, and hope to have an update for you soon.
This is indeed occurring due to the ‘Crosshair Remap’ mod.
Sorry to hear this Arsla. If you could upload a console log, I can share this with our Backend Engineers. Alternatively, as this issue has been impacting you for a while now, I’m happy to help with a refund should you prefer that.
If you haven’t already, please could you use the ‘Verify Integrity of Game Files’ option?:
This appears to be caused by the ‘PreviewCosmetics’ mod.
There is most certainly an issue with the Zealot Flamer. We’re working to hotfix this.
This appears to be caused by the ‘Ration Pack’ mod. Hope this helps.
This (edit: well, the crash at least!) does seem to be mod-related - I’m not sure which, I believe it’s a UI mod.
Please try disabling the Overwolf Overlay.
Regrettably we cannot due to limitations in our backend, but I’m able to move over any paid currencies if that’s of any help.
We are working to hotfix this, apologies for the inconvenience.
Certainly!
%appdata%
within the search input and select ‘OK’AppData\Roaming\Fatshark\Darktide
Hey thanks for flagging this. I have forwarded it on to the combat team who have found a bug in relation to this that will be fixed in an upcoming patch!
Hi,
We’ve had a look into this and haven’t found anything that would change this on our end!
Could you please attach some evidence so we can look into this further? Are there any particular feats/blessings you have equipped/unequipped?
Added!
On 1.1.10 the side mission pickups are locked on the same location (scriptures & grimoires have separate locations) which is changed on a weekly cadence. So this is intentional. It was however missed in the patch notes. It should be updated eventually.
Thanks for the report!
Sorry @MetalTigerlily, I appreciate you’ve been waiting a while, we are stuck on this admittedly. It’s still on our radar.
Hey, just to let you know that this is a bug which will be fixed in the next hotfix - not an intended change!