What's this "need scan" nonsense now required to drop on a low wake?

It makes no sense to be needing to scan a low wake when you are dropping on a target. It's a fixed point in space where a ship has dropped... so why?

[down][down][down]

---

EDIT: Seems to apply only to dropping out on CMDR's low wake i.e. players.

To answer the next question... at first I thought my buddy (who spotted this) must have been targeting a hi-wake but just now we checked this out and it is most definitely a player low wake that needs a scan to drop into.
 
Last edited:
Are you sure? Since when?
edit: I just droppend out of SC on a low wake left by NPC outside the station. No problem. (other that there was no station nearby)
 
Last edited:
Most probably it was a high-wake instead of a low-wake. To follow a high-wake you need of course the wake-scanner - or you manage to eyeball the destination star by aligning the center-vector of the wake with a star from you navigation panel...
 
Are you sure? Since when?
edit: I just droppend out of SC on a low wake left by NPC outside the station. No problem. (other that there was no station nearby)


I should have added - this only seems to apply to the low wakes of CMDR's (players). NPC's are fine.

Most probably it was a high-wake instead of a low-wake. To follow a high-wake you need of course the wake-scanner - or you manage to eyeball the destination star by aligning the center-vector of the wake with a star from you navigation panel...

At first I thought my buddy (who spotted this) must have been targeting a hi-wake but just now we checked this out and it is most definitely a player low wake that needs a scan to drop into.
 
Last edited:
I followed a friends low wake yesterday without scanning it

We were not winged up to avoid issues with with Core Mining, so was just like following a random player
 
This is happening and it was a low wake that resulted in a "need scan" message for me as well, not a hi wake. It was a fellow live player.

GunnerBill wasn't hallucinating or mistaken. Never happened to me until after this last update.
 
Last edited:
Happened to me twice since 3.3.

Random CMDR (not a friend/wingmate) in SC, drops to normal space, but you cannot follow his low wake because of this "need scan" nonsense.
 
I followed a friends low wake yesterday without scanning it

We were not winged up to avoid issues with with Core Mining, so was just like following a random player

Curious how that worked out for you. Did you 'get the graph' regularly, and all Core Deposits worked properly when in un-wing?
(sorry for off topic burst)

\\///
Oo
>
Spike.K
 
Curious how that worked out for you. Did you 'get the graph' regularly, and all Core Deposits worked properly when in un-wing?
(sorry for off topic burst)

\\///
Oo
>
Spike.K

Multicrew, I as gunner got the graph but the asteroid yielded nothing.
Winged up my wing mate did not get the graph but the asteroid at least yielded fragments
Unwinged graph and fragments appeared

I was initially in MC
Then when that failed, brought my ship over but wasn't mining equipped, just a scout to eyeball fractures for cores so cannot comment on if everything would have worked for both of us
 
It's a very old bug, was already happening back in early 2015. It's been mostly fixed, but I see it crop up every once in a while.
 
It's a very old bug, was already happening back in early 2015. It's been mostly fixed, but I see it crop up every once in a while.

It is?

I don't doubt you but in my 3000+ hrs game play since commercial release I've only ever seen this since the recent update!

Any idea of the trigger, is it limited to a specific volume of space or tied to the player??
 
It is?

I don't doubt you but in my 3000+ hrs game play since commercial release I've only ever seen this since the recent update!

Any idea of the trigger, is it limited to a specific volume of space or tied to the player??

This is the screenshot I used to open a ticket on Jan. 13th 2015 :D

The issue happened, back then, with some low wakes left by other players, and even then not always and not tied to any player in particular. I'm relatively confident it was mostly patched out as I've only encountered it once or twice after that in the course of these 4 years.
 
This is the screenshot I used to open a ticket on Jan. 13th 2015 :D

The issue happened, back then, with some low wakes left by other players, and even then not always and not tied to any player in particular. I'm relatively confident it was mostly patched out as I've only encountered it once or twice after that in the course of these 4 years.

Cloud not scanned! I mean I *remember* that but when did it change to "Wake"?

+1
 
Back
Top Bottom