Hi I just updated to the New Version of Ragdoll to test the new Locomotion feature. However Im experiencing a bug where the character just snaps at one end of the grid and does not calculate a path.
Any thoughts on how I can fix this? Im using Mac Version.
Unclear; any messages in the Script Editor? If you launch Maya from a terminal, it may output some additional messages there.
Hi Marcus
This is what I get.
from ragdoll import interactive as ri
ri.assign_plan()
isolateSelect -update āmodelPanel4ā;
isolateSelect -update āmodelPanel4ā;
isolateSelect -addSelectedObjects modelPanel4;
// Warning: Locomotion failed with āSolved To Acceptable Levelā
//
ragdoll._on_plan_complete() - Plan Complete
Maybe it has something to do with some permissions from admin?
Hm, thatās a clue. Can you try following these steps exactly, and let me know what you see?
If it still doesnāt work, can you check the Node Editor to make sure this is what it looks like?
And then check the Attribute Editor under Targets to confirm that this is what it looks like?
Finally, can you open this scene and let me know if this works?
boxtest.zip (45.5 KB)
Hi Marcus,
Thanks for the thoroughness. I opened the file you had and it prompted my machine to enable loco3D. And after that it works.
Now Im having an issue whenever I enable locomotion in the scene and I open a new scene it creates an error
Not quite sure how I can find the other details since it doesnt record in the Script Editor.
Any thoughts? Thank you.
Great, so the original issue seems to have been MacOS blocking access to the loco3d file on disk; itāll require permissions similar to the ragdoll.bundle and Turbo* (licencing) files.
The next issue of a crash on a new scene is something I am unable to reproduce here. Are you able to test this on a different machine, or with another version of Maya or any other circumstance that could provide more clues? Also, if you are able to launch Maya from a terminal, that terminal may provide some additional clues post-crash.
i had the same issue ā Warning: Disabling due to missing targets.
setting this plugin (cmdx_ragdoll.py) to load solve it for me
sharing in case someone run into the same issue as me. i just started the trial today haha.
Thanks for sharing @lpchow, and welcome to the forums! 
This seems like a clue, we will investigate!
Running into a similar issue, and cmdx_ragdoll and cmdx_locomotion are enabled in Plug-Ins.
When I open the box test .ma file I can see the plug-in shapes, they snap between two positions when I scrub the timeline. But on the file open it gives this error:
// Warning: Locomotion failed with āSolved To Acceptable Levelā
If I delete that plan, select the box then the spheres, Assign Plan, I get this error:
// Warning: Disabling due to missing targets.
// Warning: Disabling due to missing targets.
I can see an rPlan in the Outliner, but I donāt see any plug-in shapes.
Any helps much appreciated, thanks!
Hello, which version of Ragdoll are you on? And what OS?
If you try these steps, what happens?
Followed by this:
If you unload, and reload cmdx_ragdoll, leaving cmdx_locomotion unloaded, what happens?
Thanks, Yea tried all of the above before posting, except the leaving locomotion unloaded, that gives same results though. Iām on linux on a floating license.
Ok, Iāll assume you are on Ragdoll 2024.07.01.
Next, letās check your install. Itās possible thereās a file missing or unable to run.
import os
PATH = os.environ["PATH"]
PATH = PATH.split(os.path.pathsep)
PATH = list(reversed(PATH)) # Look from latest to earliest
ext = {
"nt": ".exe",
}.get(os.name, "")
fname = "loco3d" + ext
exists = False
for path in PATH:
loco3d = os.path.join(path, fname)
loco3d = os.path.abspath(loco3d)
if os.path.exists(loco3d):
exists = True
break
assert exists, "loco3d could not be found on:\n %s" % "\n".join(PATH)
if exists:
print("-> Success! loco3d found @ %s" % loco3d)
Run this in your Script Editor, and make sure it says āSuccess!ā once complete. If not, itāll give you a series of paths to look into, one of them should point to maya/modules/Locomotion-2024_05_07/shared/linux, and in there you should find a file called loco3d. Also check the size of it, it should be around 10 mb.
Thanks for the quick reply, sorry yes thatās the right version, investigating now since I donāt think I can immediately see shared files since Iām on a floating license server situation, but will report back.
Hey there. We can ensure that the executable (LOCOMOTION_EXECUTABLE) is being found in PATH in this case. Nonetheless could you please guide us where in the python source code to look for the application of that executable? We are having trouble to find any hints of it inside of the assign_plan method in commands.py
Hm, challenging. Itās possible Ragdoll and Locomotion are installed with incompatible version numbers. Can you confirm that your Ragdoll version is 2024.07.01 and Locomotion is 2024.05.07? These are the ones found together on the Download page here (at the time of this writing).
You can confirm the versions by looking at the LOCOMOTION_EXECUTABLE path, it would include the version number. Ragdoll would reside next to it, as itās another module.
There isnāt much in the form of checking compatibility between these, as they used to be bundled together. But my theory is that a prior bundled install was made, followed by a new install of Ragdoll-only. If so, installing the latest Locomotion via that download page should solve it.
Python isnāt involved in the handling of this executable unfortunately, that executable is the computational source of locomotion and is managed inside the compiled plug-in.
Hey there. Versions are matching and this is the first time we are using this plugin pipeline-wide. We are currently using this with Maya 2023 on CentOS 7. Could the conflict be originating from there?
Thank you, I can reproduce this here under those circumstances. Investigating now.
Sorry for the delay, weāve identified the cause and patched it up, available as a new download here. You do not need to update Ragdoll for this, only Locomotion.
On Linux and Mac, youāll also need to set the executable bit for the loco3d file in the installation/modules directory.
cd ~/maya/modules/Locomotion-2024_11_14/shared/unix
chmod +x ./loco3d
Let me know how it goes!
Hey! Thanks for the update! We deployed it but sadly we are running into the same error. Are there more specifics about our environment that we can provide that might help in addressing this?