Hey Everyone,
Bioware has released the latest patch 3 for PC and Console. You can read more details in our post: Dragon Age™: The Veilguard Patch 3 (PC/Console)
Once you've had a moment to download it, can you confirm if this is still happening?
Well, turns out I also suffer from this bug.
Though I didn't realize it until now because at now point in the game were the Altars or the Chests interactable for me and I just thought that they would unlock later in the story. Thing is, I just finished gathering all Companions and with the amount of Altars and Chests I couldn't do anything with up to this point and no signs that this would change anytime soon, so I got suspicous.
And here I am, finding out about the bug that's keeping my quest rewards from me, along with quite a bit of side content.
Personally I suspect that there is a flag in the game, something like "has_lyrium_dagger" that just never got set to "true" for me and that there are a myriad of triggers later in the game that might set the flag to "false".
So far my resolution was to progress through a major world state update. Hope it is for you too since it seems like the trigger is either the final companion recruitment or a gate unlock in the crossroads. 🙋♂️
though the flag makes sense, all my lyrium dagger prompts for, say, over world skills for party members who arent there. I wonder of those are different vs the generic dagger prompts. 🤔
So I went back and checked again and it is definitely something with the Dagger, because when I went and loaded the decision save right after retrieving it and returning to the Lighthouse, where your quest is to decorate your room, I actually had the Dagger, as can be seen in the image to the right. (Img 1)
Img 2:Now the next save I have was already in the Ossuary and by that point I already lost the Dagger as can be seen here: (Img 2)
And yes the loop is supposed to be visible even in armor: (Img 3)
Img 3:Personally I suspect that the bug occured for me when I completed Solas Memory in the Converged City the first time, given that that was the only significant thing I did between the Lighthouse and encountering my first ever Fen'Harel Altar, which already stopped working.
I tried replicating the bug twice with slightly different setups, but this time around everything worked fine.
So I suspect that there is an element of randomness when it comes to this bug.
Regardless, I would assume that a fix for this on the Player side would be quite simple, if a Save Editor for DA:V was already available. Sadly it isn't, and so we have to pray that it'll get fixed with the Patch that is coming soon.
PS: Yes, I'm quite sure that the Companion Ability use of the Dagger is something very different from using it to interact with Altars and Chests. I would say that the ability use is essentially just a reskin of a companion using it, so functionally as long as you have recruited the companion whose ability you want to use, it will likely just check if the companion is with you and if yes, the companion is going to execute their animation and if no, then it's Rook's lyrium dagger animation and the game doesn't really care beyond that.
Now for the Altars and such, you could theoretically encounter them before going to the ritual site to get the dagger, so the Devs needed a way to prevent you from interacting with them while you still didn't have the dagger. And that is probably what is biting us in the **bleep** right now, as there appear to be multiple somethings that can disable whatever is supposed to be telling the game that we do in fact have the dagger and it seems like that the after retrieving the dagger, there possibly is only the switch after act 8 that has a condition to enable again.
Just to clarify, without the dagger loop is when the bug is active for you?
i usually have the loop with me playing bug free atm as expected (as far as i understand your report which is as expected?). But my entire time bugged the first time, it was also there for me. Used to wonder why it was just the loop actually. Thought it was supposed to be tucked behind based on the idle animation, so i wondered that if its just the random loop hanging on the hip it was a visual bug too. So we can add that to the odd randomness of it 🤔
my second occurrence happened during the crossroads boss behind the triple revenant gate again after the dinner table squabbling after weisshaupt. This was also the time the first one reset, moving into act 2. But since technically i hadnt progressed story and got my second occurrence of the bug I can see where some people could have the bug persist through world state updates. And like you said, randomness. Its maddening. Lol like when pawn dragon blight wasnt explained properly for dragons dogma 2 (if anyone can relate). 🤣
if i encounter it a third time (or kill the boss again to test) ill take note if the loop disappears for me. Cos that would be a better tell instead of keeping an altar accessible at all times to make sure all is well before tackling progress. 😵💫😭 thats what i do for now. Every milestone i swing by an altar im preserving to see if im bugged. 😵💫🤣 it’s inconvenient but a sure fire way to tell so far.
man. Just hope our reports can help this get fixed (not that it matters for me now that im almost through with my first playthrough as I dont usually do multiple playthroughs without ng+ etc). If not for perceptive players like us here, the rest could be oblivious to this problem like I did the (possibly) first time. I just figured when I first played that i just didnt know which altars actually had functions and rode the game through part of act 1 until i was more comfortable with the ui. And in hindsight im certain this had happened earlier too and i just didnt realize it til i was actively activating them as i went and understood the markers on the map.
interesting to note though. Ill notice the loop if it happens again. I dont think im going to attempt the boss for now since its not important until pre-ending. But ill notice it if another event triggers the bug again and report back. Thanks for noticing this detail. At least solves the other unrelated part of me wondering if the loop alone without the blade was a visual bug or not. 🙋♂️
Yes, without the loop the bug is active, with the loop present everything works as expected.
