-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when trying to automate detection and transfer #159
Comments
I guess the issue is that bpy.ops.wm.cgt_feature_detection_operator is bound to blenders window manager (mainly to show realtime updates) and while running blender headless this results in an error. BlendArMocap/src/cgt_mediapipe/cgt_mp_detection_operator.py If you have an issue with the opencv image display (idk if that's an issue in the docker as there is no window manager), you'll find a So either overwrite in the add-ons operator directly or create an own operator :) Quick outline:
|
I just found the time to adapt the operator and it works like a charm. Haven't build a Docker container out of it yet but I can fully run the end-2-end process from the terminal now. Thank you so much! Is that something you would be interested in having as well? |
You are welcome, glad it works! |
@NikKaem It will be great if you would sare your solution. Thank you! |
I'm currently trying to build a script that automates the whole end-2-end process with BlendARMocap
Minimal Code looks like this:
This works if I execute the terminal command
blender -P Script.py
. However, as soon as I try to keep blender in the background withblender -b -P Script.py
the detection part fails with the errorRuntimeError: expected class WM_OT_cgt_feature_detection_operator, function cancel to return None, not set
. I initially thought it was a problem with opening the detection window but even if I disable the drawing of the window the error persists. My ultimate goal is to run it all in a docker container which would be difficult if I need to show a frontend for it to work. Is there any workaround for that?The text was updated successfully, but these errors were encountered: