Hello Brian,

There have been some developements.  Max will now automatically load the plug-in if it sees it in the install paths.  With that in mind, you don’t need so say “pluginManager.loadClass FBXEXP”.

You only have to state the following. ( Notice that in the second line of code there is a #noPrompt, this has to be there to avoid the Preferences UI popping up for every shape you export.)

FBXExporterSetParam “Animation” true
exportFile (SavePath) #noPrompt selectedOnly:True using:FBXEXP

hope this helps
Cheers!
Carlos

Hi again brian1,

Okay, let’s try something else.  The following steps should eliminate the plug-in as the problem.

First, let’s double check that the plug-in is loaded correctly (you may know how to do this already, but for argument’s sake, I’m describing the steps just to make sure we’re on the same page)

1) Start Max
2) Go to Customize>Plug-in Manager
3) Look for the fbxmax.dlu entry
4) Make the loaded status is green

If the status is not green:

5) Manually load the plug-in
6) Execute FBXExporterGetParam “Animation”

At this point you will get either a True or False result.  If you don’t, please let us know what version of the plug-in you are using.  If you do get a True or False result, this is proof that the plug-in is not the problem.  In this case, it would seem that your batch process is not loading the plug-in before you call the exposed functions even though Max should have loaded the plug-in automatically.

If this is the case, we’d have to refer the problem to the Max team to see why this is happening.  Let’s see what your results are and we’ll go from there.

Cheers!
Carlos

I suggest you post this issue in the Max forum, explaining your problem telling them about the tests that we’ve run here.  Since we now know the plug-in is not the problem, they may have a better idea on where to start when looking into Max.

Regards,
Carlos