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

    Importing v7 Parameter Track Animation

    SDK Help
    0
    4
    531
    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
      Helper
      last edited by

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

      On 06/03/2003 at 08:35, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   8.012 
      Platform:      
      Language(s) :     C++  ;

      ---------Is there anywhere in the reading of an older version of a data storage format that I can interpret old data tracks and reinterpret them to apply to new parameter tracks? The old system used a minimum and maximum falloff. The new plugin uses an anamorphic falloff system but I want to retain the any parameter animation coming out of the v7 plugin data format.

      bt

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

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

        On 06/03/2003 at 10:48, xxxxxxxx wrote:

        One way to remain backwards compatible is to use the same plugin ID for the R8 plugin. Then C4D will correctly import old tracks. You simply have to check on the fly if a track has been converted and set a flag in the container when it has. I use this method myself in MSA3.

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

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

          On 06/03/2003 at 15:01, xxxxxxxx wrote:

          Quote: Originally posted by Mikael Sterner on 06 March 2003
          >
          > * * *
          >
          > One way to remain backwards compatible is to use the same plugin ID for the R8 plugin. Then C4D will correctly import old tracks. You simply have to check on the fly if a track has been converted and set a flag in the container when it has. I use this method myself in MSA3.
          >
          >
          > * * *

          I am using the same IDs and the track is recognized but never shows up in the timeline ( nor do the parameters show as keyed ). It does import the data and set the first frame if the same parameter ids are used. I cannot see where Parameter tracks are imported and placed?

          Plugin ID the same
          Parameter IDs from the original are all there.
          Message ( when the document is opened ) does show that the track is on the object.
          Timeline nor the AM shows the keyframes.

          Ideas?

          bt

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

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

            On 06/03/2003 at 15:58, xxxxxxxx wrote:

            Also, it seems to me that none of the SDK examples show how to deal with previous version files. In fact, they do not even seem to have the same plugin IDs. Can you just take a simple object such as the double circle and make it work right? That would be a great example. Maybe the rounded tube?

            Thank you,

            bt

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