DPKit Motion Info node showing no outputs

[ASCIISkull]

Attempting to use the Motion Info node, I am getting no output. Input spy reads no values from any of Motion Info's outputs except speed(which is a constant -1.#nd). I tried multiple setups, with the object it was applied to parented to the 'driving' null, unparented, etc.

Also, when I choose 'Use Parent' and close the node, when I reopen it I cannot unselect 'Use Parent' or choose anything from the dropdown('control is disabled'). If I select an item from the list and close it, reopening it doesn't allow me to choose 'use parent'.

Is there something I missed?

This is on Win32.

[dpont]

Motion Info input has more than one output,
the main and (almost) always giving a value
is the "Distance", other like "Position" are
not exactly what you get with the Item Info
node, it needs an input like "Covered Distance".
I can't figure what do you want to achieve
and what are your exact settings and context
or content to reply with more precision.

Denis.

[ASCIISkull]

Currently, I have an object which is the child of a moving null. Adding the node to the object and choosing the parent as the source for the node, I then plugged each output on the node into input spy and, except for speed giving -1.#nd, all the outputs of the node gave a value of zero or 0.0,0.0,0.0.

[dpont]

I still don't understand what is your context (node editor),
content (animation of the reference) and what kind of effect
you are trying to do.
Motion Info node has some common utility,
I haven't Spy here but I currently use basic
settings here without problems.

Denis.

[ASCIISkull]

The node editor I used was the displacement for the child object.
The parent(reference) is just moving via keyframe.

I'm not trying for any particular effect yet, but I was hoping to eventually use the node to drive an MDD displacement. However, plugging the speed output(with the -1.#nd output) into mdd pointer crashes layout.

[dpont]

Yes, I use it in the Item Motion NE,
but still can't reproduce these issues,
sorry but your description doesn't help
me to investigate and Spy is not the
a way for me to debug.
May be not the appropriate node tool
for your expectation.

Denis

[dpont]

Ok, I got it,
the last additions in Motion Info node
(speed, velocity..)
broke the update of time and I got
also some specific issues with the
speed calculation.
May be a fix/update later.

Denis.

[dpont]

I fixed several things in Motion Info node,
could solve undefined output in "Speed",
the win32 version of DPKit has been updated.

Denis.

[ASCIISkull]

Awesome, thanks!