# vtk.vtkTransform.GetOrientation giving wrong results for large scale differences

**URL:** https://discourse.vtk.org/t/vtk-vtktransform-getorientation-giving-wrong-results-for-large-scale-differences/10224
**Category:** Development
**Created:** [December 16, 2022, 3:43pm UTC](https://discourse.vtk.org/t/vtk-vtktransform-getorientation-giving-wrong-results-for-large-scale-differences/10224 "2022-12-16T15:43:27Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![rdbrn](https://discourse.vtk.org/user_avatar/discourse.vtk.org/rdbrn/32/5627_2.png) [@rdbrn](https://discourse.vtk.org/u/rdbrn)
#### Post date: [December 19, 2022, 12:26pm UTC](https://discourse.vtk.org/t/vtk-vtktransform-getorientation-giving-wrong-results-for-large-scale-differences/10224/5 "2022-12-19T12:26:09Z")

</div>

@dgobbi , thanks for looking into the code. Changing the epsilon to 1e-12 would be more than sufficient for my purpose. The epsilon of 1e-3 is already on the edge of occuring cases.

@lassoan , about the UserMatrix, I’ve been trying to avoid UserTransforms due to [Are UserTransforms going to be deprecated?](https://discourse.vtk.org/t/are-usertransforms-going-to-be-deprecated/9165).

For me the ultimate solution would be to set the Matrix of the actors transform directly. Would a PR for that be appreciated or is there a reason to disallow setting it directly?

---

_[View the full topic](https://discourse.vtk.org/t/vtk-vtktransform-getorientation-giving-wrong-results-for-large-scale-differences/10224)._