Disclaimer: Until now (June 2nd 2014), I only tested it with a connection to a single remote Rendernode, located 120km away – both PCs running Windows 7 64 bit. Further tests with Windows / Mac OSx combinations will probably follow. Also, you need to consider and decide for yourself if your scene/texture size and your internet connection makes sense for a remote Team Render scenario. I tested it with a DSL 6000 connection (~5000 kbit/s downspeed and ~150 kbit/s upspeed on the weaker connection side). With a small test-scene and without any large textures, I experienced huge speed improvements even on a single rendered frame.
- Establish a Teamviewer VPN Connection from your Renderhost to your Client (or vice versa, it doesn’t really matter). Teamviewer is availiable for free for non-commercial use at http://www.teamviewer.com/ – I recommend setting up a personal user account. That way, you can install the handy “Teamviewer Host” edition on every Rendernode and make them accessible in your own Teamviewer client list, where you can see which Node is currently online. The host edition will start automatically when you boot a rendernode. Continue reading