Maya Station

Crash when loading scenes with displayPoints or type in mayapy

We have seen issues from customers who are attempting to load their scenes which contain type in mayapy that end up crashing.  These particular crashes seem to focus around the newer displayPoints node that are used in Maya.

A displayPoint node in Maya is a Utility Draw Node that is mainly used to display the Type pivot points in the .  Ultimately this crash tends to occur when the type tool is used as there is a UI draw call.

head over to our learning page for more details and workarounds.

 

 

How to prevent Maya writing a "requires" command for a plug-in

Do you wonder why error messages about some plug-in or other that Maya cannot find continue to appear when you load a scene? Do you wish you could force Maya to unload a plug-in when saving your scene so you can avoid having it load again with the scene file ?

The objective of this tutorial is help you understand why Maya might include a reference to a plug-in in a scene file, and how to prevent Maya from doing so.

To complete this tutorial, you will need Maya 2015 SP6 or Maya 2015 Ext1 & SP6 because this Service Pack release includes two new MEL commands : unknownPlugin and unknownNode; this tutorial demonstrates how to use both of them.

Around the Corner: a new M&E developer blog

There is a new blog in town!  Around the Corner, is a blog dedicated to
plug-in developers working with Maya, MotionBuilder, FBX and any other
technology that strikes our fancy at the moment of blogging.

