DR rendering problem:

[dlparisi]

So what was it?

[natty]

Problem solved.

Enlighten us..

[nirsul]

I cant say for sure as all the required steps were already done and still had situations where if I only ran 1 slave it rendered OK but adding the additional 2 caused all of them not to render.

I even changed the slots of my 3Com switch (8 slots).

the next day I restarted all 4 Pcs and they all rendered OK at once.

so I cannot really explained it.

Bits me but for the last 2 days They are working as they should - TOUCH WOOD .....

NIR

[nirsul]

OK

I am back and this is because last weekend I re-installed SP3(a) after returning to SP2 (a bug that was fixed in the latest release 'a').

Problem is - out of 3 slaves - (all are similar ) one o is not rendering texutres. the rest are OK - meaning theat maps are correctly named (UNC)
I checked firewalls and even tried turning off - not helping.
I re-created the slaves list (made sure thay respond) in the Render Setup > Distributed Rendering > settings...

I created a simple scene with one texutre (UNC) :






Ping - both ways works nicely.
I restarted each PC.
I even re-installed VRAY SP3a
I truned off and then on the SWITCH box/router
I verified that the license is visible from the slaves.
I verified that the slave is aiming at the correct port 30304 (on the client's IP)

I am stuck really.

last time it was solved by itself (as I couldn't point a finger at one thing I did)

NIR

[vlado]

In general the only way to handle textures that is guaranteed to work 100% is to copy them locally on each slave. In many cases, accessing the textures from a network works fine also, but there are exceptions like in your case.

Best regards,
Vlado

[nirsul]

Vlado

Luckily for me (as I may use SP2 happily) and bad for you: I re-installed SP2 and the problem is gone - on the first try !!!

I am SURE that it is a bug in SP3/SP3a

You have a scene I scene which I sent you yesterday - this is the same scene I was having troubles with (the images posted here are from a very simple scene to test the network - I may sent it to you)

NIR

[dmartind3]

I too am having this issue, and it seems as though it has to do with how the irradiance map is passed to each slave. Is this possible, or am I way off? The other thing is, if it happens on one file with textures, but renders fine on a completely different file with textures, what does that mean?

[natty]

Hi

when you update to SP3 are you also updated the License server to SP3 ?

[nirsul]

All the related Pcs were updated to SP3a

but for now I will stick to SP2 as Vlado's remark means that it is not something he knows about and that can be fixed.

Nir

[vlado]

I am SURE that it is a bug in SP3/SP3a

While it definitely is a problem (although I am not at all sure it is a bug in V-Ray), it is definitely not a SP3 bug, as people have had similar issues with previous versions of V-Ray also.

Best regards,
Vlado

[nirsul]

Vlado

whatever you need of me to help solve this as I would
like to able to use SP3x.
I can tell you that the moment I ran SP2 this specific problem - vanished.

if you want me to send you the specs of my system/s - just ask.

Nir

[vlado]

I just have to find a way of reproducing this in our network here somehow...

Best regards,
Vlado

[grasshopper]

When we had this problem I'm sure we solved it with creating a new render node account with full access permission control. then using this as a login for all the render nodes. Also make sure your .ini files are up to date. We started using bat files to keep them synchronized.