Original Post — Direct link

I have been stuck on "Into the Fog" for awhile. All I need is the key, but no matter what trick I use it will not spawn. I have tried sitting over a thousand meters away for a hour, and always the same 3 npcs respawn. I feel like I remember there was 4 initially, but the fourth never seems to respawn. I have gone back to England and waited there a hour before coming back. I have checked my file integrity over, and over again to no avail. I would love to finish this DLC, and move onto the next, but it appears to be rather broken. I have seen many other people with similar issues complaining, but I figured one more post showing it was indeed still out there, and still broken would get this closer to being fixed.

Any help is appreciated! Thank you!

about 3 years ago - Ubi-Oxavo - Direct link

Hello @heretic721 and thanks for reaching out to us!

I understand from your post that you are unable to collect the cavern key in the quest "Into the Fog" as the enemy doesn't spawn.

The development team are aware of this issue and they are investigating further. Once we have any updates to share from this investigation, we will let you know within within the News & Announcements forum.

In the meantime, our teams would like to use details from your progress on Assassin's Creed: Valhalla to make further research. Please make sure that your latest save has been added to the Cloud (it will have a cloud icon next to it). This step will allow us to use your save files for investigations.

We would also need a video of the issue.

We apologize for any inconvenience and thank you for your patience and understanding while we work to resolve this issue.

about 3 years ago - Ubi-Keo - Direct link

Hi @heretic721 apologies for the late response.

I have forwarded your video and save file on to the development team.

As Ubi-Oxavo mentioned above, please keep checking the news and announcements for updates.

about 3 years ago - Ubi-Keo - Direct link

@heretic721 Thanks for the update, I'm sorry to hear that the issue persists after the latest update.

I have informed the development team.