Original Post — Direct link

I cannot complete the shifting loyalties quest (and therefore cannot receive the Freedom Fighter trophy/achievement) because there is a glitch in the system which prevents the final opponent from appearing. I have completed the quests in Kalstad and Dokkerland, as well as retrieving the Monestones in Nidheim; I can even find the dead thrall with the stones arranged, but noting else ever happens except a triggered enemy encounter that cannot be completed, even when the lone enemy that appears is defeated.

I am running version 1.6.2 on a PS5, utilizing a PS4 disc.

I have reviewed the previous thread regarding this error: https://discussions.ubisoft.com/topic/168697/tfs-unable-to-complete-shifting-loyalties/4?lang=en-US; I have attempted each of the workarounds (dying in the water after defeating the enemy, exiting/reentering the Animus, etc), but none are successful (and, in principle, I shouldn't have to use a workaround anyway; it should just work).

I have attached a video of my run (starting in Nidheim) that shows 1) that the thrall's corpse doesn't appear, but that I can interact with it as though it were there, 2) that the werewolf never spawns and that 3) that you are trapped in the area after defeating the enemy that does actually spawn. You can see my video here:

">

I would be glad for someone to fix this as I have made about a dozen runs trying to unlock this trophy, all of which end precisely the same way. I can't get the trophy until/unless this is fixed. I know this was a problem prior to version 1.6.1, so it is very frustrating that it was not fixed by now, especially if, as I anticipate, support for this game is going to end now that AC: Mirage has been announced.


over 1 year ago - Ubi-Thrupney - Direct link

Hey @jackturner3 , thanks very much for reaching out with your report of the werewolf not spawning in Shifting Loyalties. I can understand how frustrating it is to not be able to finish a trophy due to a glitch, and I'm glad you've let me know about this.

I've gone ahead and reported this to our teams, who are continuing to investigate the issue. Thanks for being so comprehensive with your reporting here, especially in regards to your game's version and what workarounds you'd tried - that really helps us out. Please let me know if you've any other thoughts or questions while we continue to look into this.