Can't Select the Correct Path when Projected and Current Trajectories are too Close

[Sauron]

I've (and so have you ) worked around this in all sorts of very involved ways (dragging maneuver nodes backwards from the projected trajectory onto the current trajectory...), but it's an extremely serious usability issue that's completely unacceptable even in an alpha. There are many trivially easy fixes/workarounds to this problem that should have been implemented ages ago (for example a hotkey to create a maneuver ~1 minute ahead of you which could then be dragged as needed wouldn't solve the problem, but it would mitigate it.) Precise node isn't a great solution considering the fuss involved in inputting the correct time. But this issue has to go sooner rather than later.

The really obvious but very non-optimal (but still preferable) solution would probably be to prioritize the current trajectory. Better yet, the option to hide one or both would do the trick.

Edited February 22, 2014 by Sauron

[AlamoVampire]

Agreed! +1

[Dunbaratu]

Yes this is annoying. Another possibly related problem is when two or more vessels are close to each other, you are unable to pick which ship you meant to target on the map view. It keeps redirecting your click to the wrong one of them. This might be related because both that complaint and this complaint in this thread seem to be a case of being a bit weird about how it handles "near" clicks. It seems that a mouse click has a certain radius around it and if a thing is in that radius then the click is near enough to be counted as clicked on that thing. The problem is when there's more than one thing within that radius, it doesn't seem to select the one that's closest to the click. It just selects the first thing it finds it its data structure that fits the nearness criteria even when there's aother thing that would be even nearer. Thus when two objects are both within the click-radius of each other, it's nigh impossible to get the game to realize you meant the "second" one it finds.

At least that's my guess about what's happening because that's what it looks like from the user's point of view. If that's what's happening then the fix would be to find ALL hits within the click zone and select the one of them with the least distance from the click, rather than just stopping on whichever hit is discovered first.

[thereaverofdarkness]

I think the problem is that the click radius is measured in game distance, not screen distance. Zooming in should make it easier to select the exact thing you want, but it doesn't.

The maneuver node issue also happens on trajectories going pretty much down into the ground, even when there is no secondary trajectory to cover up the primary.

[Doozler]

I found this prolem really bad trying to do a planetary burn away from kerbin, where I was trying to click a node but had to deal with all the flags, stations, etc that are all on top of each other.

One way to deal woul be that hovering the mouse over the close trajectories/ craft brings up a quick-pick list that you could then select from.

[Nuke]

just fade out the other trajectories, your own, and that of your target if you have one are the only ones you are really concerned about.

[Sauron]

just fade out the other trajectories, your own, and that of your target if you have one are the only ones you are really concerned about.

Not primarily the issue. It's more about interplanetary transfers--can't access what you need to through the trajectory that appears after a maneuver node.