Dealing with a CurrentStateToObject bug
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 11/10/2006 at 04:46, xxxxxxxx wrote:
User Information:
Cinema 4D Version: 9.6
Platform: Windows ;
Language(s) : C++ ;---------
Hi,
I have found a inconsistency bug with the Current State To Object command. My question is, how should I deal with it?
My plugin needs to get the deformed points of a polygon object in a TagData plugin.
If you have a polygon object, that has a deformer as its child, and you add an additional tag (such as a material) on the the polygon object, and then you execute the Current State To Object.
The resulting deformed polygon object magically appears under a Null Object instead of just being a polygon object.
This only happens in the above sitation.
ONLY Test 4 will produce a polygon under a Null Object, the other Test object actually returns a polygon object.
Well I need to do the above through code, so the only way I can think of to deal with it is to check the result of the MCOMMAND_CURRENTSTATETOOBJECT to see if its a null and has a polygon child.
As anyone else experienced this before?
Thanks
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 11/10/2006 at 06:29, xxxxxxxx wrote:
yep. Happens also in other situations (in generators). I am also simply checking if there is a null-object and go thru the hierarchy until it finds a polygon object.