PositionInterface, OrientationInterface, and PoseInterface need optional transform update behavior

[JeroMiya]

RequiresPositionInterface, RequiresOrientationInterface, and RequiresPoseInterface are convenient base classes for a behavior that requires one of those interface components in its own logic. However, those behaviors currently always update their parent game object's transform (position or rotation or both). This should be optional in case the dependent behavior wants to take over the transform modification. A true/false property that can be set in the editor (like the path), which disables the code that updates the parent object's position and orientation.

We may also want to expose something to RequiresFooInterface subclasses to enable/disable the update behavior programmatically instead of relying on the editor flag to be set a certain way.

[DuFF14]

Not sure what you mean. Do any of the prefabs have this behavior? Maybe you can provide an example where an interface is updating its parent game object?

Also, I didn't catch this earlier, but I think now that we're using state APIs in these interfaces, transform updates should be happening in LateUpdate rather than Update, as this is closer to the time when the image will be displayed on the screen.

[JeroMiya]

I meant the transform updates in their respective Update methods.

[JeroMiya]

@DuFF14 Do you have any hardware to measure actual tracking lag? I was testing using LateUpdate as you suggested to see if it improved the visual lag, and it seemed to, but I can't really tell. My Razor Hydras have very little lag, but I'm experiencing some pretty bad lag on the HDK 1.0. I always have though, so it may just be the hardware or something in my setup.

[peroht]

@JeroMiya are you experiencing the smoothening effect of the 1 euro filter as a tracking lag?