Warning for the horn honkers(related to double scan glitch)

[dognosh]

(Horn Honking= initial mass scan with your advanced scanner)
If you are trying to get to a region and are mostly traveling through systems, I will guess you scan entry star and honk horn ? then go to next system ?

On rare occasions after honking horns and getting "23 Systems Discovered...etc" or similar, don't just leave ! look in scanner or left UI panel for unknowns, because if there aren't any then your scan was unsuccessful and you have to honk again !

Even if there are only 10 bodies in that system, that is at least 5000 Cr lost, and over 1000-2000 systems it can build up !

 

[Fenric]

(Horn Honking= initial mass scan with your advanced scanner)
If you are trying to get to a region and are mostly traveling through systems, I will guess you scan entry star and honk horn ? then go to next system ?

On rare occasions after honking horns and getting "23 Systems Discovered...etc" or similar, don't just leave ! look in scanner or left UI panel for unknowns, because if there aren't any then your scan was unsuccessful and you have to honk again !

Even if there are only 10 bodies in that system, that is at least 5000 Cr lost, and over 1000-2000 systems it can build up !

After having this happen a few times I just got in the habit of waiting until the star I warped in at becomes target-able to do my disco-scan. If it's lagging, you won't be able to target the star either, so I just wait and see. Also, you can usually just look at the radar and see things pop up instead of looking at the navigation panel.

 

[dognosh]

After having this happen a few times I just got in the habit of waiting until the star I warped in at becomes target-able to do my disco-scan. If it's lagging, you won't be able to target the star either, so I just wait and see. Also, you can usually just look at the radar and see things pop up instead of looking at the navigation panel.

Correct, mostly but sometimes if you don't discover suns, just planets, it doesn't show on scanner, correct ?

 

[AsukaZ]

Noted, thank you.

 

[lolanon]

I've had it could of times today. Quite annoying.

 

[Bacon Sarnie]

This is happening all too much lately.
I started double honking systems that only show the star and nothing else to be sure that its correct.
Noticed it was doing this about 5 days ago.
Who knows if I've missed any before, best not to think about it, after all Im not out here for the money anyway but it does help.

 

[Fenric]

Correct, mostly but sometimes if you don't discover suns, just planets, it doesn't show on scanner, correct ?

I suppose if the system has one star and planets that are thousands of Ls away, they might not show on the radar. However, I've found if I always wait for the star at the warp in point to become target-able, the discovery scanner never fails (lags).

 

[Rikk]

Good call!

I tend to use a combo of the number of things and whether there are planets showing on scanner. Few items, no planets, I currently assume belts.

I will start having a quick look at system map.

 

[Galten75]

Yeah, I believe Ziggy Starduster are correct, we are to eager to honk loading up before we even fully arrives. Easy up on the explorer reflexes guys.

// G

 

[wilkie79]

Try this in Voice Attack (if using), it fixed the problem for me:

---
Say Scan system

Begin Condition : [scan] Has Not Been Set
Set [scan] value to 1
Say, 'Scanning system' or 'Scanning'
Click right mouse button - set to 6 seconds (The binding I have for scanning systems)
Pause 0.1 seconds
Press Enter key and hold for 0.1 seconds and release (The binding I have for hardpoints)
Pause 0.1 seconds
Say, 'Scanning completed' (and wait until it completes)
Pause 8 seconds
Say, 'Hardpoints Retracting ' (and wait until it completes)
Set [scan] value to [Not Set]
End Condition - Exit when condition met
Begin Condition : [scan] Has Been Set
Say, 'Please wait' (and wait until it completes)
End Condition - Exit when condition met
---
Say Open system map or Open galaxy map

Begin Condition : [scan] Has Been Set
Say, 'Please wait' (and wait until it completes)
End Condition - Exit when condition met
---
Next time you view the system map or the galaxy map, the system bodies are displayed.

 

[Kancro Vantas]

Noticed this. I always look for system map and also double honk if only star shows up just to be sure

 

[CMDR AKIRA MASAKARI]

Not sure about this, but I think it happened more often when loading up the foghorn upon entry. Seemed if I waited a couple of seconds it worked fine.

This one, if you let to many scans to run simultaneusly, it can glitch.
When you enter a system, wait for the main star to be autoscanned before honking the horn.
And don't honk the horn while surface scanning the main star, that could glitch too.

 

[Sapient6]

This one, if you let to many scans to run simultaneusly, it can glitch.
When you enter a system, wait for the main star to be autoscanned before honking the horn.
And don't honk the horn while surface scanning the main star, that could glitch too.

I played around with this approach for a while, but it adds so much extra time that I just don't feel like it's worth it for what is usually very infrequent problem.

At this point I Honk immediately upon entry while lining up with the main star. I select the star to begin its surface scan as soon as that becomes available, usually just a second or two before the horn fires. While the surface scan is running I switch over to the system map to see if there is anything of interest. If it's just the main star then I'm back out to the front view pretty quick, usually with enough time to fire off a second honk before the surface scan on the main star completes.

For long range trips the extra seconds spent in the transient systems can add up quickly, so giving up five seconds here and there just to be extra sure that the discovery scanner does it's job in a single pass starts feeling costly to me.

 

[CMDR AKIRA MASAKARI]

I played around with this approach for a while, but it adds so much extra time that I just don't feel like it's worth it for what is usually very infrequent problem.

At this point I Honk immediately upon entry while lining up with the main star. I select the star to begin its surface scan as soon as that becomes available, usually just a second or two before the horn fires. While the surface scan is running I switch over to the system map to see if there is anything of interest. If it's just the main star then I'm back out to the front view pretty quick, usually with enough time to fire off a second honk before the surface scan on the main star completes.

For long range trips the extra seconds spent in the transient systems can add up quickly, so giving up five seconds here and there just to be extra sure that the discovery scanner does it's job in a single pass starts feeling costly to me.

Yes my approach wastes up to 30 seconds per jump. It has to do with how you want to explore. I prefear to take it easy even when i'm rushing toward a POI. In fact, even if i don't surface scan, i was never able to make more than 500Ly/hour with a 33 Ly jump range.

 

[lolanon]

Because I zero throttle before I enter a system, I need to accelerate before jumping again. I tend to honk when my fsd is cooling down. I play on a game pad and have accelerate and scan on my right trigger and bumper so tend to hold both down.

So I end up honking on enter and exit of a system.

 

[Greyhawk]

Is this related to the double detailed scan you have happen occasionally? Where the detailed scanner says you have acquired detailed info then the scanner immediately starts rescanning the same target. Pain in the rear.

 

[Gelegeus]

Is this related to the double detailed scan you have happen occasionally? Where the detailed scanner says you have acquired detailed info then the scanner immediately starts rescanning the same target. Pain in the rear.

A bit of both. If you ADS the system it comes back as completed, but nothing appears on the scanner or the system map (other than the main star). You then have to do the ADS again. We explorers learn to live with these glitches. Imagine if the pew pew brigade had to blow up a NPC twice to get the bounty.

I did a speed run for an hour today and managed 40 systems, all ADS'd, scooping at every available star and detail scanning every main body. At an average jump of 28Ly, thats over 1000Ly/Hour. In that hour I had to double honk around times.

 

[Nilt]

Imagine if the pew pew brigade had to blow up a NPC twice to get the bounty.

Heh, that's an excellent point. I imagine they'd storm FDevs with torches and pitchforks email pictures of barnyard animals or something.

 

[Greyhawk]

Its especially bad when it takes such a long time to scan something.