This blog is authored by Cyrille Fauvel and me (Kristine Middlemiss, I am
sad to say I am departing this blog :()

To tell you a little about our selves we are 2/6’s of the Media & Entertainment worldwide team of API gurus providing technical services through the Autodesk Developer Network.

When either of us comes across some information on programming for Autodesk
technologies that we think you’ll be interested in, then you can expect it to
be posted here. That will be technical (how-to) solutions derived from
answering questions from ADN partners and from Autodesk forum users, sample
projects, white papers screencasts, conference presentation material, and other
information derived from our work. This blog is a vehicle to put lots of up to
date information in one place so you can easily find what you need to solve
your programming problems.

Enjoy!

Kristine

Free Maya API and 3ds Max SDK 2 Day Training in St Petersburg, Russia

The Autodesk Developer Network (ADN) will be hosting a free 2 day Maya API and 2 day 3ds Max SDK training sessions in St. Petersburg, Russia on May 22^nd, 2012 and May 23^rd, 2012.

This unique opportunity allows you to dive into the inner workings of our software, and come out with a strong fundamental knowledge of the architecture. You will see and understand how you can utilize and benefit from the API’s/SDK’s of these powerful software’s.

1. Maya API (Python) - registration
2. 3ds Max SDK -registration

To register and view the course schedule, please look here:

http://www.adskconsulting.com/adn/cs/api_course_sched.php

Python MDataHandle.asString() does not return the string content

When writing a custom node using Python and trying to retrieve an attribute string with the compute method, the MDataHandle.asString() method does not return the attribute string content, but a string referencing the internal Maya MString:

def compute( self, plug, data ):
  if plug != myTestNode.outputAttr:
   return maya.OpenMaya.MStatus.kUnknownParameter
  inputHandle = data.inputValue( myTestNode.myStringAttr )

  # returns something like "_18691109_p_MString"
  simpleAttrValue = inputHandle.asString()  

To retrieve the real string content th MDataHandle::asString() returns a reference to an internal Maya MString object. Because it is a reference, if the user changes the contents of the string that is immediately reflected in the datablock without having to call set(). There is no way to provide equivalent functionality in Python because, among other things, Python strings are immutable: any changes create a new string and the MString class that is available in C++ is not available in Python because it has its own string implementation which makes our not needed.

However, there is a simple workaround. If you add this code you will get the string content rather than the reference to the internal string.

stringData =inputHandle.data()
stringFn = maya.OpenMaya.MFnStringData(stringData)
stringValue = stringFn.string()
print "real stringValue:", stringValue

Working with Internal Data Using setInternalValueInContext

When writing an MPxNode which stores data internally using setInternalValueInContext that is connect to another node. Everything will work well until you save the scene and re-load the scene. It seems you have to force an update of the attribute of your node with a refresh, such as displaying the Attribute Editor.

The reason for this is the value that is maintain for an internal attribute is only used when the attribute does not have an incoming connection. If the attribute has an incoming connection then the connection determines the value of the attribute and your node has no say in the matter. To handle this, use MPxNode::connectionMade() and MPxNode::connectionBroke() to maintain a flag telling you whether the attribute is currently connected.

In Python, that would look something like this:

class myNode(maya.OpenMayaMPx.MPxNode):
         myNode.myAttr = maya.OpenMaya.MObject()

         def __init__(self):
                 self.myValue = 0.0
                 self.myAttrIsConnected = False

         def connectionMade(self, myPlug, theirPlug, iAmSrc):
                 if not iAmSrc and myPlug == myNode.myAttr:
                          self.myAttrIsConnected = True
                 return ompx.MPxNode.connectionMade(self, myPlug, theirPlug, iAmSrc)

         def connectionBroken(self, myPlug, theirPlug, iAmSrc):
                 if not iAmSrc and myPlug == myNode.myAttr:
                          self.myAttrIsConnected = False
                 return ompx.MPxNode.connectionBroken(self, myPlug, theirPlug, iAmSrc)

In the compute(), check the flag. If it's true then update the internal value from the datablock before using it:

         def compute(self, plug, block):
                 if plug == myNode.someOutputAttr:
                          if self.myAttrIsConnected:
                                   self.myValue = block.inputValue(myNode.myAttr).asFloat()

If you need the internal value outside the compute() then write yourself a helper method which gets the value from a plug when the flag is set and call that method as needed:

         def get_myValue(self):
                 if self.myAttrIsConnected:
                          plug = maya.OpenMaya.MPlug(thisMObject(), myNode.myAttr)
                          self.myValue = plug.asFloat()
                 return self.myValue

Free Autodesk Media & Entertainment API/SDK Webcast Trainings

Free Autodesk API/SDK Webcast Trainings

The Autodesk Developer Network (ADN) is offering free Maya API, 3ds Max SDK, MotionBuilder SDK and FBX SDK webcast trainings. This unique opportunity allows you to dive into the inner workings of our software, and come out with a strong fundamental knowledge of the architecture. You will see and understand how you can utilize and benefit from the API’s/SDK’s of these powerful software’s.

1. Maya API (Python)
2. MotionBuilder API (Python)
3. 3ds Max
4. FBX (C++)

To register and view the course schedule, please look here:

http://www.adskconsulting.com/adn/cs/api_course_sched.php

For specific course agenda’s go here:

http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=785271

Okay, I loaded my Plug-in, now what?

I got this great question the other day, it may seem simple however that is what is so great about the question.

Everyone thinks it's so simple that no one ever writes about it!

What do you do in Maya once you use the Plug-in Manager or the MEL command loadPlugin to load your plug-in.

Once you have loaded your plug-in, shhh, this is the part no one tells you, you still have to create your node in the scene!

To do this you can use the MEL command ‘createNode {nodename}’ so for example to create any Maya default node you could do this:

 createNode Transform;

Here we are creating a standard node that comes with Maya (there are hundreds), the name of the node matches the node name in the documentation under Nodes and Attribute Reference, which you can access from the standard help documentation that comes with Maya:

But you can also use this createNode for custom nodes that you creating using the Maya API. Let’s say you have compiled the Devkit sample ‘pnTrianglesNode’, you would do this after loading the plug-in:

 createNode pnTriangles;

One you run this command, the node is now actually in your Maya scene, and will be saved there on scene save. From here you just need to connect other nodes to this node in your scene.

Also, the other way to create nodes in the API is to use the class MDGModifier, there is a method there called createNode.

~Kristine

Global Symbol Evaluation

Are you working on Linux?

Have you ever seen a file with this *.sog extension in your plug-in directory?

Ever wonder what it is?

It is possible to force plug-ins to export their symbols by putting an additional file, with the same name as the plug-in with the extension '.sog' in the directory with the plug-in. This would cause the plug-in to be dlopened using the RTLD_GLOBAL flag.

The .sog extension is our own indication that a plug-in should be loaded with extra loader options.  The RTLD_GLOBAL flag.   Normally we don't set this flag so any functions will be known to the plug-in itself and not pollute the global name space.

Normal plug-in loading:

• pluginName.so

To load a plug-in with RTLD_GLOBAL flag included:

• pluginName.so
• pluginName.sog

The ending ‘g’ meaning global.

You need both files.  The .sog is there for existence only - can be a zero length file.

They should ensure the other plug-in that exports its functions has a .sog file to match that plug-in so it is loaded with global scope.

The presence of a .sog file will enable the plug-in symbols to be available for other plug-ins to use.

Cheers,

Kristine

Exporting Hair Geometry

If you are writing an exporter plug-in and want to add support for exporting hair geometry data (much like the mayatomr functionality). At first glance there does not seem to be any API functionality for hair other than collision solving via MHairSystem, which does not give access to the hair data. To access the hair geometry scalar data (per-hair and per-vertex data) use MFnPfxGeometry::getLineData() and then use MRenderLineArray and MRenderLine to get at the per-vertex data. For other data, you’ll have to access the attrs on hairSystem or pfxHair node directly.

To elaborate the actual hair geometry is represented in the pfxHair node (which is connected to the hairSystem node when paint effects output is used). This derives from the base class pfxGeometry which is also used for stroke and pfxToon nodes.  To get the hair geometry one can use the call  MFnPfxGeomtry::getLineData for the pfxHair node. (Note that if one used curve output instead of pfx output on the hair system, then one could simply access the set of output nurbs curves on the hair system, but as this is rather obvious I’m assuming they want the pfxHair data)

One thing worth noting is that your exporter would also potentially work (to some degree) for paint effects strokes and Maya toon lines, in addition to hair, because they all share the same base class.

~Kristine