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 - maurus

Pages: [1]
1
[C4D] Feature Requests / Re: Textures on Area Lights
« on: 2021-03-05, 10:40:38 »
+1

2
[C4D] Resolved Bugs / Re: C4D Layer Shader in Bump channel
« on: 2021-03-05, 10:40:00 »
+1 to this

3
+1 As everyone's using x-particles fro pretty much every cool rendering, this is definitely a MUST DO. Thank you for the timely implementation!

4
[C4D] Feature Requests / Re: TurbulenceFD Support
« on: 2021-03-02, 16:29:31 »
+1

5
[C4D] Bug Reporting / Re: Velocity pass
« on: 2021-01-29, 17:57:34 »
They they want Corona to compete with the other engines in the animation world, then everything with motion blur is important.
...

Actually I didn't try the burn-in motion blur much. The render for the animation I'm working on right now takes so long, that it would be too "dangerous" or tricky to work with a direct motion blur (as well as Depth of Field) as I want as much control as possible in the post. I'm not sure what I should think about when I work with a professional compositing tool like Nuke or, like in my case, Fusion that support motion blur with a velocity-pass in post, and then the render engine is buggy and can't deliver. I can't understand that this important feature is swept under the table. I mean, it's information that is arleady available while the rendering process - it's not something that has to be calculated separately. But I'm no programmer and I may missing an important issue for embedding/fixing the velocity-pass.

The best part is, that Render Legion / Chaos Group still has the tutorial online that describes the workflow when working with vector motion blur as a multipass source!

To be honest: I'm quite disappointed right now. I really like the corona renderer! It's easy and straight forward, it's fast and the results are nice! But! There are more and more flaws that bug me and for some points a fix or correction it's not even in sight! Not to talk about that it would come soon...

Here just a few points concerning the Cinema 4D version:
- The in this thread mentioned vector motion blur pass bug.
- MoGraph Multi-instancing still doesn't work bug-free (even though they said it would work in the daily build of v7. But it only works in simple scenes).
- Display-Tag has no effect.
- No VDB integration.
- X-particles work only with a workaround.
- No clouds from Cinema Cloud System (even though they're worth close to nothing, but I would have been happy about two or three times for that).
- PyroCluster and other smoke- and volume effects don't work.
- No animation rendering in the VFB (also no LightMix for animations. Though I kind of understand this one).
- No Rendering in Takes.
- No ACES-Support (Hello! It's 2021! ACES is still quite new though, but very important for a professional workflow in a line with footage from other sources such as Film cameras or other VFX-Tools and a professional colour grading workflow).
- The much praised Material-Library that Corona has in the MAX version is still not available for Cinema 4D. And AFAIK it's not even planned...

Again, I really like the Corona renderer! And I try to motivate me to not switch do another renderer (My No.1 candidate is Arnold, followed by Octane-X (as soon as I've got my new MacBook Pro 16" M1X) and Redshift (as soon as they adapt to Metal).
Many of the above mentioned bugs or missing (important) features give me the feeling, that MAX is clearly the preferred draught horse of Render Legion / Chaos group and that the Cinema version is just the little annoying brother that mom said you have to take with you when you go play with your friends. Also they give me the feeling, that they only want to please the architectural rendering artists and basically ignore the rest that do cool motion graphics and animations.

@ The developers: That's nothing personal! Again, I really like Corona and I would be sad if I have to decide to switch my main render engine. But some of the above mentioned points are too important to be ignored.
A statement would be appreciated!

Best
Maurus

6
[C4D] Bug Reporting / Velocity pass
« on: 2021-01-28, 18:11:34 »
Hey folks!

I wonder what's about the bug with the velocity-pass in Cinema 4D. I mean, I've seen that other post from two years ago saying, that this is a known issue. Well, I'm not a programmer, but I think two years should be enough to fix the bug of this very important render pass. ¯\_(ツ)_/¯
Or do I make something wrong? If so, then I'm deeply sorry! But I'm used from the corona render, that the settings are already set to "best" out of the box. Therefore I think it's supposed to work without much tweaking, no?
I've tried different settings and different animation methods (object movement, camera movement, animated effectors., etc.), but still - black image.
Or has maybe someone a workaround for this issue?
At the moment I'm quite disappointed. I would have been happy to have a velocity pass several times. :(

Thank you and cheers
Maurus

7
Hardware / Corona and Apple Silicon
« on: 2021-01-09, 11:49:02 »
Hello friends

Has anyone tested corona on an Apple Silicon device? How's the performance?
And even more important: Does Corona work on an M1 at all? I mean like really working, not just "somehow spitting out an emulated image".

If someone of the developers can give me the guarantee that corona works on silicon, then I'd be willing to maybe get a MacBook Air M1 and run some tests.

Thanks and cheers!

8
[Max] Resolved Feature Requests / ACEScg
« on: 2020-03-02, 22:58:00 »
Hey everybody!

How about ACES (or ACEScg) support for Corona? Linear kinda works though it would be nice to be able to get the maximum out of my renders with ACEScg in my ACEScct workflow.

Cheers
Maurus

Pages: [1]