-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
AttributeError: 'DXCamera' object has no attribute 'is_capturing' #74
Comments
hey 0xDEITY, Per the exception: When creating the instance keep it simple unless you need to, like setting 2 gpu or 2 monitors. In my case, I noticed NOT setting the "device" or "output" helps, and only to define the "region", as code below Running this code works if you run it for one or multiple instances in the same scope. I'm using version 0.0.5 and I'm having the same "is_capturing" issue but with different details related to "available resources", details: The way I'm able to reproduce this issue is when using multiple instances in different parallel scopes/threads such as SubProcVecEnv, each instance needs a dxcam on a specific region, so on the 3rd or 4th instance created the 'is_capturing' error is thrown, probably by its duplicator nature and resource handling. My workaround was to provide specific resource time when creating a dxcam instance to avoid all instances creating the cam simultaneously aka "Delayed Start", and at the end releasing properly the instance with ".release" or "del". |
I have 2 graphic cards in my computer. I have the same issue with you too. P.S. Graphics settings -> find python.exe -> Graphic preference -> Power saving |
So I had working code yesterday. I didn't change a thing. Now suddenly dxcam is throwing this error:
I don't understand why this is happening. I don't think it is an issue with my code.
The text was updated successfully, but these errors were encountered: