Skip to content

[Bug] MjPDController attached to G1 articulation but robot remains fully unresponsive #76

Description

@mulegan

Summary

MjPDController attached to G1 articulation but robot remains fully unresponsive

Environment

  • Unreal Engine version:5.7release
  • OS (Windows / Linux) and version:Windows10 22H2
  • URLab plugin version / commit SHA:567cbd907a570b820beb87fbddd69c356a6d86da
  • Visual Studio version (Windows only):Visual Studio 2022
  • MJCF Path :RoboJuDo/assets/robots/g1/g1_29dof_rev_1_0.xml

Reproduction steps

  1. Added AAMjManagerActor to the level, enabled Bridge Server, and configured Control Subscribe Endpointto tcp://0.0.0.0:5556
  2. Imported the G1 MJCF to generate the blueprint, manually added the MjPDControllercomponent in the Blueprint's Components panel, and ensured Enabledand Auto Activateare checked
  3. Spawned the G1 instance in the level, confirmed its Articulation Prefixexactly matches the target in the policy: g1_29dof_rev_1_0_C_1
  4. Launched PIE, opened the Simulate Widget, and clicked Play (or pressed P) to trigger control logic

Expected behaviour

  1. After clicking Play in the Simulate Widget, the widget enters running state, and actuator sliders update dynamically in sync with policy output.
  2. G1 responds to policy control and executes corresponding motions..

Actual behaviour

  1. Simulate Widget is unresponsive: After clicking Play, the widget remains in Pausedstate. All 29 actuator sliders stay static with no value updates.
  2. Persistent collision scale warnings: UE outputs repeated LogPhysics: Warning: Scale3D is (nearly) zeroerrors. Even after manually setting all Geom_Sphere*collision components' Transform Scale to (1,1,1)in the editor, saving the blueprint, and relaunching PIE, the warning persists.
  3. Auto-activation has no effect: Confirmed Enabledand Auto Activateare checked for the PDController. Restarting PIE does not change the behavior.
Image

Relevant logs

Before submitting

  • I searched existing issues and didn't find a duplicate.
  • I'm on a supported Unreal Engine version (5.7 or newer), or I've noted why not in the environment block.
  • I reproduced this on the latest main (or noted the commit I'm on).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions