Open kezzyhko opened 2 months ago
Hello!
Thanks for the top quality bug report! I implemented this feature originally with normalized heightmaps in mind (always ranging from 0 to 1) which is why I first missed this issue. I am aware of this bug, and I think this commit fixes it (and adds inspector tools to add terrain automatically): https://github.com/Balint-H/mujoco/tree/feature/unity-hfield-context
There's an open PR for it that has not yet been merged.
However I've mainly tested it in my own use cases and I'd really appreciate if you could give it a go as well (the commit is for MuJoCo 3.1.4). If it still doesn't work for you I'll go through the scenes you shared and send in a fix ASAP.
If it does work I'll ask for someone at DM to merge in the PR.
I'm glad others are using the plugin as well, so let me know if you have other questions.
@Balint-H
Yep, I have seen your PR, but for some reason I didn't think it would fix that bug. Anyway, I have tested my usecase with MuJoCo 3.1.4 + plugin at https://github.com/Balint-H/mujoco.git?path=unity#feature/unity-hfield-context
, and it works perfectly. Now waiting for the PR merge :) Thanks for your help and for your contributions!
Description
Video with the problem is attached below
When using a terrain (hfield geom) in Unity, physics collisions may not match the rendered visuals. This happens in case when terrain data contains heights in smaller range than [0..1]. For example, if terrain is a flat plane at height 0.7, mujoco will think that highest point is at height 1, and collision will happen at height 0.7 * 0.7 = 0.49. But as soon as we add one point at height 1, everything starts working correctly.
Steps to reproduce
Video
https://github.com/user-attachments/assets/e3e6b9f9-d32d-403b-b1a3-ddc5871701d5
Versions
It probably does not depend on particular versions, but I'm gonna include them anyway
OS: Windows 10 MuJoCo: 3.2.0 Unity Editor: 2022.3.28f1