Results 1 to 11 of 11

Thread: LW 2018 Motion buffers issue

  1. #1

    LW 2018 Motion buffers issue

    I am having an issue in 2018 with motion buffers.

    I have the motion buffer enabled and have it to save. I have tried saving it as part of a multi-layered .exr, and also as a file of its own. When I'm in after effects using the Extractor to separate them out, it shows that there are X and Y buffers in the multi-layered .exr, but it doesn't seem like there is any data. Has anyone else had this issue? Is this a bug?

    Same workflow works fine in 2015 using the compositing buffer export.

  2. #2
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,824
    i’ve had an issue with the depth buffer and no data. don’t know if it’s related.

    do you have exr trader? could try that. i can’t say if it works as i haven’t upgraded.

    i do get the feeling that there are some bugs in there.
    Last edited by gar26lw; 02-24-2018 at 06:58 PM.

  3. #3
    I recently reported a bug about motion buffers; they currently completely ignore deforming objects and only operate off of direct translate/rotate/scale (keyframed) movements.
    Professional-level 3d training: Ryan's Lightwave Learning
    Plugin Developer: RR Tools for Lightwave

  4. #4
    LightWave Engineer Jarno's Avatar
    Join Date
    Aug 2003
    Location
    New Zealand
    Posts
    597
    There is an issue with the motion buffer creation. It will only work if Motion Blur is on in the camera, and the deformations have actuallly moved some vertices at the current scene time.

    ---JvdL---

  5. #5
    Quote Originally Posted by Jarno View Post
    There is an issue with the motion buffer creation. It will only work if Motion Blur is on in the camera, and the deformations have actuallly moved some vertices at the current scene time.

    ---JvdL---
    The info is greatly appreciated, that'll tide me over until any changes are put in place.
    Professional-level 3d training: Ryan's Lightwave Learning
    Plugin Developer: RR Tools for Lightwave

  6. #6
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,493
    Quote Originally Posted by Jarno View Post
    There is an issue with the motion buffer creation. It will only work if Motion Blur is on in the camera, and the deformations have actuallly moved some vertices at the current scene time.
    Jarno, please clarify: Presuming camera Motion Blur is enabled, are you saying deformation motion only gets recorded to motion buffer if there's actual deformation delta for vertices at the current scene time, or that no motion gets recorded to motion buffer unless there's deformation delta for vertices at the current scene time?
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

  7. #7
    Well, Jarno is right, in the sense that the Motion buffer data saves only when Motion Blur is checked. But that kind of defeats the purpose. Now the beauty pass and alpha channel have a rendered blur on them. I even tried turning on camera motion blur and setting the blur length to zero, but then no motion vector data records at all.

  8. #8
    LightWave Engineer Jarno's Avatar
    Join Date
    Aug 2003
    Location
    New Zealand
    Posts
    597
    It is a bug in determining whether or not motion vectors should be calculated from deformation. Motion vectors are used for the motion buffer, and also for motion blur. However, it only checks for the motion blur being active. Probably because the motion vector code was originally written for motion blur purposes only, and then the motion buffer was just seen as a way of capturing that blur in a buffer.
    It wasn't realised that the needs of the motion buffer was independent of rendering motion blur.

    A second bug in the same code attempts to do an optimization by only calculating the motion vectors from deformation if there is any actual deformation going on. It does that by checking a flag, assuming that flag means that the mesh has deformations applied. But it actually means "this mesh was deformed the last time the mesh was evaluated". Typically the last time the mesh was evaluated is at the scene time at the start of the frame.
    So if a mesh switches from non-deforming to deforming over the duration of the frame, it still thinks the mesh isn't deforming at all and no motion vectors from deformation are calculated.

    All this is a long-winded way of saying that a fix is in testing.

    ---JvdL---

  9. #9
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,493
    Quote Originally Posted by Jarno View Post
    All this is a long-winded way of saying that a fix is in testing.
    The additional info helps us work around the situation, though, so thanks!

    Can you clarify whether the fix will address both the incorrect interpretation of whether mesh deformation needs tracking and that motion blur needs to be active? Requiring motion blur be active, as Axis3d mentions, somewhat defeats the purpose -- hopefully the fix addresses both issues, and not just the deformation flag issue.
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

  10. #10
    LightWave Engineer Jarno's Avatar
    Join Date
    Aug 2003
    Location
    New Zealand
    Posts
    597
    The intention is that the buffer will work with motion blur turned off.

    ---JvdL---

  11. #11
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,493
    Quote Originally Posted by Jarno View Post
    The intention is that the buffer will work with motion blur turned off.
    Great to hear, thanks for the clarification!
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •