Holy buckets, Batman! - Part II

[Streetwise]

Here is an image I'm working on that's doing some weird stuff. It doesn't matter if I send the job to BB, or use DR from my workstation, same results. At the point at which I did the screen grab, the network nodes were all on standby (0% CPU). Not sure what's going on. So for the moment, I'm doing a progressive render and that seems to be working for me. This happened once to me before, but I can't find the post or remember what was causing it. Quite odd, and unsettling.

[vlado]

Which V-Ray build is this? Next time it happens, look at the vraylog.txt file on the render slaves and see if there is anything meaningful there.

Best regards,
Vlado

[Streetwise]

Which V-Ray build is this? Next time it happens, look at the vraylog.txt file on the render slaves and see if there is anything meaningful there.

3.30.03

Remind me again where the log file is? I looked in AppData.

[vlado]

Type %temp% in Windows explorer and you'll get to the folder where the file is by default.

Best regards,
Vlado

[Streetwise]

I just checked. See attached. No Weirdness found.vraylog.txt

[vlado]

It looks like 3ds Max already restarted overwriting the previous log. I'm thinking we should keep the last 5 logs or something...

Best regards,
Vlado

[Streetwise]

Is there a way to tell Vray how many logs to keep?

[glorybound]

Windows 10?

[Streetwise]

Windows 10?

LOL. I'll bet you were hoping!? I'm still on 7, especially after reading all the junk you're going through... Or were you saying I should upgrade??

[glorybound]

I would tell you to kill the runtimebroker gremlin

[squeakybadger]

We have started seeing this. It seems to be one node that gets stuck and then everything goes a bit crazy like the image posted.

Only happens with DR though, and you can fix it by just finding the problem node and removing it from the DR properties on the rendering dialog box at the bottom.

I've had a look at the log file and it only gives an error about not being able to delete the server scene file.

[Svetlozar Draganov]

What V-Ray version is that? Does it happen with the latest 3.40.01?
Have you noticed if it is a general issue or it only happens on particular scenes?

[squeakybadger]

It's just a random occurrence for us. Vray is version 3.30.05

I'll update everything to the latest service pack this week and see if it still happens.

[Streetwise]

Seems to be just one scene that is doing it for me. Upgrading to 3.4 didn't fix it. I ended up going "progressive" on it. That seemed to work.

[Morbid Angel]

its probably because your dr slaves have crashed, or failed to begin rendering. Switching to progressive probably used your main workstation to render the scene.
its likely because either there is a missing plugin, or a different vray build or something like that which is preventing them from running.
having said that though, I've had a scene not long ago where from 22 machines 4-5 machines would render then crash, then start rendering again, do some buckets then crash and like that in the loop until the image was done. Though the rest of them rendered fine without crashing.