# Child in physics compound body not rotated properly under Ammo.js and Oimo

**URL:** <https://forum.babylonjs.com/t/child-in-physics-compound-body-not-rotated-properly-under-ammo-js-and-oimo/13291>\
**Category:** Bugs\
**Created:** [August 11, 2020, 1:46pm UTC](https://forum.babylonjs.com/t/child-in-physics-compound-body-not-rotated-properly-under-ammo-js-and-oimo/13291 "2020-08-11T13:46:06Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\
**Post date:** [August 14, 2020, 8:18am UTC](https://forum.babylonjs.com/t/child-in-physics-compound-body-not-rotated-properly-under-ammo-js-and-oimo/13291/8 "2020-08-14T08:18:39Z")

</div>

> [@gbz](#):
>
> 1. You must set and use rotationQuaternion when creating physics objects because physics engines rely only on them.

This is there to explain that the physics engines convert your rotation to quaternions so don’t use .rotation after setting a physics impostor. I do agree however that you can understand this sentence a bit differently 🙂

This is certainly a bug, and it seems like the extent size change is the way to go. There was a reason why we decided to use extendSizeWorld, so I will have to see when what should be used. The logic is clear thou 😉

Want to report an issue on github so we can follow this? Link this thread as well when filing it.

---

_[View the full topic](https://forum.babylonjs.com/t/child-in-physics-compound-body-not-rotated-properly-under-ammo-js-and-oimo/13291)._
