Are the Rare Artwork Salvage Missions Broken?

I took one of these missions and went to the system where I was to search. I scanned the nav beacon, but I didn't get any sort of mission update saying which signal source I was meant to fly to in order to recover the artwork. I also took a black box recovery mission at the same time (but different system), which did work. Am I doing something wrong with the artwork mission? From what I remember when I last did one (which would have been a few months ago) these missions worked pretty much like the black box recovery ones where we can either scan the nav beacon and get told where to look for the mission items, or we can do the FSS and find the orange signal source that we're meant to go to. This current mission isn't giving me either one.
 
I routinely and frequently accept salvage and black box missions, including rare artwork salvage missions. I encounter what seems like random occurrences of mission failures just as you describe - that is to say that the mission site is simply not to be found. It's just not there. I doubt that you're doing anything wrong.

My preferred method to complete these missions is to fire up my FSS and find the mission site that way. This is much quicker than visiting the Nav Beacon over 90% of the time and works very well.

A quick way to tell if the mission is doomed to fail is at the moment you drop in to the target Star System. You'll note when you're on one of these missions, that your ship's COVAS immediately reports "mission objective detected" when you drop in to the target Star System. When the mission is doomed to fail, no such report is made so you'll know right away.

I've done this countless times and began noticing that the lack of a COVAS announcement was indicative of a problem.
 
its more of s server networking problem if mission objectives dont appear this is very true of ground settlement objectives too where very often simply logging out then back in can make them appear as they should..........
in space this may mean also jumping out of the system & relogging so upon entry you get the mission objective detected message
but as mentioned above sometimes they just get

LOST IN SPACE! (or in the servers;))

as for fd fixing this they cant its inherit of syncing an amazon based ec2 peer to peer network
 
Last edited:
I have tried departing the system and returning, usually as I complete other missions and loop back towards the issuing system. I believe I have infrequently had success in then finding the mission target, but I have not intentionally kept track of that. I know that the majority of the time, this by itself doesn't help.

I'll try relogging (along with depart & return) and see what happens. Thanks for the suggestion.
 
Back
Top Bottom