This is owen burgess's Typepad Profile.
Join Typepad and start following owen burgess's activity
Join Now!
Already a member? Sign In
owen burgess
Recent Activity
KM, Could you break down this 80% and tell us how you would categorise your problems: . Crash/hang . Incorrect result . How to If a large proportion is Incorrect result and How to, then maybe - in the short term - we should be writing more tutorials and solutions. Would this help? Also, if you care to share, when you encounter a problem with MRfM, where do you go for help? Owen
Toggle Commented May 6, 2009 on Reporting and Analytics at Maya Station
Hi David, Indeed, if you assign an object to a Display Layer then the Drawing Override attributes of your object are determined by the Display Layer. There are two solutions: 1) you assign *only* the root node of your skeleton to the Display Layer. That way the root's children do not have their Drawing Override attributes tied up by the Display Layer. 2) better still, open the Connection Editor and load in: to the left-hand column the Display Layer node, and to the right-hand column an object that is assigned to it, so in this case your Joint. If you highlight the drawInfo attribute of the layer, you will see that it is linked to the drawOverride attribute of the Joint. It is the connection of these attributes that explains why toggling the Visibility on a Display Layer effects the visibility of the objects assigned to it. Let's take a closer look. Expand the attributes and notice that they are both what are known as "compound" attributes. This means that the "child" attributes you've just displayed inherit the connection, and therefore the value of their "parent" attribute. To answer your question, all you have to do is disconnect drawOverride from drawInfo, and proceed to connect the "child" attributes one by one, all *except* the Level of Detail attribute. Now you are free to set this attribute manually, since it is no longer "locked or connected". Cheers, Owen