Hello,
I am trying to export into bvh a file that contains a trained marker set with relative bones and bones chains. After solving the asset, I tried to export it into a format containing the skeleton information. I could export into fbx, but not into bvh format. I am not sure what the problem might be: the pop-up window for the bhv export gets displayed and stays on the screen for very little time; no file is exported. I get no errors. Has anyone already experienced a similar problem ? Maybe I am doing something wrong when defining the bones relationships. How could I get more information on the error (if any)? I tried already to have a look at the error log interface, but it is empty
Thank you
Valeria
problem when exporting trained marker set to bvh
Re: problem when exporting trained marker set to bvh
Hi Valeria,
This issue you’re facing — the BVH export pop-up flashing quickly and no file being saved, with no error messages — is indeed frustrating and not uncommon in workflows involving marker-based skeleton solving.
This issue you’re facing — the BVH export pop-up flashing quickly and no file being saved, with no error messages — is indeed frustrating and not uncommon in workflows involving marker-based skeleton solving.
-
- Posts: 1
- Joined: Wed Jun 11, 2025 10:00 pm
- Contact:
Re: problem when exporting trained marker set to bvh
Hi Valeria,
yes, I've seen similar issues before—BVH export can silently fail if the skeleton isn’t fully hierarchical or properly mapped. Double-check that all bones are correctly parented and that there's a single root. Also, try exporting from a simplified version of your rig to isolate the issue.
For more details, enable verbose logging (if available) or check if there’s a console output during export. Sometimes, re-validating the skeleton structure helps too.
Good luck!
yes, I've seen similar issues before—BVH export can silently fail if the skeleton isn’t fully hierarchical or properly mapped. Double-check that all bones are correctly parented and that there's a single root. Also, try exporting from a simplified version of your rig to isolate the issue.
For more details, enable verbose logging (if available) or check if there’s a console output during export. Sometimes, re-validating the skeleton structure helps too.
Good luck!