Hi,
I’m trying to render some panoramic images but when the render is done, I see little squares showing up. The image has problems that I can’t figure out where do they come from.
I am using the local rendering farm in our office and my personal workstation to do the scene. I suspect the renderin farms is to blame…looks like the rendering buckets are not done rendering yet, or the scene has not been not transferred properly to the farm…
This doesn’t happen when I render from my PC only. Here ate the screenshots.
Hey Mate,
Fixing this will be done by changing (or removing) the bump from the carpet.
This is a problem I’ve encountered a lot and discussed here at great length… I don’t use panoramic rendering so I thought it was fixed (are you using latest release?).
Good luck
Hello,
Could you please advise what is the full version number of V-Ray for Rhino you are using?
The issue could be due to either an unsuccessfully transferred texture to the render node or discrepancies in V-Ray versions between render nodes.
To determine the problem, please do a test render with the DR Bucket render element enabled. This will allow you to match each bucket with the machine which has rendered it. The next step is to access the machine through the V-Ray Swarm interface. Please copy its log and send it over at support@chaosgroup.com . Additionally, compare the V-Ray version used by that render node and the rest. If t here are no errors or warnings in the logs, you might want to try clearing the V-Ray packages on that machine (Disable the node, access the “Versions” section, clear everything, and then reenable the node).
For more info about V-Ray Swarm controls, visit:
https://docs.chaosgroup.com/display/…nal+Menu+Items
https://docs.chaosgroup.com/display/…arm+QuickStart
Should you need any assistance obtaining the required info, simply send us an email (support@chaosgroup.com).
Kind regards,
Peter
Wired…i tried to replicate the scene today but it rendered clean, no buckets, with all the machines in the render farm working together. We have installed the same version of rhino anywhere 3.40.04
Hmm! Don’t know what to say Peter. But it happens time after time, with different scenes. Should be smth connected to the network for sure.
Thanks for the info…Only now I noticed that the bucket appear only in the floor where there is a texture applied and nowhere else. The problem must be with textures not transferring correctly to the farm i guess…
As I mentioned, take a look at the problematic render node’s Swam log. Next time the problem occurs, please search the log for warnings of unsuccessfully transferred assets. Let us know what info there is or whether you need help finding it!
Kind regards,
Peter
Will do Peter as soon as I catch this problem again, thanks a lot for your help!
Had this issue in earlier versions as well - no recent encounters with 3.40, though. It usually occurred in heavy scenes and went all over the place.
I believe it happened when a render client got slower than the host…
Therefore, we usually did used the waekest machine as the host and set it to low thread priority. Maybe that’s something for you to try out?
I haven’t had any more issues so far, strangely… Will keep it in mind for the future though
EDIT: I discovered that the issue was with different Vray versions installed on the render farm. Made a fresh install today with the latest update from the Chaos download page and all works like a charm!
Thanks for the support guys!
Actually, I just saw this happening last week with all versions being exactly the same when all of these options were selected:
- Interactive
- Progressive (needs to be when Interactive is on)
- GPU Acceleration
- Swarm (+2 nodes, host being the weakest machine)
- IM&LC
Turning off GPU Acceleration solved the problem.
Could you please share a screenshot of the incorrect render result?
If you manage to reproduce the issue, could you please send an email at support@chaosgroup.com with info about each machine’s GPU model and driver version?
Kind regards,
Peter
Looks like no CUDA-supported device has been found.
In v3.4 only render nodes with CUDA devices can participate in a GPU render job. Those which don’t quality should not be engaged at all.
Could you please provide us with the previously requested info as well as the full progress log?
Kind regards,
Peter
Hello, Matthias,
We received your email. My colleague already informed you that a proper fix will be available with v3.6. Until then, CPU rendering is the only viable alternative if you wish to initate render jobs from that specific machine with Intel GPU device.
Despite having a fix already prepared, we’re interested in figuring out the exact chronology of the situation you experienced. If you decide to reproduce the issue, in addition to the swarm logs which my colleague requested, would you be able to also send over the full render progress log?
Kind regards,
Peter
Hello Peter,
will do - I’m in a bit of a hurry right now but placed a sticky note on my desktop 
Catch you soon!
Matthias