Asset3D supports transform argument, but Mesh3D does not

[roym899]

Minor issue since it can easily be worked around by manually transforming or logging a separate transform.

To be honest, not sure why Asset3D supports it. However, I think it is nice to have for simplicity.

Maybe worth considering whether other archetypes like Points3D should also support this argument.

[teh-cmc]

To be honest, not sure why Asset3D supports it.

Because they are different things: the transform you log independently is an in-tree transform while the one attached to Asset3D is an out-of-tree transform... which is a concept that we've talked about a lot and never fully agreed on whether nor how to generalize it, which is why it only exists in a couple places at the moment and so it gets very confusing... 😞

See:

• Standardize and generalize out-of-tree transforms #2197
• Asset3D:
  

  rerun/crates/re_types/definitions/rerun/archetypes/asset3d.fbs

  Lines 39 to 42 in 756793e

  	/// An out-of-tree transform.
  	///
  	/// Applies a transformation to the asset itself without impacting its children.
  	transform: rerun.components.OutOfTreeTransform3D ("attr.rerun.component_optional", nullable, order: 3000);

• OutOfTreeTransform3D:
  

  rerun/crates/re_types/definitions/rerun/components/out_of_tree_transform3d.fbs

  Lines 9 to 17 in 756793e

  	/// An out-of-tree affine transform between two 3D spaces, represented in a given direction.
  	///
  	/// "Out-of-tree" means that the transform only affects its own entity: children don't inherit from it.
  	table OutOfTreeTransform3D (
  	"attr.rust.derive": "PartialEq"
  	) {
  	/// Representation of the transform.
  	repr: rerun.datatypes.Transform3D (order: 100);
  	}