Anyone Else Having Team Render Problems?

[BigAl3D]

Cinema 4D r19.053

I tried Team Render with the Beta 1 RC Aug 6 and have strange rendering issues. The scene in question is not using the Denoiser by the way. If this animation is launched using Team Render on the iMac and using a Mac Pro Trashcan and a Windows 10 client in the mix, a couple things happen. The iMac will render as expected, the Mac Pro will render it, but the lighting is way off. I'm not talking about flickering, but a totally different look. Tomorrow, I'll post the two versions. The Windows box just never starts.

As recently as two weeks ago, I've used this same setup except the Mac Pro was the master. Things we've tried: reinstall plain Beta 1, different frame ranges, number of passes, launching from Mac Pro, launching from Windows 10 server. I even tried just hitting render on the Windows Box (no Team Render) and it never started so that PC might have a different issue than TR. Tomorrow, I'm going to zap C4D and Corona from the Windows box and reinstall everything. This is my fastest renderer so I hope this works.

The only way we got this to render is to render different frame ranges on each Mac. Anyone else?

[houska]

Hi,

I will assume that you tried the Beta 2 Daily Build, because that's what we released on August 6th. So you have an animation scene and you are trying to render it using Team Render, right? How many frames does the animation have? What do the console outputs say (Shift+F10)? Have you tried this with a standard C4D renderer? If you try to open the "Team Render Machines" window in C4D, what does it say? Are all the machines present and running? What are the pings and what do the connection tests say? Do you have compatible C4D and Corona versions on all machines?

[BigAl3D]

So you have an animation scene and you are trying to render it using Team Render, right? Yes, but even rendering a single frame has the same issues.

How many frames does the animation have? What do the console outputs say (Shift+F10)? Different projects. One has 800 frames and another has the other has only 130. Still frames have same issue. Very strange.

Have you tried this with a standard C4D renderer? Corona scene renders with Standard and Physical engines.

If you try to open the "Team Render Machines" window in C4D, what does it say? The Mac Pro that rendered the funky lighting showed everything was normal. The only other odd thing was the TIFF files generated were very small file size (12k to 500k for a 1080 size) and Photoshop could not open them,. Sadly those files were trashed. The Windows version never started and never got past the "Preparing Scene Data" and did not list errors in the console.

Are all the machines present and running? Yes. All machines are running and ready.

What are the pings and what do the connection tests say? This is interesting. Pinged the Studio app and the Client app. Only the Windows box had failures: "4 packets transmitted, 0 packets received, 100.0% packet loss." The other clients had 0% loss. Odd thing is, from my Mac, it seems that the Windows box is rendering.

Do you have compatible C4D and Corona versions on all machines? Yes. Everything is the exact same version.


Sometimes simply deleting a tag can get it to work. Sometimes that trick doesn't work. I'm sending a simple scene (MediumComplexity_Singlecloner_Tree_v2) that we've been testing with all day. Started with cubes, but then added a more complex object to push it. Seems like our issues about not rendering is only on the Windows 10 box and happens with and without Team Render. We believe the issues all point to Object Motion blur. If you play with the number of clones and/or the number of Transformation Segments, you this scene with get stuck at Preparing Scene Data.[/b]

In the end, I think this is a continuing issue that I and others have posted about previously. Sorry for the long post.

[houska]

So I found one crash that happened immediately when you started a render. This should be fixed in one of the next daily builds. But I expect there will be more issues, so if you encounter some of them, don't hesitate to report it again, please :-)