[BUG] Watch UI Broken

[RootbeerGuy99]

Platform: Xbox Series X

Upon loading up the game, the Watch UI changes/updates its hud correctly whenever the player opens their scanner, however, when the player chooses to fast travel to a new location, the Watch UI no longer correctly changes/updates when opening up the scanner.

The only mod I have installed is Watchtower, which is fully updated.

 

[RootbeerGuy99]

I'd also like to add that I tested this by loading a character that was already standing in the Starborn Ship. Pulling up the scanner correctly updates the HUD, but then if I fast travelled to a new location (such as Akila City), pulling up the scanner no longer updates the HUD.

 

[kinggath]

Thank you for this report! I had it happen once myself on this patch (which we thought fixed it) and I couldn't figure out why it only happened one session. Fast travel seems to be the answer - though only certain fast travel seems to trigger it for me.

Either way, that should be the intel we need to fix this.

 

[Ragnos21]

Hello. I have the same problem. But I don't use fast travel. When loading the game, the compass works as it should, but as soon as I go to any other location, the compass stops switching.

 

[Zabraxa]

Thought I'll add a point. Happens to me as well. No fast travel, just when I open the Starmap.

Example:

1. Load Save - Watch works
2. Press M - Watch stops working
3. Load Save again - Watch works again
4. Press M - Watch stops working

 

[UrzaPlaneswalker]

I only found one location where the watch worked: the Stroud-Ecklund asteroid where you hunt down Maya Cruz. It hasn’t worked anywhere else for me

 

[deathraptorF22]

It looks like the watch UI is still buggered. Although I'm fairly sure at this point it's a Bethesda issue, and we all know they're too lazy to do anything about it. To clarify the watch works fine until you open up your map then it stops functioning. And yes I am on version 1.0.2 of the Watchtower mod, it is up to date.

 

[twolargepepperoni]

We didn't include a fix for this in patch two as we are still working on one with our UI developer. We hope to see this resolved once and for all in a future patch.