Author Topic: Velocity pass  (Read 4327 times)

2021-01-28, 18:11:34

maurus

  • Active Users
  • **
  • Posts: 8
  • 42.
    • View Profile
    • Maurus's Insta
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
"The ships hung in the sky in exactly the same way that bricks don't."  -Douglas Adams

2021-01-28, 19:44:55
Reply #1

lollolo

  • Active Users
  • **
  • Posts: 222
    • View Profile
"Fixing the remaining motion blur issues" is not even on the Trello to-do list for v7 or v8. (maybe they will add it later)
It is not important to me personally, but I'm wondering too why this has such a low priority.

2021-01-28, 20:41:12
Reply #2

BigAl3D

  • Active Users
  • **
  • Posts: 879
    • View Profile
They they want Corona to compete with the other engines in the animation world, then everything with motion blur is important. You may be referencing my post about the Velocity Pass. The only reason I tried that method was because there were bugs with the regular motion blur under certain conditions. I believe in my case it was using Mograph and motion blur and objects that had a certain tag on them was causing some things to blur and other no blur. Plus, Mograph would randomly move objects around randomly and on random frames. I should dig up that project to see if v7 handles that any better.

Funny that is was only two years ago, maybe on the first release or even the Alpha version, and we are already at "version 7." I still think the version numbers are moving way too fast. We should be on a lower version number until it's on par with the Max version features, but I digress.

2021-01-29, 17:57:34
Reply #3

maurus

  • Active Users
  • **
  • Posts: 8
  • 42.
    • View Profile
    • Maurus's Insta
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
"The ships hung in the sky in exactly the same way that bricks don't."  -Douglas Adams

2021-02-01, 16:20:22
Reply #4

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3812
  • Bengamin
    • View Profile
    • Cormats
Hi Maurus,

Thanks for your feedback, we really do appreciate it. Some of which you have mentioned are listed in our road map for the future. Have you managed to check it at all? If not, it can be found here: https://trello.com/b/dgI8vjDb/corona-tentative-road-map-cinema-4d. If you would like to see something implemented in a future release, please let us know by posting it to our feature request section of this forum. That can be found here: https://forum.corona-renderer.com/index.php?board=38.0.

There is no favoritism within our team over 3ds Max or C4D. The Max version has been around for much longer and has a larger team than the C4D team. This however has been growing recently and we are working with as much manpower as we have.
Bengamin Jerrems l chaos-corona.com
3D Support Specialist - Corona l contact us
Corona Uploader l Upload
Portfolio l Click me!

2021-02-02, 03:53:12
Reply #5

BigAl3D

  • Active Users
  • **
  • Posts: 879
    • View Profile
This is my biggest frustration that the C4D version of Corona is using the same version number as the more mature product for Max. This is where some of these expectation and frustrations come from. Seems pretty obvious to me.

2021-10-28, 15:20:09
Reply #6

lollolo

  • Active Users
  • **
  • Posts: 222
    • View Profile
Velocity pass is still dead… Hope you have not forgotten ;)