has anyone tried running routines in 2017r1 with blank moves? ( MOVE/POINT,NORMAL,<,-0.6704,> ) Just had several cmm crashes where these move types seem to be driving to 'zero' instead of 'blank'.
So awhile back I learned this trick of leaving some of the fields blank in a MOVE/POINT, NORMAL.
I immediately did not trust it, even after my coworkers showed me that it worked (this was using 2013 MR1).
My gut feeling was that this trick was probably exploiting a loophole where Wilcox forgot to disallow blank fields like they do
everyotherfield.
And now it looks like they closed that loophole.
Best Practice = do not leave any fields blank.
Number Games you are correct. This is how I learned this Move Point process from the Help section. Hexagon either needs to Fix this issue with the blank Axis in the Move Points and Fix the issue with the Increment Move in offline mode with the virtual Machine. If not then Hexagon needs to remove the Blank Axis Move Point from the Help section.
Number Games you are correct. This is how I learned this Move Point process from the Help section. Hexagon either needs to Fix this issue with the blank Axis in the Move Points and Fix the issue with the Increment Move in offline mode with the virtual Machine. If not then Hexagon needs to remove the Blank Axis Move Point from the Help section.
