Hi,
I’ve downloaded the latest builds for the KrakatoaSR and the Exporter (Jun 12, 2012), and when I try to export a scene from maya I got the following error:
KrakatoaSR_Exporter.mel line 1547: fopen: unable to open file "/Maya2KSR/SCENE/_0018.py" for mode "w". //
// Error: prt_particle_ostream::close() The output stream "/Maya2KSR/PRT//particleShape1_0018.prt via temp file: /tmp/fileXGGt44" had an error while moving the temporary file.
The temporary file "/tmp/fileXGGt44" was unable to be moved
The destination file "/Maya2KSR/PRT//particleShape1_0018.prt"
Error number: 2
Error message: No such file or directory
It’s happening in Maya 2011 & 2012, running on CentOS.
I don’t think this is permission related, since the maya project and the scene are in my home folder.
Also I would like to make a suggestion - I don’t think is too usefull to hardcode the paths of the exporter and loader scripts in the creation of the KrakatoaSR shelf, when you load the plugin.
// Shell button command:
source "[plugin_root]../Scripts/KrakatoaSR_Exporter.mel";
// Note that even though the scripts and the .so are in the same folder it doesn't work:
// Error: Line 1.107: Cannot find file "[....]../Scripts/KrakatoaSR_Exporter.mel" for source statement.
It would be much better if you just code
source "KrakatoaSR_Exporter.mel"
this way the scipt will get sourced as long as it is in a folder from the MAYA_SCRIPT_PATH. I find this the better way, since it’s always preffered to keep the stuff organized and every type of maya resource in different path (plugins, scripts, icons, etc.)
I believe this is happening because your Maya scene hasn’t yet been saved.
The exporter has a bug where it doesn’t work with Maya scenes that aren’t saved. The reason for the bug is that the exporter uses relative paths to the Maya scene file name. Thanks for the bug report! I hope to fix this for the next release.
Well, saving the scene fixed part of the problem. Now the next one:
Since on Linux the /tmp folder is actually located in a separate mount point /tmp (tmpfs), Krakatoa’s Exporter can’t deal with that:
// Error: prt_particle_ostream::close() The output stream "/home/niki/Desktop/KTMP/Maya2KSR/PRT//nParticleShape1_0077.prt via temp file: /tmp/fileoGOLhs" had an error while moving the temporary file.
The temporary file "/tmp/fileoGOLhs" was unable to be moved
The destination file "/home/niki/Desktop/KTMP/Maya2KSR/PRT//nParticleShape1_0077.prt"
Error number: 18
Error message: Invalid cross-device link
//
If I save my scene directly in the /tmp/ folder the export is fine. I also tried changing the environment vars for TMP and TMPDIR in Maya, but it seems the exporter doesn’t take them into account.
Is there any way to tell Krakatoa where to dump the temps, because now it looks like the temp path is hardcoded somewhere?
Ah, this is something I’ve never tested on Linux. Thank you for reporting the problem. I’ll take a look at it.
Hi
Got same error (cannot move /tmp/file****) when project located on NFS drive (like /hosts/server/PROJECTS/) and /tmp located on root drive
Seems error msg “Error message: Invalid cross-device link” appears when KMY trying to make link file (ln /tmp/file*** /dectdir/destfile ) over 2 different partitions
I forgot to mention this earlier, but this problem in the last build posted. Thanks for the bug report!