FatsharkJulia

Looking in to it.

As above. Sorry!

Thank you Harridas - looking in to it.

This is due to be resolved in our upcoming patch.

To be resolved in our next patch!

Due to be solved soon.

We’re on the case!

Not at this time, unfortunately!

We are currently investigating reports of players crashing on mission start.

Existing reports may be merged here, to help us keep track of the issues being reported.

We are aware of and looking in to issues where progression for the ‘Abhor the Mutant’, Cliffhanger’ and ‘Up Close and Personal’ Penances is not counting as expected.

This is also because the descriptions are potentially misleading. Bear with me whilst I investigate!

Existing reports may be merged here, to help us keep track of the issues being reported.

We’re on it.

We are aware the descriptions for ‘Warp Battery’ and ‘Shocking Stuff’ Penances are misleading.

These Penances list Malice or above as the requirement, but progression is only counted when on Heresy or above.

Existing reports may be merged here, to help us keep track of the issues being reported.

We are aware of a number of issues where enemies - commonly the Mutant - can yeet the player outside of the map boundary or in to otherwise unreachable areas.

Existing reports may be merged here, to help us keep track of the issues being reported.

Sorry to hear that. Your crash is GPU-related but there was likely some underlying vulnerability to start with, we operate in protected memory so it should never be possible to cause physical harm to your components.

Let us know if you’ve had any luck with the above. We’re also looking in to similar issues so I’ll add this to our internal report.

Thank you for the update. We’re looking in to it.

I believe this is related to something we’re currently looking in to, so I’ve raised this to our database.

This is mentioned in your logs, and may be of help:

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

They are moved to the GPU-related crashes post because they are GPU-related, and we need to at least attempt to keep it organised. We are running on empty working loooong hours days every day, so we don’t have the time to respond to each and every person experiencing the same GPU-related error.

I can also see this error in your logs, which may help you:

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

We’re looking in to it. Thank you!