Hello Commanders,
With the 3.0.3 update a speculative fix was introduced for the Comms Panel issue, and we do apologise that it seems to have not made it into our patch notes! From reports we've seen so far, it would appear this fix was successful in rectifying the issue, but if you still experience any trouble please do let us know right away.
Do Random Mission offers/messages arriving in our INBOX and interfering with existing mission progression count as a Comms Panel Issue?
There are reports coming in after the 3.03 update that Assassination Missions are still being stalled if an Alternate Target is offered to the player via a Comms message into the INBOX.
The original mission can not be updated to show the planet/target location using the ADS until that alternate mission offer is located in the INBOX message list and either deleted or accepted. Until the player actively engages with that message, the original mission will not update when the system is scanned/honked.
ISSUE #2 / Planetary Scan Job Missions Failing to Complete Due to Rogue Inbox Messages
A similar issue is also still happening in 3.03 with Planetary Scan Job Missions. If during the process of physically completing the scan mission the player's ship receives ANY random mission offer/message between the Scan Job's "Nav Beacon Scan Data" message and the final "Mission Successful" message, the latter WILL NOT post to the INBOX and the Scan Job mission will not complete, despite all surface objectives being met!
In order to complete the now stalled mission, the player must first DELETE the Random mission offer that clogged the process, and then return to the outpost/building on the surface, rescan the beacon and return to their ship. This will complete the mission, but will also subject the player to a duplicate bounty.
If the player is unlucky enough to have yet another random mission offer or message come in while the second attempt is ongoing, the mission will once again fail to complete.
It took me several hours of testing and experimenting to confirm the above bug is indeed real, and does indeed cause the entire scan mission to glitch and not complete properly.
All due to totally unrelated mission offers entering the inbox before the 4 message Scan Job thread is received by the player's ship uninterrupted by any other INBOX activity.