Heightmaps setPose (and friends) give wrong behaviour

Hi, thanks for the great physics engine. I found this issue while working with heightmaps created using data from a std::vector. Below I've attached some extra information.

Issue: Heightmaps collision detection "stops" working when we set the position of the heightmap using either setPosition or setPose.
OS: Ubuntu 18.04.3 LTS
RaisimLib-version: master branch (HEAD @ dfc3d63c82d75905c3caad353d799c17899fa365)
To reproduce: see example heightmapFromCpp in this branch.
Behaviour: See gifs below. When it fails, there seems to be a collider below the actual graphical object (look at the capsule in the middle as it bounces on something invisible).

Using hm->setPosition (collision fails)

gif_issue_heightmaps_pose_1

Using centerX, centerY

gif_issue_heightmaps_pose_2

This happens with both the constructor from std::vector data, and the one using TerrainProperties.

Note: A workaround I'm using is to set both centerX and centerY with the x-y position required, and offset all my heights by the z-position I wanted the heightmap to be. So far it works ok, but if using TerrainProperties, there's no offset parameter exposed (as in the fromPng constructor), so in that case I can't place the heightmap exactly where I need it.

leggedrobotics / raisimLib

Heightmaps setPose (and friends) give wrong behaviour #33