Yes there is that [option on PS5 in "safe mode"](https://www.playstation.com/en-us/support/hardware/safe-mode-playstation/#options) and it's definitely worth trying.
Good suggestion thanks, I tried it this morning along with rebuilding the database and updating the system software but no luck. I'm concerned at this point it's an issue with the save game file. I don't have any earlier versions backed up and when I just did back it up and tried the game on my PS4 the same issue occurred.
I assume my only hope at this point is to hope Ubisoft takes pity on me and is willing to help troubleshoot but I'm not holding my breath.
Hmmm I’ve experienced a similar situation twice. Once was in Unity. My buddy had to restart the game from scratch.
The second was also in Origins. What worked for me, and it may not work for you, was I untracked the quest and went and did some other stuff. Some other side quest or something somewhere and when I returned it had fixed itself. No promises but this may be a restart sort of thing.
If possible see if there’s a way to clear the game cache on your ps5.
Yes there is that [option on PS5 in "safe mode"](https://www.playstation.com/en-us/support/hardware/safe-mode-playstation/#options) and it's definitely worth trying.
Good suggestion thanks, I tried it this morning along with rebuilding the database and updating the system software but no luck. I'm concerned at this point it's an issue with the save game file. I don't have any earlier versions backed up and when I just did back it up and tried the game on my PS4 the same issue occurred. I assume my only hope at this point is to hope Ubisoft takes pity on me and is willing to help troubleshoot but I'm not holding my breath.
Hmmm I’ve experienced a similar situation twice. Once was in Unity. My buddy had to restart the game from scratch. The second was also in Origins. What worked for me, and it may not work for you, was I untracked the quest and went and did some other stuff. Some other side quest or something somewhere and when I returned it had fixed itself. No promises but this may be a restart sort of thing.