I think I figured out why so many of you explorers are having honk issues...

  • Thread starter Deleted member 115407
  • Start date

Deleted member 115407

D
The first time you run a honk with the built in discover scanner (or detailed surface scanner), you need to run it from FSS mode. After that you can run it from combat mode.

Seems to apply to each ship.
 
The first time you run a honk with the built in discover scanner (or detailed surface scanner), you need to run it from FSS mode. After that you can run it from combat mode.

Seems to apply to each ship.

You mean analysis mode? Will have to double check when I get back in. I've never used the honk in the FSS, though I hear it can be done.
 

Deleted member 115407

D
You mean analysis mode? Will have to double check when I get back in. I've never used the honk in the FSS, though I hear it can be done.

Yeah, I don't know what the modes are called - I haven't committed it to memory yet.

But if you try to honk from the built in DS, you get a "not in this mode" message. So if you switch to discover mode and honk, then you will be able to just honk from the cockipit. Then I noticed that my countermeasures (chaff and PDM( say "Not in this mode"

So there is obviously some confusion happening.

P.S. Sorry for the typos. Just trying to play and type at the same time.
 
Last edited by a moderator:
Nope, no honk in combat mode for me in supercruise leastwise at all. Module can't be used in this mode notification. Tested between switching back and forth several times, between a few systems just now, and switching modes before jumps.

Works fine when switching to the "correct" mode though. I just assumed it's working that way intentionally for whatever reason.

Not a biggie for me. Can't shoot my guns in supercruise anyway.
 
Last edited:

Deleted member 115407

D
Nope, no honk in combat mode for me in supercruise leastwise at all. Module can't be used in this mode notification. Tested between switching back and forth several times, between a few systems just now, and switching modes before jumps.

Works fine when switching to the "correct" mode though. I just assumed it's working that way intentionally for whatever reason.

Not a biggie for me. Can't shoot my guns in supercruise anyway.

Hmmm... strange
 
For what it's worth... yeah

I fly in supercruise w/the discovery scanner on one trigger and the DSS on the other. (xbox)
(This being a certain fire group.) - So, while flying in analysis mode...
I can honk any system while jumping to collect the star data.. and misc info.
I can fly toward a body with it targeted and it automatically discovers it like one would have done in FSS mode with resolving the image.
As soon as I am close enough for probes with the DSS, it will read 'too fast' instead of 'out of range', and I simply pull the trigger to enter the DSS mode. Fire off the probes to map the body and exit the mode.

Also... all the mining weapons will work in analysis mode.
This is handy, of course, because of the additional scanner for the rocks being used in that mode.

I still need to tweak my bindings a bit, and how some of my fire groups have multiples on the same trigger... which only work when in the proper mode, etc...

I don't have all the answers, but I've found the system to be quite comfortable.
It seems flexible and able to adjust to a few different styles of exploration in my limited (in-bubble) experience.

Cheers.. and all the best on your flights! o7
 

Ah, was wondering what you were talking about there for a minute. But yeah, I hear in the bubble already discovered systems have targetable bodies without the FSS needing to be gone through first. Not the case out in the black for undiscovered bodies I'm afraid... grumble, grumble.
 
Last edited:

Deleted member 115407

D
Ah, was wondering what you were talking about there for a minute. But yeah, I hear in the bubble already discovered systems have targetable bodies without the FSS needing to be gone through first. Not the case out in the black for undiscovered bodies I'm afraid... grumble, grumble.

Mmm... even discovered bodies need a scan for me. I was in a well known pristine system trying to map the rings, but it wouldn't let me DSS until I ran a basic scan.

I just think the whole thing is buggy.
 
Mmm... even discovered bodies need a scan for me. I was in a well known pristine system trying to map the rings, but it wouldn't let me DSS until I ran a basic scan.

I just think the whole thing is buggy.


Yeah whole system is misbehaving. Additionally I am out some 30kly in pretty blank area and the Codex is hit or miss on updating. Working as expected I guess.
 
Mmm... even discovered bodies need a scan for me. I was in a well known pristine system trying to map the rings, but it wouldn't let me DSS until I ran a basic scan.

I just think the whole thing is buggy.
Hmm, that sounds odd. Here’s what the general case is:


- If a System has never been discovered before (so never had data handed in to UC), all you will see are things within passive scan range. Honking will detect and L3 scan all stars. If you enter the SysMap at this point, al you will see are the stars and anything within passive scan range. You will need to enter the FSS to detect and identify other bodies. Locating a body in the FSS will give you a full L3 scan of the body (i.e. what the DSS scan used to provide) and will also identify any significant surface signals by general type - geological, biological, Human, Guardian, Thargoid.” - and show numbers of signals detected.

- If you enter a system which has had data handed in to UC, then the bodies will show up on entry to the system but with limited (L1 I think) data, and will show as Unexplored. They will be visible on the SysMap, in the HUD and on the Scanner display. You can enter the FSS mode to scan these bodies. You can also target them and when close enough L3 scan them (which is pretty much exactly the same as DSS scanning used to be). Also if you fly to within the Discovery Scanners’s passive scan range you’ll get an L3 scan on those bodies. If you’re close enough to use the new DSS probes, you’ll be well within the Discovery Scanner’s passive scan range, so there shouldn’t be a situation where your close enough to use the probes but can’t because the body hasn’t been scanned (not sure what was happening in your case!)

- If you enter a system where all body info was public previously (i.e. Sol, Achenar, the starter systems, etc.) then as I understand it you should still get all that info.
 
Yeah whole system is misbehaving. Additionally I am out some 30kly in pretty blank area and the Codex is hit or miss on updating. Working as expected I guess.
Just checking here... what is it that the Codex doesn’t seem to be updating with for you?
 
Maybe I can use combat mode to not discover things in a system? Been noticing discovery type notifications pop up even when I don't honk. Not sure if I always want to leave a trail everywhere I go in the game.

I'm sure no one cares what I'm up to all that much. Just the thought of it in immersive terms being out alone in the black seems kind of strange to me.

Cheers.
 
Last edited:
Yeah, I don't know what the modes are called - I haven't committed it to memory yet.

But if you try to honk from the built in DS, you get a "not in this mode" message. So if you switch to discover mode and honk, then you will be able to just honk from the cockipit. Then I noticed that my countermeasures (chaff and PDM( say "Not in this mode"

So there is obviously some confusion happening.

P.S. Sorry for the typos. Just trying to play and type at the same time.

Confirmed - this is exactly what happened to me.
 
Back
Top Bottom