New ga setting at times feels like it does not register a new target despite the available ga target and will instead default to the beam target, probably because it’s tied to the reticle appearing on the target and not having los for frame perfect ga’s. This causes awkward positioning mistakes when old ga would have properly flied to the target.
Edit: New bugged interactions since ress/lunar year patch.
Video clip example how guardian angel bugs out and does not GA to valid new target, yet consumes guardian angel cd:
And at times, if you don’t have the reticle appear on the target, even if it’s a valid target, it will not consider that new target a valid guardian angel target with the new setting.
Here reticle appears on the player when GA is being held down, but as soon as the reticle disappears for a split second despite player holding down GA button on that target beforehand, it’s no longer considered as valid new GA target.
Here is an example of normal GA where player can perform frame perfect GA despite never seeing the visual reticle cue appear. (clip stopped working for some reason, I need to redo it)
Lifting this back up because setting is bugging worse now.
It seems to not be registering new targets anymore fast despite facing towards the direction of the ga and this seems to have happened either during the mercy ress patch or the lunar new year patch.