Hey Chris!, Thanks for the link. That gave me an idea. I'm on Windows 8, Maya 2015, FBXplugin 2015. FBX file imported came from 3dsMax , fbx plugin version 2010. And then tried 2014, and gave me the same errors.
Found this thanks to your link http://techartsurvival.blogspot.com.es/2014/10/laziness-and-cleanliness-and-mel-oh-my.html I wanted to avoid using PyMEL. But i think i'll finally end up using it anyway. :-D I read there is a cmds.FBXImport method created in maya.cmds. I'm trying that out... but anyway, i thought it could be some kind of conflict of names with "fbx" string. I unloaded FBX plugin, and no FBX format is allowed. That's ok. Then activated it once again, and saw on its info that it adds "File Conversions: Fbx, DAE_FBX, and others...". So FBX is no longer present, but Fbx (???)! Great, hopefully i can use it on cmds.file() like before... I wonder where FBX came from when i was working last week.. Trying to use Fbx in the cmds.file( ) And works, but the code continues executing, no matter what happens with the importer. A screen asking for settings appears, and my script fails (import is not finished,but code continues executing...O_O. Not modal prompt) Then i try to use mel.eval( "FBXImport -f " + path) <-- which is said to be an import process with no import options screen opening. But then i get this great window telling me there is an error, and the file is either corrupted or either an incorrect version. WTF!, if i import the file using maya menus, it works and imports ok. The version, maybe it's 2014 or 2010... But FBXImport doesn't have any option to tell it to ignore version. This is so funny.... Using cmds.FBXImport hopefullly helps... But there is no option for ignoring version. -- Lidia 2015-02-23 19:02 GMT+01:00 Chris Lesage <[email protected]>: > What version and OS first of all? > > I've had similar problems where my scripted FBX process suddenly changes. > > After choking through a lot of help docs and tutorials, I've been > (relatively happily) using PyMEL's mel module, as suggested in this TAO > thread: > http://tech-artists.org/forum/showthread.php?4988-Problem-doing-an-FBX-export-with-PyMEL > > Example from the thread: > pm.mel.FBXResetExport() > pm.mel.FBXExportBakeComplexAnimation(v=False) > pm.mel.FBXExportConstraints(v=False) > pm.mel.FBXExportInputConnections(v=False) > pm.mel.FBXExportUseSceneName(v=True) > pm.mel.FBXExportInAscii(v=True) > pm.mel.FBXExportSkins(v=True) > pm.mel.FBXExportShapes(v=True) > pm.mel.FBXExportCameras(v=False) > pm.mel.FBXExportLights(v=False) > pm.mel.FBXExportFileVersion(v='FBX201300') > filename = 'path_to_export_file' > pm.mel.FBXExport(s=True, f=filename) > > That is probably not your issue and it would be nice to know what > happened, but maybe it will work. > > On Mon, Feb 23, 2015 at 3:53 PM, Lidia Martinez <[email protected]> > wrote: > >> All my process was ok. I used cmds.file( path, type = "FBX", return new >> nodes.... ) >> >> Now i execute and tells me "FBX" is not a known type. ?¿¿. >> I import by hand and says its "Fbx". It was working days ago. And a >> window for the settings appears now, making all my script fail. >> >> I wonder what the hell happened from Thuesday. Is it an unexpected >> update?. did somebody entered my pc at work? (ankward). It was working, i >> imported fbx files, no prompt, FBX with uppercase worked... >> >> I read here: >> >> http://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2015/ENU/Maya/files/GUID-699CDF74-3D64-44B0-967E-7427DF800290-htm.html >> ... >> It is not recommended to use python file's command, but fbxImport from >> MEL. O_O not a "return new nodes" parameter available now... so i have to >> rewrite everything i did. >> >> Does anybody know what happened here?. >> >> -- >> Lidia >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAAB1%3D8zq1nMS_vHZ9wjhiYZ2FFejnmYhZNGsJyRq0o91q%3DqXig%40mail.gmail.com >> <https://groups.google.com/d/msgid/python_inside_maya/CAAB1%3D8zq1nMS_vHZ9wjhiYZ2FFejnmYhZNGsJyRq0o91q%3DqXig%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAHUba0%2BtwP7SFH5Nxdj_%2BVkmLQ0vSVFxSXR84SEbr2g3q7cnJg%40mail.gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/CAHUba0%2BtwP7SFH5Nxdj_%2BVkmLQ0vSVFxSXR84SEbr2g3q7cnJg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAAB1%3D8z0GRJHxU%3D0%3D2Qcv93GVpsgWrxeK8CRxRzxEmygRrj9kA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
