New Blender and Render Farms

46 views
Skip to first unread message

Rod Kennedy

unread,
Apr 5, 2016, 3:47:04 PM4/5/16
to Blendertarium
There has been a rumor floating about our staff that seems to indicate that the latest version of Blender won't support rendering on a render farm. This seems completely counterintuitive and counter productive.  Has anyone else encountered this issue? Is it an actual issue or is it a technical problem local to us?  If it is a real problem is there a work around?

We've been doing some good stuff with our render farm and hope that this is just a minor operator error.

Rod Kennedy
Casper Planetarium

Scott Sumner

unread,
Apr 6, 2016, 5:09:21 PM4/6/16
to blende...@googlegroups.com
Usually for batch rendering I write a shell or Python script to handle it.  As long as the command line implementation of rendering is available that shouldn't be affected.  Sometimes I also use the "frame skip" option that Ron introduced me to.  I'm working on a rendering manager that would allow jobs to be distributed to desktops purely on an "as available" basis.  Once I get that working I'll post about it here.

Scott


--
You received this message because you are subscribed to the Google Groups "Blendertarium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blendertariu...@googlegroups.com.
Visit this group at https://groups.google.com/group/blendertarium.
To view this discussion on the web visit https://groups.google.com/d/msgid/blendertarium/a1c08d10-ef75-4c0b-b0f0-6de8641ff606%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Rod Kennedy

unread,
Apr 6, 2016, 6:26:38 PM4/6/16
to blende...@googlegroups.com
actually we did some digging and turns out it is an issue with Open GL....the new blender doesn't support the older version of Open GL on the machines...it may be something for our IT people. 

--
You received this message because you are subscribed to a topic in the Google Groups "Blendertarium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blendertarium/I1pNLjY2yP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to blendertariu...@googlegroups.com.

Visit this group at https://groups.google.com/group/blendertarium.
To view this discussion on the web visit https://groups.google.com/d/msgid/blendertarium/CAMkqAVrh5TT%2BGKaaKj7KP%3DsB44Z-VU4FZvh4qzw0Xkr41A9cZQ%40mail.gmail.com.

Ron Proctor

unread,
Apr 15, 2016, 11:13:46 AM4/15/16
to Blendertarium
That might affect your workstations, but shouldn't affect command line renders.


On Wednesday, April 6, 2016 at 4:26:38 PM UTC-6, Rod Kennedy wrote:
actually we did some digging and turns out it is an issue with Open GL....the new blender doesn't support the older version of Open GL on the machines...it may be something for our IT people. 
On Wed, Apr 6, 2016 at 3:09 PM, Scott Sumner <scottin...@gmail.com> wrote:
Usually for batch rendering I write a shell or Python script to handle it.  As long as the command line implementation of rendering is available that shouldn't be affected.  Sometimes I also use the "frame skip" option that Ron introduced me to.  I'm working on a rendering manager that would allow jobs to be distributed to desktops purely on an "as available" basis.  Once I get that working I'll post about it here.

Scott

On Tue, Apr 5, 2016 at 2:47 PM, Rod Kennedy <rod...@myncsd.org> wrote:
There has been a rumor floating about our staff that seems to indicate that the latest version of Blender won't support rendering on a render farm. This seems completely counterintuitive and counter productive.  Has anyone else encountered this issue? Is it an actual issue or is it a technical problem local to us?  If it is a real problem is there a work around?

We've been doing some good stuff with our render farm and hope that this is just a minor operator error.

Rod Kennedy
Casper Planetarium

--
You received this message because you are subscribed to the Google Groups "Blendertarium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blendertarium+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Blendertarium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blendertarium/I1pNLjY2yP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to blendertarium+unsubscribe@googlegroups.com.

Rod Kennedy

unread,
Apr 15, 2016, 12:51:08 PM4/15/16
to blende...@googlegroups.com
Thanks Ron,
Actually we puzzled it out.  Turns out it wasn't a problem with blender...it was a problem with Windows Remote Desktop.  WRD doesn't support the new version of Open GL...so we simply changed to using Team Viewer to remotely log into the render nodes.
Rod

On Fri, Apr 15, 2016 at 9:13 AM, Ron Proctor <ronpr...@gmail.com> wrote:
That might affect your workstations, but shouldn't affect command line renders.


On Wednesday, April 6, 2016 at 4:26:38 PM UTC-6, Rod Kennedy wrote:
actually we did some digging and turns out it is an issue with Open GL....the new blender doesn't support the older version of Open GL on the machines...it may be something for our IT people. 
On Wed, Apr 6, 2016 at 3:09 PM, Scott Sumner <scottin...@gmail.com> wrote:
Usually for batch rendering I write a shell or Python script to handle it.  As long as the command line implementation of rendering is available that shouldn't be affected.  Sometimes I also use the "frame skip" option that Ron introduced me to.  I'm working on a rendering manager that would allow jobs to be distributed to desktops purely on an "as available" basis.  Once I get that working I'll post about it here.

Scott

On Tue, Apr 5, 2016 at 2:47 PM, Rod Kennedy <rod...@myncsd.org> wrote:
There has been a rumor floating about our staff that seems to indicate that the latest version of Blender won't support rendering on a render farm. This seems completely counterintuitive and counter productive.  Has anyone else encountered this issue? Is it an actual issue or is it a technical problem local to us?  If it is a real problem is there a work around?

We've been doing some good stuff with our render farm and hope that this is just a minor operator error.

Rod Kennedy
Casper Planetarium

--
You received this message because you are subscribed to the Google Groups "Blendertarium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blendertariu...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Blendertarium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blendertarium/I1pNLjY2yP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to blendertariu...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Blendertarium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/blendertarium/I1pNLjY2yP8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to blendertariu...@googlegroups.com.

Visit this group at https://groups.google.com/group/blendertarium.
To view this discussion on the web visit https://groups.google.com/d/msgid/blendertarium/b6b705e8-8bd4-478e-99e1-0aff9e9f8334%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages