Hey Guys,

I’m asking this in this forum because the python code for motionbuilder seems to have changed a little to carry out commands, and I’m using mobu 2009. I don’t want to run into problems because the code is now different to what the suggestive solution might be.

Is there any way to visually show that a character has been selected through code? That is, I’d like to know if mobu has some functionality that highlights the related mesh of a character. I’d like to avoid simply selecting the character mesh because that confuses the artist as he is looking at the animation. I’ve got 20 character instances in a scene and a dialog with 20 character names. I select 1 of the names, and I’d like motionbuilder to somehow visually show me who I’ve selected out of the lot by hinting it. So that I don’t have a cluttered wireframe just for example an outline, or a brightening of color on my character.

Is there a mobu function to achieve something like this through python, or am I dreaming?

Gabester, each MB version, each MB extension, probably each MB patch have changes in python. So we should have different forums for each of them to post questions? More over, why you assume, that only people using MB2009 could have idea on how to help you? Look on this from other side too, when someone will look for answer to his python question he will probably look into python section for answers, I doubt he will look in here. Do you see where I am going?

Please, ask questions in python forum. Thx.

Throw a marker over the character’s heads and toggle it’s visibility?

KXL, I do see where you are going, but after being dissapointed by simple syntax variations between versions of Mobu, and having “Seen” that there is a thread for Mobu 2009 specifically, I would personally look in the 2009 forums knowing that the answer contained within the previous forums might not be 100% correct.

Why does python get changed in versions? It’s not an efficient workflow. If we as a company construct a tool-chain built around a particular set of function calls, and those calls no longer exist in a newer version, I’d consider that a bug, where the process is hindering our pipeline because we now have to cater for those changes.

You know what, I use maya for similar automation tasks, and between version 6.0 and 2009, I haven’t had to change 1 line of text between my scripts. This is a bar that in my opinion needs to be met by industry standard packages.

Anywho, we kind of veered off the topic, the fact is, that I would check the 2009 forums first, and then check the python forum. I wouldn’t discount 1 from the other, it’s all about the order in which I would perform the searches.

Oskar, the sollution works great! Thanks. See, you didn’t need to write 1 line of code.

Gabester, yeah...it is OT..so will do it quick. I was not refering to such changes of python. I was talking about new functions exposure, new properties avaiable in classes. As for functions that no longer exist in newer version - it is true that it should not happen, but sometimes it can’t be avoided I think.

Cheers