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
- Added AAMjManagerActor to the level, enabled Bridge Server, and configured Control Subscribe Endpointto tcp://0.0.0.0:5556
- Imported the G1 MJCF to generate the blueprint, manually added the MjPDControllercomponent in the Blueprint's Components panel, and ensured Enabledand Auto Activateare checked
- Spawned the G1 instance in the level, confirmed its Articulation Prefixexactly matches the target in the policy: g1_29dof_rev_1_0_C_1
- Launched PIE, opened the Simulate Widget, and clicked Play (or pressed P) to trigger control logic
Expected behaviour
- After clicking Play in the Simulate Widget, the widget enters running state, and actuator sliders update dynamically in sync with policy output.
- G1 responds to policy control and executes corresponding motions..
Actual behaviour
- Simulate Widget is unresponsive: After clicking Play, the widget remains in Pausedstate. All 29 actuator sliders stay static with no value updates.
- 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.
- Auto-activation has no effect: Confirmed Enabledand Auto Activateare checked for the PDController. Restarting PIE does not change the behavior.

Relevant logs
Before submitting
Summary
MjPDController attached to G1 articulation but robot remains fully unresponsive
Environment
Reproduction steps
Expected behaviour
Actual behaviour
Relevant logs
Before submitting
main(or noted the commit I'm on).