The functions that default to keys [ and ] don't seem to be doing what they're supposed to. Instead of cycling through all the targets, they seem to cycle through some subset of the targets on the radar. I've watched it go through ~3-4 targets out of ~7-8 total, so I have to resort to selecting the target in front of me and aiming at them individually (When I'm searching for a recon, for example).

A.) Has this issue been addressed before?
B.) Is it just me?
C.) Am I misunderstanding the function of those keys?

(Linux version)

that command is kinda odd because of how objects are determined to be 'next'. You're right in that it doesn't work as expected.

oops that was me posting as my wife accidentally because i forgot to log her off.

Ok, Ray...if you say so.

(pssst, fellas...I think Ray and sarahanne are one and the same...shhhhh)

Eww ray, you're logging off your wife?

Maybe some (other?) command could iterate through the objects based on their distance away from you. Then, instead of being ambiguous about who is "next," it just picks the next farthest away. (I assume that in the process of crunching the geometry, it wouldn't be too hard to cache the distance or distance-squared to each object.)

And if something moves closer than the current target before you switch, then you just miss it until the next round.. Maybe even have an opposite command that selects the next nearest object. I could live with that as long as I can actually find a recon in a mess of other bots - rather than going drone x, none, drone x, none, ... when there are 3+ blips on the radar.

May I also quickly suggest that there be a deselect all targets key? I know you can aim at empty space and hit "select next in front" or whatever, but it's just such a pain.

Nope, I do exist. It just means that Ray was working from home for a change.

The [,],{ and } keys are useful for targeting station components. (not that you can do much to them anyway, but it's cool to see what they're called.) Sometimes you can target a roid or Iceyo.