Wing Beacons: Default to On
- Thread starter Azuvector
- Start date
Only useful when in a wing anyway. It does seem to be a pretty obvious suggestion.
I agree on this, I see very few times when not having the wing beacon active is useful. So default on would be the preferred option.
Alternatively, having this as a toggle option like voice comms, should wing beacon be enabled by default, yes/no.
Alternatively, having this as a toggle option like voice comms, should wing beacon be enabled by default, yes/no.
Oh wait, hang on...
Spotted an issue a month or so ago: Two players in a wing, both with wing beacons on and we were trying to drop in on the same, fast moving signal. Can't recall what it was exactly but whoever dropped second was hundreds of km from the other every time.
Then I turned my nav beacon off, while they left theirs on and dropped in first. The very next try I dropped in right on top of my wingmate, problem solved. So yeah, I can think of one reason not all wingmates want their beacon on at the same time.
Will edit if I remember what the instance type was.
Edit: Might have been a wing assassination target
Spotted an issue a month or so ago: Two players in a wing, both with wing beacons on and we were trying to drop in on the same, fast moving signal. Can't recall what it was exactly but whoever dropped second was hundreds of km from the other every time.
Then I turned my nav beacon off, while they left theirs on and dropped in first. The very next try I dropped in right on top of my wingmate, problem solved. So yeah, I can think of one reason not all wingmates want their beacon on at the same time.
Will edit if I remember what the instance type was.
Edit: Might have been a wing assassination target
Last edited:
Well the problem I have seen is when you have nav locked your wingman. This can create all sorts of issues. But this nav lock is another action that you have to enable/disable.
Most notably we have encountered this around gas giants with rings. Either to drop into targets in the rings or signals sources around the planet. Turning of navlock fixes this, but you now have to fly there and drop in on the signal.
[edit]
This is most likely a bug, as this did not use to be like this.
Ok, but under this proposal it would just default as on. You could still turn off the beacon for whatever reason.
It’s still much more convenient to have it on by default than off.
Yup, yup, and yup.
Just pointing it out because the issue mentioned took a few tries to narrow down and work around, for experienced players. If the default is on, new players may not even realise there's an option to turn it off because there's no need to go looking for it.
It's still a great observation, and implementable solution.
please and thank you. I don't know how many times I've joined a wing only to be reminded 15 minutes later to turn on the beacon, which should have been on from the start.
This. All the time.
Another +1 from me for wing beacon defaulting to on. Or at least, if it defaults to off, it should remember what you've set it to and stay on after you've set it on once, even if you do log out and back in.
This should also be fixed, though - it should wait until you've dropped to normal space before sending the "wing drop" signal to other members, or they drop at your position when you pressed drop, not the position you actually dropped to, which is fine if you're just dropping in the middle of nowhere and completely useless if you're dropping onto a signal or get interdicted because your position when leaving supercruise is not your position when entering normal space.
But nothing to do with wing beacons other than you *can't* nav lock someone who doesn't have their beacon turned on. Which is not generally the sort of thing you want to be messing with in situations where you really need nav lock to be working.
This is an issue with how nav-lock works - not the wing beacon itself. Certainly nav-lock shouldn't default to being on (and couldn't, since you need to pick a specific wing member to lock).
This should also be fixed, though - it should wait until you've dropped to normal space before sending the "wing drop" signal to other members, or they drop at your position when you pressed drop, not the position you actually dropped to, which is fine if you're just dropping in the middle of nowhere and completely useless if you're dropping onto a signal or get interdicted because your position when leaving supercruise is not your position when entering normal space.
But nothing to do with wing beacons other than you *can't* nav lock someone who doesn't have their beacon turned on. Which is not generally the sort of thing you want to be messing with in situations where you really need nav lock to be working.
I guess it's a bit like having the SRV cargo scoop auto deployed by default or having the ship auto request docking permission when dropping at a station. Yes in theory the game could do these things for us at little or no real cost but by not doing so it adds to the immersion of being a starship pilot and having switches we need to flick at appropriate moments. Personally I prefer the immersion of these things not being on by default.
Also valid points, but where does one draw the line?
The scanner zoom in my SRV always resets to zero on deploy...
Not quite annoying enough for a bug ticket, yet...
The one in the ship used to, now it persists across menu logs...
Yay, but why also persist when swapping my ship?
New FSA frequency tuner bar always defaults to centre on exit...
Posted a ticket yesterday, cos it's doin my head in!
If Beyond is the QoL tweak patch, they missed a bunch of stuff
It's called Navlock, my amigo
Yes! Default to on!
+1 for the suggestion.
Absolutely!
+1
+1
I agree with the OP. There's no reason I can think of why you wouldn't want the rest of your wing to know where you are. Unless you've fallen out with them, of course.
Nav-lock should be left as it is, however.
Nav-lock should be left as it is, however.
i am sure you have to turn it on manually, because now with squadrons, you can turn it on as "squadron beacon"
*opens up beta*
*looks at the wing beacon switch*
*sees nothing changed*
meh
really, they even went through the process of giving this a place in the new interface instead of having it turned on permanently
if i remember that correctly, it even has two places (in chat interface too)
*opens up beta*
*looks at the wing beacon switch*
*sees nothing changed*
meh
really, they even went through the process of giving this a place in the new interface instead of having it turned on permanently
if i remember that correctly, it even has two places (in chat interface too)