Can't open file in mayapy in Maya2020

Can't open file in mayapy in Maya2020

copenhagenbombay
Explorer Explorer
1,558 Views
0 Replies
Message 1 of 1

Can't open file in mayapy in Maya2020

copenhagenbombay
Explorer
Explorer

Hi good folk!

I'm having a bit on an issue, and I'm trying to figure out if I'm the doofus here and missing something obvious.

I'm trying to run some python command through a GUI less maya, to tweak a file, by using:

mayapy.exe -c "import maya.standalone;maya.standalone.initialize('python');import maya.cmds as cmds;cmds.file('my_file_here', open=True,f=True)"

 (+my tweak commands afterwards).

 

But it won't open my scene, and I get a crash report. The read out from cmdline is like this:

[2020/Mar/27|13:42:58] V-Ray: V-Ray Next for Maya, update 2.1 version 4.30.01 from Jan 21 2020, 20:37:48
[2020/Mar/27|13:42:58] V-Ray: V-Ray core version is 4.30.01
Initializing V-Ray for Maya

[VMAYA PT] Loaded and initialized C:\Program Files\Autodesk\Maya2020\vray/shaders/ptbercon_special.dll
[VMAYA PT] Loaded and initialized C:\Program Files\Autodesk\Maya2020\vray/shaders/ptuvwgen_bercon.dll
[2020/Mar/27|13:42:59] V-Ray: Loading plugins from "C:\Program Files\Autodesk\Maya2020\vray/vrayplugins/vray_*.dll"
[2020/Mar/27|13:43:00] V-Ray: 83 plugin(s) loaded successfully
[2020/Mar/27|13:43:00] V-Ray: Finished loading plugins.
Warning: V-Ray: Could not get the renderer
Warning: V-Ray VolumeGrid: Loading shaders failed - no <*.txt> files in .
V-Ray VolumeGrid: loading C:\Program Files\Autodesk\Maya2020\vray/scripts/VRayVolumeGridInit.mel...
Warning: file: C:\Users\chris\OneDrive\Documents\maya\2020\prefs\filePathEditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'aiImage.filename' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\chris\OneDrive\Documents\maya\2020\prefs\filePathEditorRegistryPrefs.mel line 5: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\chris\OneDrive\Documents\maya\2020\prefs\filePathEditorRegistryPrefs.mel line 6: filePathEditor: Attribute 'aiStandIn.dso' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\chris\OneDrive\Documents\maya\2020\prefs\filePathEditorRegistryPrefs.mel line 7: filePathEditor: Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'.
V-Ray VolumeGrid: OK.
pymel.core : INFO : Updating pymel with pre-loaded plugins: vrayvolumegrid, stereoCamera, vrayformaya, cacheEvaluator, renderSetup
Warning: file: C:/Program Files/Autodesk/Maya2020/scripts/startup/initialStartup.mel line 179: Y-axis is already the Up-axis
AbcExport v1.0 using Alembic 1.7.5 (built Feb 6 2018 18:28:08)
Initialized VP2.0 renderer {
Version : 2016.11.53.12. Feature Level 5.
Adapter : GeForce GTX 1080/PCIe/SSE2
Vendor ID: 4318. Device ID : 7040
Driver : .
API : OpenGL V.4.6.
Max texture size : 16384 * 16384.
Max tex coords : 32
Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
Shader compiler profile : (Best card profile)
Active stereo support available : 0
GPU Memory Limit : 8192 MB.
CPU Memory Limit: 31071.4 MB.
MultiDraw consolidation: enabled
}
OpenCL evaluator is attempting to initialize OpenCL.
Detected 1 OpenCL Platforms:
0: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 10.2.141.
Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.
OpenCL evaluator is unable to find a GPU device that can share VBOs with OpenGL.
AbcImport v1.0 using Alembic 1.7.5 (built Feb 6 2018 18:28:08)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node vrayMultiProjection (id: 1115335/0x001104C7)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayCurvature (id: 1115347/0x001104D3)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayTriplanar (id: 1115362/0x001104E2)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayPointParticleMtl (id: 1115353/0x001104D9)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayStochasticFlakesMtl (id: 1115359/0x001104DF)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayAlSurface (id: 1115350/0x001104D6)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayHairNextMtl (id: 1115320/0x001104B8)
[2020/Mar/27|13:43:07] V-Ray: Registered dynamic node VRayBerconNoise (id: 1115370/0x001104EA)
info: MDL SDK 2018.1, build 307800.1800, 09 Aug 2018, nt-x86-64
info: Loaded library "C:\Program Files\Autodesk\Maya2020\bin\libvrayfreeimage.dll".
Warning: Python callback failed
Warning: line 1: filePathEditor: Attribute 'aiStandIn.dso' and label 'Standin' have been saved already.
Warning: line 1: filePathEditor: Attribute 'aiVolume.filename' and label 'VDB' have been saved already.
00:00:00 769MB WARNING | [mtoa] [<built-in>] [node aov_write_vector] Assigning temporary node id 1138176 to associated Maya type name aiAovWriteVector.
Warning: line 1: filePathEditor: Attribute 'aiImage.filename' and label 'Image' have been saved already.
Warning: line 1: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' and label 'IES' have been saved already.
Successfully imported python module 'arnold'
Successfully imported python module 'mtoa'
Warning: };
Warning: "C:/Program Files/Autodesk/Maya2020/scripts/others/imageFormats.mel" line 65.2 : Global variable is already initialized; this occurrence is ignored.
Successfully registered renderer 'arnold'
Stack trace:
Foundation.dll!Tstring::compare
Foundation.dll!Tstring::operator==
Foundation.dll!TstringArray::find
Shared.dll!TsceneFile::addFileInfo
Shared.dll!TfileInfoCmd::doCommand
CommandEngine.dll!Tjournal::operator=
CommandEngine.dll!TmelVariableList::`default constructor closure'
CommandEngine.dll!TmelVariableList::`default constructor closure'
CommandEngine.dll!SophiaExecutable::evaluate
CommandEngine.dll!TcommandEngine::executeCommand
Shared.dll!TmayaAccessor::execute
Translators.dll!TmayaAsciiAccessor::reader
Shared.dll!TfileTranslator::read
Shared.dll!TglobalTranslator::doReadFile
Shared.dll!TfileUtil::readFile
Shared.dll!TsceneOperator::openFile
Shared.dll!TfileCmd::handleFileOpenFlag
Shared.dll!TfileCmd::handleFlags
Shared.dll!TfileCmd::handleFlags
Shared.dll!TfileCmd::doCommand
CommandEngine.dll!TpythonInterpreter::dispatchMayaCommand
python27.dll!PyCFunction_Call
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_EvalCodeEx
python27.dll!PyRun_FileExFlags
python27.dll!PyRun_StringFlags
python27.dll!PyRun_SimpleStringFlags
python27.dll!Py_Main
mayapy.exe!<7FF63C2E2A3C>
mayapy.exe!<7FF63C2E2FA0>
KERNEL32.DLL!BaseThreadInitThunk
ntdll.dll!RtlUserThreadStart
00007FFD0C9CF600[WARNING] V-Ray for Maya may not have been uninitialized properly!

Sorry for the long chunk of print out, but at least here you can see the full picture.

If I remove vray/arnold/bifrost from the plugin list, and save a new file (to get as "clean" a scene as possible), then I can open it with mayapy, without a problem.
But if I then open that clean file, and open the hypershader in that file, and save it. Then I get this error when trying to open it from mayapy:

Warning: file: C:/Users/chris/OneDrive/Documents/maya/projects/930382_Kiwi&Strit_2/Production/Assets/3D_Assets/Test.ma line 138: Unrecognized node type 'nodeGraphEditorInfo'; preserving node information during this session.
Warning: Errors have occurred while reading this scene that may result in data loss.
File read in  0.017 seconds.

Which seems to say that it can't find a maya type node 😕 ? So even just maya without plugins are having issues with mayapy.

I'm a bit of a loss here. I've used mayapy on a previous project with no problems.

It should be said that I am working on my private workstation at the moment, and started using maya2020, which both are new variables compared to last time I used mayapy.

 

I hope anyone has an idea of why this could be happening? Or how to get around it?

best regards

Christian

0 Likes
1,559 Views
0 Replies
Replies (0)