-
Notifications
You must be signed in to change notification settings - Fork 821
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
[Blender] unable to start process, #2764
Comments
Is #1006 #486. You can follow the instructions here and see how blender fares. If you run into display issues after getting over the PulseAudio blocker, try running Blender remotely from a Real Linux VM using llvmpipe (as opposed to Intel/NVIDIA/AMD DRM drivers) to VcXsrv on Windows first, so you have a baseline. Also include your use-case for running blender on WSL as opposed to Windows will help. Bonne chance. |
Amusingly, blender does work (for some value of working). No one would do that, mind. But does paint. This is on 17063, but I'm pretty sure FCU 16299 would be okay too. OpenGL stuff has been okay since someone tried OpenRTC2 back in October 2016. |
since it was just for debugging purposes when a linux machine was not available, I will not proceed with your suggestion. Honestly I don't want to install the full ubuntu desktop on WSL just for this task. |
seems related to #1006
The text was updated successfully, but these errors were encountered: