THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 06/04/2005 at 19:10, xxxxxxxx wrote:
Cinema 4D Version: 8.503
Platform: Windows ; Mac ; Mac OSX ;
Language(s) : C++ ;
Well, much to my chagrin, thinking how easy it is to export/import Position/Rotation/Scale tracks, I find that the client is *really* using an XPresso tag with UserData sliders on the object (despite the test file using the simpler P/R/S tracks). It is this data that is animated, not simple P/R/S tracks.
I note that id = 700 (which appears to correlate to a DynamicSub or DynamicGroup to the best of my searching) and that id = index of affected slider.
If this information is correct, how does one reestablish the link between the Track and the slider data/XPresso node during import?
Might I add that haste is required here!!! There are only two weeks to fulfill this project and only TODAY have I discovered this miscommunication in requirements (which triples/quadruples/who-knows the anticipated workload and schedule to completion).
I WILL contact Maxon directly if there is no response by tomorrow morning.
On 06/04/2005 at 20:38, xxxxxxxx wrote:
This was definitely the correct course. It appears that, at least in this instance, the DescID ids allow me to export and functionally import the XPresso-Port/UserData Value Track information.
In case there are even more XPresso complexities on the horizon, is there anything else that would be beneficial to know (like maybe a different id)?
On 07/04/2005 at 13:30, xxxxxxxx wrote:
I have contacted MaxonUSA tech support as the client is not having the same successful results experienced by me (tested on MacOSX C4D R9.102 English and Windows C4D R9.101 English). Client is using MacOSX C4D R9.101 English.
All other supported track types (Sound/Time/Position/Rotation/Scale) are exporting/importing as expected.
On 08/04/2005 at 10:01, xxxxxxxx wrote:
It appears possible that the client wasn't quitting Cinema 4D prior to updating the plugin (though this would point to them always having it running?). Yesterday it was not working, then a testing update (to check some data in the Console) worked for them. Could be that I had them quit Cinema in order to temporarily move other plugins out of the Plugins folder during troubleshooting.
Tis the joy of working globally...