THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 09/10/2006 at 22:43, xxxxxxxx wrote:
Cinema 4D Version: 10.0
Platform: Windows ;
Language(s) : C++ ;
Look, as a qualifier, I think that my experience with C4D animations in my plugins is veteran-professional. I've done several comissioned and several commercial plugins with animation as a main facet.
R8 - no problems.
R9 - no problems.
R10 - no animation tracks, sequences, keys whatsoever. This is just a recompile of the existing R9 code - no compiler errors or warnings (after GetPoint/GetPolygon changes of course). No error dialogs from my plugin.
What has changed that it compiles cleanly for R10 that it just doesn't create any animation? Since there are no SDK docs yet, I don't know where to begin (actually, I don't want to look - it took me a day just to make the changes from R9 to R10 on this easy compiling stuff).
On 10/10/2006 at 08:27, xxxxxxxx wrote:
Well, if you look at the cinema4dsdk project and the animation plugin file blinker.cpp, you'll notice a lot of changes. I'm going over that area at the moment to see what changes have affected my plugin, too.
On 10/10/2006 at 08:58, xxxxxxxx wrote:
Aha! Also look at the morphmixer.cpp file, and the changes to its function CreateKey().
The R9.x version is using BaseTrack, BaseSequence and BaseKey, and the R10 version is using something new: CTrack and CKey.
In R9.x, you had to allocate a BaseTrack, then add a BaseSequence, then allocate a BaseKey. But, the R10 looks like you simply allocate a CTrack and then add a CKey.
On 10/10/2006 at 12:33, xxxxxxxx wrote:
Well ain't that the cow's manure.
I was looking through the resource api folder and all of the 'legacy' stuff is still there. Why? If it's nonfunctional, it should be removed. That would explain why there are no compiler or runtime errors, but no animation as well.
Thank you very much for the pointers! I will get on it and let you know if the conversion is a success!