Up until today, I have been able to see the following commendations;
1. Tidal Basin Combat Merit
2. Tidal Basin Discovery Merit
These were the last 2 I needed, in their respective categories.
I was waiting until I completed this week's Invasion event with a friend of mine.
Well, upon completing this week's invasion (heroic), those 2 commendations have become locked with the message "Continue to explore Washington DC to unlock this commendation".
Is this a known issue? I have never experienced this myself until 45mins ago.
I have restarted the game. I have restarted my system. Both to no avail.
My commendation score is 3745, in case anyone might be thinking I don't know what I'm doing.
Just super frustrated. I started working on commendations this week and have been knocking them out steadily, until now.
Hopefully if it is a bug, it gets fixed "soon"?
Anyways, thanks to anyone able to shed some actual light on this problem.
Ps. Past week I've been seeing PS4 Error Code (CE-34878-0) multiple times a day. Rebuilt my database multiple times to no avail. Didn't have this issue a week ago.
1. Tidal Basin Combat Merit
2. Tidal Basin Discovery Merit
These were the last 2 I needed, in their respective categories.
I was waiting until I completed this week's Invasion event with a friend of mine.
Well, upon completing this week's invasion (heroic), those 2 commendations have become locked with the message "Continue to explore Washington DC to unlock this commendation".
Is this a known issue? I have never experienced this myself until 45mins ago.
I have restarted the game. I have restarted my system. Both to no avail.
My commendation score is 3745, in case anyone might be thinking I don't know what I'm doing.
Just super frustrated. I started working on commendations this week and have been knocking them out steadily, until now.
Hopefully if it is a bug, it gets fixed "soon"?
Anyways, thanks to anyone able to shed some actual light on this problem.
Ps. Past week I've been seeing PS4 Error Code (CE-34878-0) multiple times a day. Rebuilt my database multiple times to no avail. Didn't have this issue a week ago.