Announcement

Collapse
No announcement yet.

Vantage timeline mismatch

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

  • Vantage timeline mismatch

    If the timeline in Vantage is 0 to 100 then it renders 100 frames.
    In Max 0 to 100 is actually 101 frames.
    A camera from Vantage coming into Max from a Vantage file thus has
    incorrect keyframes, one at 0 and the other at 100, making the output 101 frames.
    https://www.behance.net/bartgelin

  • #2
    Of course I can manually fix this by moving each end keyframe in Max back by one, though this is prone to error or forgetfulness, so I wonder if you guys can confirm it
    for me please and say whether it can be fixed for the next update or just something we'll need to remember to compensate for.

    I'm also unsure how this would impact keyframes that are not simply one at the beginning and one at the end, as I've instructed the cameraman to not make that type of move,
    so as to not to introduce further confusion into this project.

    Cheers
    https://www.behance.net/bartgelin

    Comment


    • #3
      Hi,

      I actually got this wrong; the situation is that a 100 frame shot in Vantage means the camera updated to Max goes from 0 to 101, meaning the output is actually 102 frames.

      No response to this anyway, so either only I am experiencing this, or I have missed a setting somewhere despite searching, or it's simply a non-issue for everyone else.
      Maybe it doesn't happen with Maya/C4d or others...maybe this post remains unseen....lost in the interwebular somewhere...who knows?!
      https://www.behance.net/bartgelin

      Comment


      • #4
        So, in my ongoing blog here on the forum, we shall be discussing why this behaviour exists and how to avoid it

        The issue outlined above relates to a camera move over what 'appears' to be 100 frames in Vantage and in reality renders out as 100 frames.
        There is little info about this next part anywhere, so hopefully this helps others.

        When initially trying to set this up, one of the only videos I saw, possibly the actual webinar, set up a simple move by making the first camera, setting that to 'transient',
        making the second camera and setting that also to transient, then insert a transition before the second camera that is however long you want the timeline to be for that move.

        In my example of a 100 frame Vantage animation I did just this and indeed I got a 100 frame timeline in Vantage.
        I needed to get that camera animation back into Max - but the problem is that is was always coming in as the incorrect amount of frames,
        with the wrong keyframe positions.

        The partial answer, as I have just found, is that it is these transient frames that create this issue themselves. What appears to be 100 frames is in fact not, as those transients are not, as I thought,
        'instantaneous'...really not quite 'frames', as the video suggests, but actual frames. Hence the mismatch.

        This is where I still remain somewhat confused. The indicator for a transient frame is a very thin orange box, however the indicator for a 'frame' is a wider, uncoloured box, suggesting they are separate and different.
        So I wonder what is the point of having a transient if (forgive me if I missed its explanation somewhere) it is no different from setting that specific camera's duration to 1 frame?
        Also in this example, if a transient is 1 frame at the beginning and end, with a transition of 100 frames, why does the timeline still display as 100 frames, render out 100 frames but yet the camera export is 102 frames?
        Hopefully this confusion is clear.

        Setting it to 1 frame, as well as that of the end frame, is logical, meaning a transition of 98 frames to make the total, meaning at least I get a matched camera, (although, however not importantly, the imported timeline in Max is still incorrectly 101 frames).

        This took me days to figure out and has caused so much hair-tearing that I almost gave up....glad I didn't now and I hope this helps.
        https://www.behance.net/bartgelin

        Comment


        • #5
          Hi fixeighted,

          I have logged the issue and will take a look at it. I will inform you when there is some development on the matter.

          Best regards,
          Alecander
          Alexander Atanasov

          V-Ray for Unreal & Chaos Vantage QA

          Chaos

          Comment


          • #6
            Sure, thanks.
            I've solved the problem insofar as I can from my end, so am sure these things will be fixed in due course. It is stll beta software so didn't expect it to be without
            weird stuff
            I remain a firm supporter of it anyway, and despite this hopefully final little problem it has been literally invaluable on this project, saving untold £1000s of trad renderfarmed Vray output
            https://www.behance.net/bartgelin

            Comment


            • #7
              If the timeline in Vantage is 0 to 100 then it renders 100 frames.
              This should be fixed in the build we released yesterday - version 1.4.2.

              Greetings,
              Vladimir Nedev
              Vantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help

              Comment


              • #8
                Ah ok, I actually thought that was already fixed but thanks for the update
                https://www.behance.net/bartgelin

                Comment

                Working...
                X