Control Sensitivity - Changing Maneuver Vectors

[BentRim]

I am learning how to use maneuver nodes.  When I attempt to use my mouse to drag the prograde (or any) vector I find that it is too sensitive and I overshoot my intended value.  The same thing happens when I try to use the mouse wheel to adjust the vector.  I find this frustrating, and I seem to spend more time just trying to adjust the node with the mouse to get the vector where I want it to be.  Does anyone else have this issue?  I am spending most of my time going through the tutorials to learn transfers and docking.  My version is 1.2.2 and is stock unmodded.

It would be nice if there were an alternate way to adjust the node vectors either with control focus and the keyboard or by entering a numerical value,  or is there and I am just missing it?  

Any suggestions? 

[FancyMouse]

That's one of the two reasons why I'm using PreciseNode (provides you numeric input and also changing node in a completely different window independent of where current map view is). With pure stock - unfortunately that's what we have. When I'm in the mood of dragging the vector without the help of the mod, I usually slowly extend the handle until I'm satisfied with the speed, and then I keep cursor steady and wait - it's better to wait for a few seconds than screw up the whole thing and readjust all over again.

Edited January 10, 2017 by FancyMouse

[FullMetalMachinist]

When dragging the handles, if you 'push' instead of 'pull' it's a slightly finer adjustment. So if you want to add just a bit of prograde, push the retrograde handle towards the middle instead of pulling the prograde one out. 

Also for the scroll wheel, it scales with how quickly you spin it. If you go very slowly, like one click a second, the dV added per 'click' is very small. If you spin it quickly, each 'click' is worth more, and you get a very big change. 

[BentRim]

1 hour ago, FancyMouse said:

That's one of the two reasons why I'm using PreciseNode (provides you numeric input and also changing node in a completely different window independent of where current map view is). With pure stock - unfortunately that's what we have. When I'm in the mood of dragging the vector without the help of the mod, I usually slowly extend the handle until I'm satisfied with the speed, and then I keep cursor steady and wait - it's better to wait for a few seconds than screw up the whole thing and readjust all over again.

@FancyMouse

Thanks for the tip.  I will check out PreciseNode and give it a shot.  I'm not opposed to a modded game.  I'm very new to KSP and was wondering if I was just missing an alternative input system.  

52 minutes ago, FullMetalMachinist said:

When dragging the handles, if you 'push' instead of 'pull' it's a slightly finer adjustment. So if you want to add just a bit of prograde, push the retrograde handle towards the middle instead of pulling the prograde one out. 

Also for the scroll wheel, it scales with how quickly you spin it. If you go very slowly, like one click a second, the dV added per 'click' is very small. If you spin it quickly, each 'click' is worth more, and you get a very big change. 

@FullMetalMachinist

Thank you as well.  I had wondered when setting up a node if 'pushing' retrograde was the same as 'pulling' prograde.  In regards to the scroll wheel scaling...  I think that is my biggest problem and I kind of wonder if it is my mouse, or the game.  When physically rolling my scroll wheel I notice that I get real fine adjustment and then as I approach my intended value all of a sudden it just takes off as though I have scrolled quickly, as though It loses resolution.  My poor mouse is old and has been dropped hundreds of times...  (it's an inexpensive Logitech wireless USB) it does the job for most tasks but I wonder if it's time for a new one.

[Spricigo]

maybe you should take a look at these:

or https://spacedock.info/mod/1087/Maneuver Node Evolved

Both allow editing maneuver nodes by numeric input in a window independent from map view focus. I use the first but looks like they are pretty similar. In stock what you need its a reasonable dose of patience to setup the node well enough.

[pincushionman]

8 hours ago, BentRim said:

 

…When physically rolling my scroll wheel I notice that I get real fine adjustment and then as I approach my intended value all of a sudden it just takes off as though I have scrolled quickly, as though It loses resolution.…

By "intended value" do you mean "a particular exact dV number" or "a particular orbit shape/apoapsis/periapsis value? Because if it's the latter, it isn't your mouse. It's because big dV is worth more than small dV - as the energy of a transfer increases, and the orbit becomes more elliptical, even small changes to the dV applied become more pronounced.

Make a test sandbox, put up a small satellite with loads of dV, put it in a circular orbit, throttle prograde, and watch the orbit change. It'll start off slow, but speed up little by little, but you'll convince yourself it's not changed that much. Then it'll be faster but still OK, but then it'll all of a sudden take off to infinity.

[BentRim]

1 minute ago, pincushionman said:

By "intended value" do you mean "a particular exact dV number" or "a particular orbit shape/apoapsis/periapsis value? Because if it's the latter, it isn't your mouse. It's because big dV is worth more than small dV - as the energy of a transfer increases, and the orbit becomes more elliptical, even small changes to the dV applied become more pronounced.

"intended value" was a poor expression on my part.  I understand what your saying in respect to small dV changes being applied over long distances having a significant effect and I do believe that is part of my issue.  The other is that I have trouble sometimes selecting the proper handle on the node I am trying to edit, depending on the orientation of the view.  For instance a lot of times I am trying to move an node after spending time adjusting prograde when I then try to move the node on the orbit I mistakenly grab a radial handle and then adjust it by accident.  Possibly by not knowing any better, I then delete the node and start over which is time consuming and frustrating.  

There seems to be a fine line for me, but I do understand what your saying and why it could be perfectly normal behavior for the adjustment to take off to infinity quickly.  

I could not find the PreciseNode mod, but found one that appears to be a branch from it called Precise Maneuver.  I have it installed and am learning how to use it.