Saran Tunyasuvunakool

We've had mixed success with auto-generated type stubs for internal usage. The `.pyi` stubs were generated using [mypy](https://github.com/python/mypy), but the tool gets confused in a few places and we have...

Technically we currently _don't_ support type checkers, so it would be inappropriate to include a `py.typed`. If we do add `.pyi` files with our future releases we'll make sure that...

We've changed the GL linkage on `simulate` in our 2.1.1 release. Could you please try again with the new version and let us know if the issue persists? (Also, make...

You can actually already do this without needing to touch MuJoCo's source code at all. If your goal is to provide your own actuation model (e.g. by training a neural...

If it's OK I'm going to hold off on merging this PR for a bit since we're currently investigating CMake.

Hi! Could you please give us the native stack trace at the point where you hit a segfault?

Can you go up further than that? Looks like there's more error message there. (Also, if it's possible to copy the text and paste it here rather than a screenshot...

Coming back to this now in the context of MuJoCo 2.1.1 release, I'm now fairly certain that neither MuJoCo nor dm_control make Ubuntu-specific assumptions. The 2.1.1 MuJoCo build for x86_64...

Since the original post is from last week, I presume you're still working with `mujoco` version 2.1.3? If that's the case could you please try upgrading to 2.1.4 to see...

Would you be able to tell us exactly which parts you are finding particularly problematic? This would help me target my documentation effort to the most useful place. (Sorry for...