@m_adam Thank you!

Hi Shir, thanks for following up and providing your additional info. Showing parameter in the Attribute Manager or a custom icon in the Object Manager is not such a big issue: you can start looking at Py-RoundedTube which is an ObjectData derived plugin where all such a stuff (and more) is shown. That said, the real question is instead to understand what your rig is actually doing and see if it's reasonable to implement the Xpresso functionality from a set of "primitive" functions you implement in your plugin or if would be instead easier to programmatically recreate the Xpresso rig in an XpressoTag then attached to the object generated by your plugin. Actually this assessment can't be done from here where the final functionality and the complexity of your Xpresso network is unknown. So far I do see three approches: start on your own, step-by-step, dissect the code from the example I mentioned above and try to move your steps alone outsource the task to some paid developer or call for volunteers in our very helpful PluginCafe community. I'm sorry not be more helpful but, as said in the first post, we can't deliver turn-key plugins or scripts but rather help our customer to learn from our resources. Best, Riccardo

Hi @Jvos, First of all, (no worry at all) I would like to remind you to read How to Post Questions especially the part about categories. Since your topic is related to Cinema 4D please next time create a topic within cinema 4d development. (I've moved it). Regarding your issue, pretty much all parameters in Cinema 4D are stored in a BaseContainer. A BaseContainer is a dictionary which links an ID (Int) to a Data. When you are doing Object[Something] you access the value within this BaseContainer. If you write in the console c4d.REDSHIFT_LIGHT_PHYSICAL_INTENSITY, it will print you the ID of this parameter. Then to get the value of a parameter which is stored in the object's BaseContainer, you don't have to pass a string, but the ID, which is registered with a SYMBOL NAME because it's easier to remember than an arbitrary number (In some case there is no SYMBOL equivalent for an ID). So as @mikeudin suggested the eval function is the right way to go, or you can directly store the ID in your list. attributes = [c4d.REDSHIFT_LIGHT_PHYSICAL_INTENSITY, c4d.REDSHIFT_LIGHT_PHYSICAL_EXPOSURE] Finally, there is no official C4D slack/discord or chat. Cheers, Maxime.

Hi, @Jvos it looks like your question got answered. Afterwards you deleted this thread. I'd like to ask you not to do so. This forum is all about sharing knowledge. There are no stupid questions and nothing to be ashamed about. Every answered question might help a future developer. I have moved this thread into the Cinema 4D Development category. Cheers, Andreas

Hi @cmpxchg8b and @a_block , I don't know much about matrix, but here is what I found. If the point with arrow should rotate to aim, then all the possible position of the point must lay on the sphere surface which sphere's center is the parent object. And one point and a vector can form a line in space. So the question becomes a line-sphere intersection problem. After solving the equations, we can get 2 points: original point and transformed point(s). After that, we can find the transform matrix between 2 points.