Any one done assassinate missions since 3.3?

Nope. There is literally no update to anything when this occurs. Nothing in messages, nothing in mission description for updates.

My usual process is:
- Jump in, cruise around a minute or two, check if target spawns.
- Stop, use FSS to see if I can find a mission target source.
- Drop to the nav beacon and scan it
- Check messages
- Check mission description
- Relog and repeat, just in case.

If I go through that twice, I then jump into supercruise for 5 minutes or so. If I still dont see the target, I abandon. At the time of abandoning, the text will still say "Target Body: Currently Unknown, Scan Required" despite the multiple scan mechanisms used.
This also happened pre-3.3

This is the SOP. I would add, if the mission turns into a wild goose chase across multiple systems I abandon it. I followed one of those once and it really is a waste of about 20 mins to find the pirate when you can kill the mission and pay a donation to get the rep back much easier. Its really fun when I stack 2-3 kill pirate missions and they all jump me in the same instance. Last night it was me vs 2 pirate lords in their vettes. Good times.
 
I usually just hit the nav beacon and that pops a bunch up.

Slightly off topic, can we get rid of the assassination missions that make you go to a different system and wait for some dope in an Eagle or Cobra contract you with the info? There really is no point to them but hassle.
 
I usually just hit the nav beacon and that pops a bunch up.

Slightly off topic, can we get rid of the assassination missions that make you go to a different system and wait for some dope in an Eagle or Cobra contract you with the info? There really is no point to them but hassle.

I agree. What really sux is there's no way to know which missions will turn into this. I'll stack 2-3 knowing that 1 of those will have to be canceled due to this idiocy.
 
I attempted one the other night.

I'd switched from my Krait to my Corvette, jumped to the target system and almost immediately got interdicted by the target.

"Excellent", I thought, "That'll save me some time."

Sadly, I hadn't flown the Corvette for some time, and foolishly I failed to check the power requirements before heading out.

Less than 15s after the interdiction, with shields still down, I was back at the rebuy screen.

Schoolboy error, but an expensive one. :(
 
I took 2 missions yesterday... arrived at Nav beacon, scanned it, no update but target dropped in like usual.
 
Last edited:
I attempted one the other night.

I'd switched from my Krait to my Corvette, jumped to the target system and almost immediately got interdicted by the target.

"Excellent", I thought, "That'll save me some time."

Sadly, I hadn't flown the Corvette for some time, and foolishly I failed to check the power requirements before heading out.

Less than 15s after the interdiction, with shields still down, I was back at the rebuy screen.

Schoolboy error, but an expensive one. :(

50% of the time when the pirate interdicts me, he's not there when its time to rumble. Very annoying.
 
Incorrect.

If you scan the nav beacon, all USS at any range are visible and identified instantly.

I'll video the next bugged one I get. It's easy to think you never get them... you can get a run of 30/40 odd and not have problems. I'm *pretty sure* it needs to be a chain-mission assassination to see the bug (as they use a different template), not a standard one.

Yes it was a chained mission actually!! Now i remember! as i reread the posts.
 
The only bug I've seen so far with assassination missions is that one mission couldn't be resolved because the target was not actually labelled "Mission target." Name matched, he was in the signal source, but killing him didn't resolve the mission. After trying three times, I abandoned the mission. I've seen similar bugs with planetary scan missions too. Fortunately, in both cases they seem to be rare.

I've had this happen too. I killed the guy four times just to be sure, but never could complete the mission.
 

Vanguard

V
I'll video the next bugged one I get. It's easy to think you never get them... you can get a run of 30/40 odd and not have problems. I'm *pretty sure* it needs to be a chain-mission assassination to see the bug (as they use a different template), not a standard one.

The changes to the FSS and how they impact the mission system are great for actually completing them (especially once you've really gotten to grips with the new stuff) but you'll probably be happy to know that it also helps us to more accurately identify any issues you might run into and confidently fix them for you. If you identify a consistent set of occurrences that seem to suggest an issue then grab as many details as you can and drop them in the bug reporting forums and we'll be able to investigate with much higher precision.

I've had this happen too. I killed the guy four times just to be sure, but never could complete the mission.

This is a great example of the above (though unrelated to the FSS) however we'd need it on the bug reporting forums with a bit more information that we could use to reproduce it.

Overall, we're very glad that you're enjoying the new mechanics.
 
I've had this happen too. I killed the guy four times just to be sure, but never could complete the mission.
.
I did a bug report about this effect during the beta. It was one of the few, which QA people actually acknowledged and reported to be looking into. But as it happens sporadically (I was unable to reproduce the bug), it's probably also a hard one to track down.
.
 
The changes to the FSS and how they impact the mission system are great for actually completing them (especially once you've really gotten to grips with the new stuff) but you'll probably be happy to know that it also helps us to more accurately identify any issues you might run into and confidently fix them for you. If you identify a consistent set of occurrences that seem to suggest an issue then grab as many details as you can and drop them in the bug reporting forums and we'll be able to investigate with much higher precision.

Just throwing back to this thread that I can now absolutely confirm that it's Chain Assassination missions only which are bugged.

For 5 "standard" assassinations, all had their USS findable either with the FSS or using a nav beacon.

For a further 10 "chain" assassinations, none had a findable USS either using the FSS or Nav Beacon, and their text never updated to provide a near body or location in-system such as a shipping lane. I had to rely entirely on being interdicted by the target, or interdicting them myself which didn't happen in some cases.

Bug report here: https://forums.frontier.co.uk/showt...SS-in-the-target-system?p=7291342#post7291342
 
Last edited:

Deleted member 115407

D
Previously I used go to the Nav Beacon as instructed.
Target the Beacon and a scan is automatically done, at the end of which I get target planets.
Often if I linger long enough at the Nav Beacon the targets appear out of supercruise.

Since 3.3 I took two missions to the same location.
Scanning the Nav Beacon reveals nothing, and also using the ping does not give information.

Is there a new way to locate targets or this may be a bug?

Work fine for me. I've been doing them all day.

Use the FSS to locate your target's signal source.

Just throwing back to this thread that I can now absolutely confirm that it's Chain Assassination missions only which are bugged.

For 5 "standard" assassinations, all had their USS findable either with the FSS or using a nav beacon.

For a further 10 "chain" assassinations, none had a findable USS either using the FSS or Nav Beacon, and their text never updated to provide a near body or location in-system such as a shipping lane. I had to rely entirely on being interdicted by the target, or interdicting them myself which didn't happen in some cases.

Bug report here: https://forums.frontier.co.uk/showt...SS-in-the-target-system?p=7291342#post7291342

Nice catch
 
Last edited by a moderator:
Back
Top Bottom