Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
5.12, 5.15
-
None
-
All
Description
According to Qt3D documentation:
https://doc.qt.io/qt-5/qt3dcore-qtransform.html#matrix-prop
It is known that:
When the matrix property is set, it is decomposed to translation, rotation and scale components.
This decomposition causes troubles like the one described here:
https://stackoverflow.com/q/60995155/3405291
The decomposing operation strips out what is effectively a shear phenomenon.
Possible suggestions:
- Giving the `Qt3DCore::QTransform` API an option to store transform matrix as a whole rather than decomposing it into its components
- Giving the `Qt3DCore::QEntity` API an option to avoid applying parent transformation into the children