Topics

31

[C4D] Bug Reporting / TR clients disconnects - [TR] Frame synchronization failed: Communication Error

« on: 2019-01-30, 18:44:16 »

MacOS 10.13.6 / C4D Studio R18.057 / Version: 3 hotfix 1 (core 3) Jan 18 2019 18:43:49

I don’t wanna beat a dead horse here, but I’m still getting random TR client disconnects that makes Team Render highly unreliable.
Not sure how much this is a C4D TR rather than a Corona issue.
I saw on the trello board that “Team render stability improvements” are planned for V.4
Will the “com error” be addressed that causes frame sync to fail?
Once I finish my current job, will install V.4 daily and check if stability has improved.

To recreate this error, almost any scene will do, just setting the render res high enough.
In my case rendering a 6k image will trigger client disconnects.

Some FYI”s
- Network: 1Gb LAN, Jumbo frames enabled in the entire chain.[/li][/list]
- Server/clients all macs
- Random clients at random times disconnects.
- CoronaTR manual settings:
 Tried many different combinations 10s-20s / 50MB, 75MB,100MB, 200MB all combinations had disconnects
- I have the 1WS/3nodes license - disconnects if I use 1 or all 3 nodes.
- Adding clients over time, to possibly not have them all send data at the same time, does not make a difference and shouldn't with just 3 nodes.

I noticed all TR consoles always say “rendering pass 2” no matter what actual pass gets rendered.
Could increasing the time between the 7 retries help?

TR console sample:

Code: [Select]

2019/01/30 08:23:18  [Corona4D] [TR] Sending chunk 0/10 to the server
2019/01/30 08:23:41  [Corona4D] [TR] Sending chunk 1/10 to the server
2019/01/30 08:23:43  [Corona4D] Rendering pass 2
2019/01/30 08:24:05  [Corona4D] Rendering initial pass
2019/01/30 08:24:05  [Corona4D] [TR] Sending chunk 2/10 to the server
2019/01/30 08:24:28  [Corona4D] [TR] Sending chunk 3/10 to the server
2019/01/30 08:24:52  [Corona4D] [TR] Sending chunk 4/10 to the server
2019/01/30 08:25:17  [Corona4D] [TR] Sending chunk 5/10 to the server
2019/01/30 08:25:41  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:03  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:06  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:07  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:09  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:10  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:12  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:12  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:14  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:15  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:16  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:17  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:19  [Corona4D] [TR] Sending chunk 6/10 to the server
2019/01/30 08:26:19  [Corona4D] [TR] Frame synchronization failed: Communication Error
2019/01/30 08:26:19  [Corona4D] CoronaCore::renderFrame: after render
2019/01/30 08:26:19  [Corona4D] Terminating DR slaves
2019/01/30 08:26:19  [Corona4D]  - terminating slave handlers
2019/01/30 08:26:19  [Corona4D]  - waiting for broadcast thread to finish
2019/01/30 08:26:19  [Corona4D]  - clearing slave handlers
2019/01/30 08:26:19  [Corona4D] Terminating DR slaves ended

Let me know if you need more info.

Thanks!

32

[C4D] Bug Reporting / VFB “region” render in Team Render not working

« on: 2019-01-15, 03:23:22 »

MacOs 10.13.6 / C4D Studio R18.057 / Version: 3.0 (core 3)

Not sure if this a known issue, since it never worked (for me).
Note: This is only in TR mode, single machine render region works flawless.

I can draw a  “region” marque in VFB, but it continues to render the entire image.
Same, if the region is already set in VFB before hitting “Team render to PV”

What does work is to set “Render Region” in the render setting > output tab.
Of course that’s a static selection and can’t be changed while rendering.

Not a high priority since there is a workaround, but do you guys have any plans to make the “Corona render region” work in TR mode?

33

[C4D] Bug Reporting / Can’t open CXR in CIE 3

« on: 2019-01-08, 16:09:53 »

MacOS 10.13.6 / C4D Studio R18.057 / Corona 3.0 stable

Get “Unexpected attribute type” with any .cxr I try.
The last version that worked for me was Beta 2 stable.

34

[C4D] General Discussion / CXR saving in picture viewer support

« on: 2019-01-07, 20:17:41 »

I  just realized that "CXR saving in picture viewer" disappeared from the trello board
I didn't yet install/activate my Corona 3 final, but wonder if it made it into this release.
It used to be on the roadmap for C 3, but now it's not mentioned anymore.

The ability to select CXR in render settings is such an important feature for users that send jobs to render farms and need to get a .cxr file back .

Edit:
Oh no, it didn't disappear, it was moved to the "big ideas" pile.... Sorry, missed that.
Does that mean it turned into a big "maybe not"?

Does anybody have an idea for a workaround if you need a .cxr file from a render farm?

35

[C4D] General Discussion / Your experience with teamrender

« on: 2018-11-07, 21:01:39 »

Hi,
I’m currently using Corona version: B2 on mac R18 on server and client.
I’m testing a scene that takes 39:28 min to render to noise level 5% on my main machine.
When adding 1 node in teamrender the render time goes to 29:29 min.
I didn’t expect render times to be cut in half, but definitely better than what I get.
Corona render settings “TR” is set to automatic. Network: wired 1 gigabit LAN.

I plan to use 1 corona license with 3 nodes (if that’s what we’ll get when released)
and send larger jobs that require faster turnaround / more compute power to a render farm. I only do still images.
If the LAN is a bottleneck, would upgrading to a 10 gigabit make sense?
I’m not even sure the gigabit is saturated as it is.

What’s your experience regarding TR?
Any tips on how to minimize overhead / get faster renderings?
How well do additional nodes scale?

Thanks.

36

[C4D] Resolved Bugs / IES light not rendering in team render.

« on: 2018-06-22, 20:55:55 »

Version: B2 daily May 30 2018 (core 2 DailyBuild May 30 2018) (same version on all nodes)
Cinema version: CINEMA 4D Studio R18.057
OS: Mac OSX 10.10.5

Hi all,
I'm using a IES file located in the "ies" folder, inside the project folder.
The IES renders fine when "render to picture viewer" on my main machine, but does not render when "team render to PV". Just the corona light renders without using the ies file.
I also tried the IES file placed in the "tex" folder (of course updated the path in corona light).
The ies only renders if the path looks like this "./filename.ies"  or "./ies/filename.ies"
If the dot in front is removed  "/filename.ies" or just "filename.ies" the light will not render.
I would assume with "filename.ies" c4d finds the file in the "tex" folder, but that's not the case.

It might be related to how c4d on mac os handles relative paths?

As a workaround I tried to use the UHD cache saved from "render to pv"
and load the file when using team render without success.
I looks like Corona still needs the ies file to calculate the light.

Can other mac c4d users confirm if ies lights work in team render.
Any ideas for a workaround?

Thank you.