LWSN and Remote Desktop

[3dreamstudios]

We use LWSN to network render on our computer. It helps us manage scenes and priorities on the fly. We remote desktop into the controller machine and occasionally onto the render machine for maintenance.

It seems once we remote desktop into the render machine LWSN no longer can see GPU's when it's launched and therefore cannot render anything. This is a big issue for us as if there is ever a problem and we need to reset the machine, remote login for any reason the renders are shot for the entire night.

Not sure if this is a limitation of the plugin and the CHECK it's doing or somehow Remote Desktop and the signing in of that.

Any thoughts?

[3dreamstudios]

Found this on another forum completely different forum unrelated to GPU rendering but rather another GPU computational program... Seems I may need to look at VNC.

---------------------------------------------------------------
When you use RDP, Windows will switch off the driver that you installed and use its own built-in driver for RDP. This driver does not know anything about weird things like CUDA, CAL, OpenCL or whatever. This driver cannot be updated.

And as such your only option is to not use RDP, but a third party program, such as VNC which uses the user-installed driver and doesn't interrupt the crunching.

[juanjgon]

As far I know VNC and Teamviewer don't have problems with the GPU rendering.

-Juanjo

[3dreamstudios]

As far I know VNC and Teamviewer don't have problems with the GPU rendering.

-Juanjo

I will test off site this evening but I think VNC will work just fine. It's the Windows RDP that apparently disables the drivers and then doesn't re-enable them or something when it's disconnected.

This isn't something you could fix either way I don't believe...with my further research! Just something for others to know possibly if they run into it.