Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - BigAl3D

Pages: [1] 2 3 ... 15
I've had this issue as well, however, in v5 it's better. Even fewer crashes when using the Render View option instead of the other window. In either case, if you try and move around too fast, or especially, if you use the F and G keys too fast in order to scrub in the timeline, crash.

This looks great. Is this plug-in Mac Cinema 4D r20 and Corona v5 compatible? I only see it running on Windows in your videos. Thanks.

Hmmm, I'm not familiar with a "Material Import function" in Corona or C4D. Usually models, you download from the internet, will will have their own Tex folder, but the paths are not localized so the file cannot find the textures. You can move the texture files so they are in the same folder as the C4D file, it will find them. You would probably copy the textures to your main Tex folder that your C4D points to. Then, when you import your model, the materials will be there.

Corona Renderer for Cinema 4D - general / Normal Map for AE?
« on: 2019-12-05, 01:38:30 »
What I want to do is render a pass with the normals of a material and use an AE plugin (like Normality) to change the reflections on a surface, i.e. change the reflections from trees to a city street. I can get normal maps out of Corona, but they are yellow to pink instead of the typical purple-to-pin-to-green. Is this possible?



Bug Reporting Cinema 4D / Re: Teamrenderer objects darker
« on: 2019-12-03, 19:28:00 »
I will confirm that the Xref issue is indeed a Maxon issue. I had this problem last year and learned of this bug over on I didn't realize you had Xrefs in that scene or I would have mentioned it. Xrefs would be very useful if they worked properly, but I don't trust them. I've had a car model's parts explode when trying to scale it.

Doesn't X-Particles utilize elements from Mograph and Instances and Multi-Instances? I'm not sure, but I seem to remember some mention of this in the past. Perhaps when they solve the existing issues with Mograph, it will make it easier to get Corona and X-Particles to play nice together.

@DH3 This sounds like the same issue we had, as well as others in the past. There's a bug with the camera tag and the devs are aware of it. The simple workaround is here in a quote from my previous post:

"As far as I know, the Corona Camera Tag on the Mac is still an issue. If you copy the camera tag setting to the Camera/Post Processing tab in the render settings and check Use Photographic Exposure, everything renders fine. At least it's an easy workaround."

Gallery / Re: 2018 Ford Expedition
« on: 2019-10-28, 18:43:15 »
@redstarcg Just saw these shots. Very nice. Can you elaborate on what we're looking at? Just the Expedition is CGI or are the entire scenes? How much retouching was done vs. just Corona? Thanks.

Gallery / Re: Mercedes Benz C63s AMG
« on: 2019-10-28, 18:33:35 »
Just saw this. Great work.

I need help Cinema 4D / Re: Rig / render differences
« on: 2019-10-28, 18:25:14 »
Motion blur has several known bugs they're working on. Curious though, did you test whether it's Enable Camera, Enable Objects or both?

FYI - Knowing more details about your project would help. How large is your render size? Animation? How long?

@Barendby We had a similar issue recently and the issue seemed to be when using several nodes in particular, having the "Client Update Interval" too low (sending data more often), then this seems to overwhelm the network. Go to the Team Render tab in the Corona render settings and change Configuration to Manual. Then you can change those numbers. By default it's 5 seconds and 64 MB. If your frames take a few minutes to render, try 30 sec or more. Otherwise, every node is trying to send 64 MB of data every SECOND back over the network. This can get out of hand quickly.

Let us know if this works. Here's a recent thread I had started on this topic.

I need help Cinema 4D / Re: More Team Render Woes
« on: 2019-10-23, 20:32:04 »
Forgot to revisit this thread. We think at some point we may have reduced the interval down to 1 sec when we had problems. The funny thing is, when we got it to work, the number was increased back to the original 5 sec.

I need help Cinema 4D / Re: More Team Render Woes
« on: 2019-10-17, 19:45:56 »
Thanks for the reply. Yes that makes a lot of sense as far as not overloading the network. No point in sending tiny chunks every second, when you don't need to. Some info on our LAN. Seems to be fast to my little brain.

10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.153/0.186/0.220/0.023 ms

10 Gbit/s

The nodes can range from one to eight. Some scenes are too slow on certain nodes. So if we do use all eight nodes, it would make sense to increase the time interval AND the size of the chunks, correct?

Could be also you're using a demo material you downloaded. I've seen that before.

I need help Cinema 4D / More Team Render Woes
« on: 2019-10-16, 23:57:27 »
So for some reason, we started getting this strange error when using Team Render. We were rendering a still frame at 4k, with some Depth of Field effect. Previously, we tried an 8k still and could not get it to work at all. Not sure if it has anything to do with Maximum size of packets settings or not, but I've never fully understood those numbers. Although, after we changed to to Interval to 1 and Packet Size to 30, it seems to work better. I just revisited an old thread where TomG talked about large size images and manually setting those numbers to 20s and 256MB.

(Complete Console text attached)

2019/10/16 17:26:55  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:26:56  [Corona4D]
Frame synchronization failed: Communication Error
2019/10/16 17:26:57  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:26:57  [Corona4D]
Frame synchronization failed: Communication Error
2019/10/16 17:26:59  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:26:59  [Corona4D]
Frame synchronization failed: Communication Error
2019/10/16 17:27:00  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:27:00  [Corona4D]
Frame synchronization failed: Communication Error
2019/10/16 17:27:02  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:27:02  [Corona4D]
Frame synchronization failed: Communication Error
2019/10/16 17:27:03  [Corona4D]
Sending chunk 26/30 to the server
2019/10/16 17:27:04  [Corona4D]
Frame synchronization failed: Communication Error

Then the clients start dropping off the render job. Didn't matter if we launched the render from the Mac Pro or the iMac. We have a couple of Windows 10 clients too, but only render clients.

Full-speed non-debug version
Build timestamp: Sep 26 2019 12:25:41
Version: 4 hotfix 3 (core 4 (Hotfix 3))
Cinema version: R20.059 CINEMA 4D Studio (single-license)

MacOS 10.12.4 (16E195)
Mac Pro (late 2013)

Pages: [1] 2 3 ... 15