Announcement

Collapse
No announcement yet.

motion blur/ alembic

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • motion blur/ alembic

    what is going on here. I have been successfully getting motion blur to work on alembic and all of a sudden I cant get it to work to save my life.
    -------------------------------------------------------
    STEP 1
    Click image for larger version

Name:	example1.JPG
Views:	1
Size:	360.3 KB
ID:	883906
    STEP 2
    Click image for larger version

Name:	example2.jpg
Views:	1
Size:	461.5 KB
ID:	883907
    STEP 3
    Click image for larger version

Name:	example3.JPG
Views:	1
Size:	293.0 KB
ID:	883908
    STEP 4
    Click image for larger version

Name:	example4.JPG
Views:	1
Size:	383.0 KB
ID:	883909
    STEP 5
    Click image for larger version

Name:	example5.jpg
Views:	1
Size:	442.8 KB
ID:	883910

  • #2
    Click image for larger version

Name:	example6.JPG
Views:	1
Size:	453.7 KB
ID:	860343

    Final no motion blur

    Comment


    • #3
      APPROACH 2

      I also tried a second approach which is to export the alembic, reimport to a clean scene, create into a vrayproxy from within maya and then reimport the proxy. this does not work either.

      Approach 2: Step 1
      Click image for larger version

Name:	approach2.JPG
Views:	1
Size:	414.6 KB
ID:	860344

      Approach 2: Step 2. You can see the velocity was brought in just fine.
      Click image for larger version

Name:	approach2_2.JPG
Views:	1
Size:	298.2 KB
ID:	860345

      Approach 2: Step 3, whats odd here is the vrmesh, with the same frame range as the alembic does not match. it seems like first few frames are missing. this is an ongoing problem i'm experiencing and I am quadruple checking to make sure i have it set to 1-80 on alembic export, and proxy creation.
      Click image for larger version

Name:	approach2_3.JPG
Views:	1
Size:	317.2 KB
ID:	860346

      Approach 2: Step 4, you can see the animation is misaligned for some reason. as mentioned above.
      Click image for larger version

Name:	approach2_4.JPG
Views:	1
Size:	298.5 KB
ID:	860347

      Approach 2: Step 5
      Click image for larger version

Name:	approach2_5.jpg
Views:	1
Size:	468.0 KB
ID:	860348
      Last edited by miguelortega; 06-04-2016, 04:54 AM.

      Comment


      • #4
        scene, alembic and vrmesh accessible here: https://www.dropbox.com/s/05sjcogu1m...ubmit.zip?dl=0

        very small file size

        forgot to add this one, just to make sure:
        Click image for larger version

Name:	approach2_tagon.jpg
Views:	1
Size:	502.2 KB
ID:	860350
        Attached Files
        Last edited by miguelortega; 06-04-2016, 05:25 AM. Reason: wrong image

        Comment


        • #5
          I don't think you export velocity at all. For alembic, adding "bifrostVelocity" to the "Motion Vector Color Set" should work even without velocities.
          V-Ray/PhoenixFD for Maya developer

          Comment


          • #6
            But did u see my image steps? I clearly am exporting the velocity. Am I missing a step? You can even see the velocity colors in the images I posted

            Comment


            • #7
              Your vrmesh export is right. I did the same thing and it worked as expected. Which V-Ray version are you using? Maybe there is something wrong with the build.
              About the alembic workflow, it seems Maya will not export the velocity, you must manually specify the Motion Vector Color Set:
              https://knowledge.autodesk.com/suppo...7055D-htm.html

              I will update our help to show this step.
              V-Ray/PhoenixFD for Maya developer

              Comment


              • #8
                I tried with 3.35 and 3.31

                Comment


                • #9
                  im confused, what are you saying is the problem? I still cannot figure this out. This is such a silly thing but i literally have spent 2 days doing this and cant get it to work consistently. it works when it wants to.
                  Last edited by miguelortega; 07-04-2016, 02:30 AM.

                  Comment

                  Working...
                  X