Have the issues been resolved?
GetContour is not called for frame redraws.
GetContour does not work with Dependence Lists.
GetContour should be rolled into GetVirtualObject and the SPLINE flag should simply return the object as an obejct type of SPLINE.
GetContour and GetVirtualObject do not work with CheckDirty ( very helpful for simplifying flow ).
GetVirtualObject and GetContour do not resolve dirty hierarchies correctly.
These need to be fixed desperately.
The GetContour issues are of serious importance.
An solution for this problem would be very very nice!
GetVirtualObject sould be used for any object type, even Spline.
There must be some solid Spline recognition method.
Some of my Plugins create Spline and Polygon objects changeable.
C4D Objects (Sweep NURBS) can recognize this Spline, but most of the other plugins can't.
It has only been an issue since v6.
I don't think there have been any additions in this area in R9. As with the rest of the application, most API changes have concerned modeling. So yes, GetContour() is still a second-class citizen compared to GetVirtualObject(), and the workaround has the same limitations as before.
My pragmatical recommendation would still hold: use GetVirtualObject() for non-trivial spline generators and don't trust the OBJECT_SPLINE flag when determining what objects to accept as splines.
Most of the features in R9 mean very little to us. We were waiting to see if MAXON would fix the SDK issues that make C4D weak for serious motion graphics work. No offense Mikael, you are very helpful, but these SDK issues have become even more painful as C4D falls further behind in these areas. When S&T; doesn't support a set of splines created with the internal array object there is a big problem ( that was a clue ). More features, less functionality.
Disclaimer: Mikael Sterner is very helpful person who has supported us through problems we could not solve by ourselves. We applaud that him for that.