Anyone else have issues with "Move Increment" command?

I don't know about your issue, but I long ago stopped 'using' increment moves.  I will program with them, need to move x amount in Y to get clear, so I use it, then when it moves that amount, I do CTRL-M to get a move/point and remove the incremental move.  I do this because IF you get an air-trigger during an incremental move, and you tell it to continue, it will move the FULL amount on the incremental move from it's current position, not from where it started the incremental move.  That can be bad, m'kay?

I don't know about your issue, but I long ago stopped 'using' increment moves.  I will program with them, need to move x amount in Y to get clear, so I use it, then when it moves that amount, I do CTRL-M to get a move/point and remove the incremental move.  I do this because IF you get an air-trigger during an incremental move, and you tell it to continue, it will move the FULL amount on the incremental move from it's current position, not from where it started the incremental move.  That can be bad, m'kay?

I think I'll adopt your method going forward.  No air triggers, no telling it to continue, but I just dog-legged Tip2 on a star probe because the machine decided to combine two separate lines of code into a single move!!

the other reason for changing to point over increment is I work in sheet metal, and when first hit part (as in, new tool, never before made parts) if the part is bad enough (and often they are) moving incrementally from where the probe ends after a touch could have crash potential.  Say the part is under-bent by 10mm (it happens) so you have to increase the prehit/retract to be able to measure the point (instead of 3), then there is an extra 7mm of retract before it starts the incremental move.