Update 2 for Dynamo for Civil3D is out - Awesome. Keep those updates coming. I’ve been itching to have an MTEXT node and now we have it.
… But unlike the TEXT node, there’s no port for Rotation?
And you can’t turn on the background mask?
Am I missing something?
Thanks
Thanks Paolo, I had a hunch that Transform might do it, came back to share how I did it and you beat me to it 
The background mask is what I was really looking forward to with MTEXT, but even without, Update 2 will streamline my user’s experience.
Wow, so the rotation works fine … but you can’t set the text height like we can with TEXT. I suppose I’ll see if transform can handle that with scaling, rather than making my users set it (or the default style) manually
Thanks Paolo, I appreciate your help. However, MText.SetHeight does not change the text height. It does the same thing as the height input port on Mtext.Create … changing the height of the text box, not the text within.
… I could spend all day listing off inconsistent and vague names and descriptions like this that I’m sure we all fall into.
… so ultimately, instead of just using some simple ports on Mtext.Create to use a rotation and an actual text height, at my insertion points, I’ve had to create the mtext at the origin, and use object.transform with coordinatesystem.scale, coordinatesystem.rotate, and coordinatesystem.translate to modify the mtext objects.
And I spent a lot of time trying to make the adjustments with the mtext created at the insertion points first and failing - probably because I don’t know enough about coordinatesystem objects, but maybe because so many of the coordinate system nodes only work relative to the Origin, not the base point of the object, or a base point that I can set.
This isn’t really a complaint or rant, I know I need to learn. This is a call for real reference material with full detailed descriptions of what the nodes and their ports actually do so that I don’t have to keep guessing.
Is it wrong to set it with .SetParameter? This discussion was helpful to see that no matter which node I used I would be laking properties, either the attachment, or rotation+textheitght.
Ultimately it was easier to create the text with the original node as the rotation AFTER placing it with the correct attachment to make the orientation work.
@gcarvalhoDF there is a node in the Civil 3D Toolkit to create MText with a rotation input, maybe that will help?
It has rotation input, but it doesn’t have attachment input. And neither of them has Background editing. Everything is working fine, I was just wondering if is it wrong to set it with the SetParameterValue blocks.
I know Python, but I still need to learn how to code with the API. Just did some basic code for sorting and calculating variables, nothing related to object editing.
Nope, not wrong…whatever works 
