Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    CKey->SetTimeLeft/Right Quantized?

    Scheduled Pinned Locked Moved SDK Help
    3 Posts 0 Posters 321 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H Offline
      Helper
      last edited by

      THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

      On 25/11/2007 at 14:05, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   R10 
      Platform:   Windows  ; Mac  ;  Mac OSX  ; 
      Language(s) :     C++  ;

      ---------
      Why is it that when I set the Left and Right Tangent times for a CKey, the BaseTime automagically (and disastrously) quantizes to the nearest frame? I don't want this. For tangents, the Time value should not be forced to an integer frame value - but I can't as well set the darned bloody thing using anything but a BaseTime. No wonder I can't get the darned tangents to be correct for the type of spline being calculated (Natural Cubic Spline - look 'er up, mates)!

      Suggestions? Anyone have a butter knife so that I can cut out my heart with less pain than this?

      1 Reply Last reply Reply Quote 0
      • H Offline
        Helper
        last edited by

        THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

        On 26/11/2007 at 00:02, xxxxxxxx wrote:

        I will ask the developers what is going on here.

        cheers,
        Matthias

        1 Reply Last reply Reply Quote 0
        • H Offline
          Helper
          last edited by

          THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

          On 26/11/2007 at 07:45, xxxxxxxx wrote:

          I found out that instead of using:

          BaseTime::BaseTime(value, fps);

          which always quantizes, this works though it didn't the first time I tried it (?) :

          BaseTime::BaseTime(value/fps);

          Using SetNominator() and SetDenominator() didn't scale value appropriatedly with respect to fps. Looking at the code for BaseTime, BaseTime(r, n) automatically quantizes (using Floor).

          Thanks

          1 Reply Last reply Reply Quote 0
          • First post
            Last post