slave not rendering w/ picture viewer

Mon Jun 22, 2015 6:31 pm

Aoktar, again, I would have thought it is obvious I have thought of this so I am havingg to explain to you that I am not a complete fool. My slave has no reason to be "hanging" which is why I am posting here. There should be no hanging whatsoever. Everything is configured correctly. My polygon counts are not exceeding any of the limits. Not even close. My available vram on the slave is 1.5 GB and this scene is 500 MB. My slave has 2x GTX Titans and 2x GTX 580s.

Please can you help me find a solution?

Mon Jun 22, 2015 6:36 pm

bepeg4d, I don't understand the frame buffer part? I can open that window and monitor vram but vram is not the issue. What does this have to do with frame buffer?

Mon Jun 22, 2015 6:53 pm

garytyler wrote:Aoktar, again, I would have thought it is obvious I have thought of this so I am havingg to explain to you that I am not a complete fool. My slave has no reason to be "hanging" which is why I am posting here. There should be no hanging whatsoever. Everything is configured correctly. My polygon counts are not exceeding any of the limits. Not even close. My available vram on the slave is 1.5 GB and this scene is 500 MB. My slave has 2x GTX Titans and 2x GTX 580s.

Please can you help me find a solution?

Sorry,
propably misunderstood the some part of your message. But i have no idea about internal functioning of network rendering.
As i said in my previous message, it's done by "Octane". I don't doing any special operation. I'm just enabling the network function and rest of job is processing on Octane side. So i can't help for that else asking for some ideas. Abstrax is developing this part.

Mon Jun 22, 2015 6:57 pm

As I asked in a previous post, can you help me reach a person who can give me some guidance on this? It is a painful problem because there is no evidence of anything wrong besides the fact that the slave does not contribute to the render. There needs to be some support for this because there is positively no issues with my network connection, sharing settings, firewall, etc. All of this has been double checked multiple times.

Maybe you do not believe me, but net render works perfectly in Standalone Octane, which is why I am posting in the C4D Forums. How can this be that it works fine in Standalone but not with the plugin? Please make an effort to answer this question. If you cannot answer this question, I have reason to believe this is an problem with the plugin. I currently think it's an issue with the plugin and I want support for it somehow.

Mon Jun 22, 2015 7:04 pm

I believe many others using net render may have this issue and not notice it is happening because all settings and reports will have the appearance that it is working correctly but when you start comparing render times, you will realize that something is wrong.

TO ANYONE USING NET RENDER IN PICTURE VIEWER, I advise comparing your render times and confirm that your slaves are contributing to the render. This is essentially software that pretends to be working but does not.

: Capture.PNG (1.2 KiB) Viewed 4774 times

Mon Jun 22, 2015 7:27 pm

I'll point this issue.

Mon Jun 22, 2015 7:32 pm

This morning, I have went through and tested each GPU from the slave in another machine to confirm there are no issues with them causing the slave to "hang". They all check out fine.

In addition, I tried running only 1 GTX Titan in the slave. My render times came out EXACTLY the same as if I had been running 2x GTX Titans + 2x GTX 580s. Not only does this further eliminate vram concerns but it also further confirms the fact that my slave is a wasted hunk of hardware until this issue is sorted out.

I also ran some net rendering with Vray to confirm there are no issues doing other sorts of network rendering. Yes I know this is a different renderer that probably works very differently but if anyone at Octane has any better ideas, they haven't said them yet. For the record, Vray net renders wonderfully on my machines. File transfers are very fast as well. All my tests point to this being an issue with Octane Software, and one that many Octane users may not even be knowing is happening.

Mon Jun 22, 2015 7:45 pm

I don't have much report about this issue. We will spent time to make some few tests. Please stay tuned...

Mon Jun 22, 2015 7:48 pm

I found this thread that involves a similar error message but using the 3ds Max plugin but gives no resolution to the problem. The issue seems to be related to the actual SAVING of samples rendered by the slaves. It sounds very related to my issue with the c4d Picture Viewer. Ultimately, the thread ends with a link to another thread that seems to have had numerous similar cases reported, but that thread has mysteriously been deleted.

http://render.otoy.com/forum/viewtopic. ... ly#p196262

These other users clearly share my level of frustration in the least, which makes me feel a little less insane.

Mon Jun 22, 2015 7:56 pm

Ok thanks. i'll check it. My idea is still same. If it's working on LV, should work on Picture Viewer. Anyway i need to make some renderings to test it again. I'm away from my network. It's possible to make these tests a few hours later. Even i'm thinking add some log output for getting and printing messages from clients.