I want to render my blender project in rdp. But some error has appeared. What is the best solution for this problem? I've spent many hours trying to troubleshoot this problem.
-
$\begingroup$ I remember that there were some issues with Remote Desktop accessing OpenGL... try coneccting using VNC. $\endgroup$– user1853Apr 8, 2016 at 3:57
-
$\begingroup$ GarageFarm.NET had the correct answer. By adding the appropriate DLL to my Blender directory (running on a Windows Azure virtual machine) I was able to get it (v2.78c) to run without a problem. Obviously this isn't going to be speedy by any stretch, but when you're just trying to render a few cubes, it's more than sufficient. $\endgroup$– Javin BondJul 13, 2017 at 12:06
4 Answers
To run Blender on a machine without OpenGl support, you would need to:
Download the opengl32.dll or opengl64.dll from this link: http://download.blender.org/ftp/sergey/softwaregl/
Copy and paste the dll next to your blender.exe (the directory would typically be: C:\Program Files\Blender Foundation\Blender)
Run Blender
This enables Blender to open with software opengl legacy mode.
-
$\begingroup$ How does this not have more upvotes... $\endgroup$ Aug 2, 2017 at 14:14
-
1$\begingroup$ What is weird about this is that it seems to only be a problem when you start Blender from inside of a Remote Desktop Session. If you start Blender before you start the Remote Desktop Session and then connect the RDS, it actually seems to work just fine. So my question is, if it seems to work just fine when connecting RDS to an existing instance, why even have this detection and limitation at startup? $\endgroup$– swoobyOct 10, 2017 at 20:05
-
$\begingroup$ I've noticed the same behaviour as swooby did. $\endgroup$ Jul 13, 2018 at 18:44
-
$\begingroup$ Also, after this, your GUI is going to become super slow, since it will use OpenGL to render the GUI. $\endgroup$– AnugaSep 13, 2018 at 8:21
-
$\begingroup$ Unfortunately did not work for me. RDP & RTX 2080 Ti on March 10 2020 drivers w/ 64-bit opengl32.dll in Blender 2.8 directory $\endgroup$– JonathanMar 17, 2020 at 0:09
Sad but simple problem. You and I are in the same boat. Our computers' graphics cards do not support opengl 2.1. (you seem to be using Vmware, so check if your host computer has opengl 2.1 support.)
Anyway 2.77 simply will not run if you do not have opengl 2.1, period. (In most cases it is not worth looking in to updating your drivers, either your hardware supports it or it doesn't.)
The solution (and what I have to do for one machine) is to use blender 2.76. That version not only does not have the opengl 2.1 requirement, but overall will run on "older" systems.
-
$\begingroup$ i've tried install blender 2.76b. It said 3d hardware acceleration not found. But i can open blender. thank you for the solution. $\endgroup$– DevzApr 9, 2016 at 4:46
I got the same problem with RDP to execute 2.77.
But, it works well with TeamViewer.
https://www.teamviewer.com/
-
$\begingroup$ Be aware Teamviewer requires purchasing a commercial license for commercial work, but is free for personal use. Alternatives are VNC, Steam Remote Play, Shadow, and more alternativeto.net/software/teamviewer $\endgroup$– JonathanMar 17, 2020 at 0:05
You can use tscon to disconnect current remote session and launch blender outside remote session.
This is described here: https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html
only problem is you have to reconnect remote session after blender is started.
after disconnection of remote session the terminal stays unlocked so the line
Rundll32.exe user32.dll, LockWorkStation locks the workstation after disconnection
last line starts blender
Put the following lines in a batch file and launch on remote machine as administrator
my start batch:
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (
%windir%\System32\tscon.exe %%s /dest:console
)
Rundll32.exe user32.dll, LockWorkStation
"C:\Program Files\Blender Foundation\Blender\blender.exe"