Message 1 of 1
Open Maya - Crash During File Load

Not applicable
08-22-2012
03:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi All,
I'm trying to debug a stand-alone application written and compiled in VC++ 2010 for 32-bit Maya 2012 running on Windows 7 x64. I can boil down my problem to these lines ("fileName" is a hard-coded const char*):
^^ problem on last line
The library initializes and clears with newFile() fine, but when it comes time for MFileIO::open(), the status is never returned because an exception along the following lines gets thrown:
When I turn on error logging beforehand, the log spits out a few copies of the following message:
I can't make sense of these rather vague-sounding messages. I've verified the file path is correct; I even tried directly copying and executing the MEL "file" command which shows up in the script window if I open the file through the GUI directly.
Has anyone else experienced an error like this before, or have any guesses as to what might be wrong?
Thanks,
-Nick
I'm trying to debug a stand-alone application written and compiled in VC++ 2010 for 32-bit Maya 2012 running on Windows 7 x64. I can boil down my problem to these lines ("fileName" is a hard-coded const char*):
MStatus status = MLibrary::initialize (argv,true);
CHECK_MSTATUS( status );
status = MFileIO::newFile(true)
CHECK_MSTATUS( status );
status = MFileIO::open(fileName, "mayaAscii", true);
^^ problem on last line
The library initializes and clears with newFile() fine, but when it comes time for MFileIO::open(), the status is never returned because an exception along the following lines gets thrown:
0xC0000005: Access violation writing location 0x122be180
When I turn on error logging beforehand, the log spits out a few copies of the following message:
Object is incompatible with this method
Method: setIndexMatters
Class: MFnAttribute
I can't make sense of these rather vague-sounding messages. I've verified the file path is correct; I even tried directly copying and executing the MEL "file" command which shows up in the script window if I open the file through the GUI directly.
Has anyone else experienced an error like this before, or have any guesses as to what might be wrong?
Thanks,
-Nick