Skip to content
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

BELLMAN_NO_GPU=0 makes problems #249

Closed
emf-developer opened this issue Jan 10, 2022 · 0 comments · Fixed by #306
Closed

BELLMAN_NO_GPU=0 makes problems #249

emf-developer opened this issue Jan 10, 2022 · 0 comments · Fixed by #306

Comments

@emf-developer
Copy link

If BELLMAN_NO_GPU=0 is set, only PC2 uses GPU and C2 and WindowPoST uses CPU instead.
You must remove BELLMAN_NO_GPU ENV to be able to use GPU for C2/WindowPoST.
tested using RTX 3090 GPU.

vmx added a commit that referenced this issue Apr 12, 2023
Prior to this change, the GPU was disabled, when the `BELLMAN_NO_GPU`
environment variable was set to any value, even when set to 0.

Fixes #249.
vmx added a commit that referenced this issue Apr 12, 2023
Prior to this change, the GPU was disabled, when the `BELLMAN_NO_GPU`
environment variable was set to any value, even when set to 0.

Fixes #249.
vmx added a commit that referenced this issue Apr 14, 2023
Prior to this change, the GPU was disabled, when the `BELLMAN_NO_GPU`
environment variable was set to any value, even when set to 0.

Fixes #249.
vmx added a commit that referenced this issue Apr 14, 2023
Prior to this change, the GPU was disabled, when the `BELLMAN_NO_GPU`
environment variable was set to any value, even when set to 0.

Fixes #249.
@vmx vmx closed this as completed in #306 Apr 14, 2023
vmx added a commit that referenced this issue Apr 14, 2023
Prior to this change, the GPU was disabled, when the `BELLMAN_NO_GPU`
environment variable was set to any value, even when set to 0.

Fixes #249.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant