THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/04/2012 at 06:41, xxxxxxxx wrote:
Cinema 4D Version: R13
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
What changed between R12 and R13 for Hair Guides Link? My OneSpline plugin works in R12 but, even built for R13, it has undesirable results. Saved out of R12 and opened in R13, same problem. Using the R12 version of my plugin in R13, same problem. My diagnosis: Something changed in the way that this Link field works in R13 and it isn't my plugin (or I don't know how to 'fix' it). OneSpline is a generator that accepts multiple splines as input and outputs a single spline (multi-segment). Works in all previous versions of Cinema 4D but not in R13. If I Make Editable (which should be identical to the returned cache of GetVirtualObjects()), that new object seems to work. Has there been a change in generator objects returning a spline object not mentioned in the SDK documentation?
On 28/04/2012 at 18:08, xxxxxxxx wrote:
While GetContour() works, changes to the input splines are not relayed to the results. This is a bit frustrating since GetContour() seems to be more about generating a spline object result parametrically instead of as a result of input objects (it isn't call on changes to the input objects and has no cache/dirty checking). There has been no change in the GetVirtualObjects() results - the Hair Guides Link always produces incorrect results.
On 29/04/2012 at 00:52, xxxxxxxx wrote:
I guess you could use the GetContour solution from here:
It works fine for my spline generators using external splines as input.
On 30/04/2012 at 03:57, xxxxxxxx wrote:
The CheckDirty() solution appears to have solved it! Yay!!