-
Notifications
You must be signed in to change notification settings - Fork 53
2019 OSX builds - crash during build from selection #29
Comments
@liorbenhorin Thanks for sharing this info. EDIT: Oh I see this in the log: |
I had the same experience on macOS 10.13.6 Maya 2019 |
Ops! I completely misunderstood the issue :( (I should not read this things in a rush, sorry) The problem is not at plugins compile time. but later at guide build time. correct? |
@miquelcampos correct. Same happens for me:
|
@liorbenhorin thanks for the confirmation |
I haven't had any issues with Maya 2019 proxy channels on macOS. |
This is going to be hard to debug for me since I don't have Maya 2019 in OSX env :( @liorbenhorin @jollypixel can you help with this? Thanks |
I will definitely take a look as soon as I have a couple of hours |
Thanks! |
@miquelcampos Yes, of course :) |
thanks! |
It doesn't crush when this is commented out in arm_2jnt_01/init.py |
It works with "Use Classic Channel Names" off and one object instead of a list |
Just run this on five objects (the last one had an attribute "test" and works fine. import pymel.core as pm |
Hello! - hope this is the correct place for this :)
I just finished building the plug-ins for Maya 2019 on OSX.
Description
When I import the template biped guide, and 'build from selection' - Maya crashes mid-way into the build.
What is working:
p.s
Build of the plug-ins seem to work perfect on 2018 OSX
To Reproduce
The error does not say much, not the standard Maya fatal error:
Additional information
built plugins: https://www.dropbox.com/s/imdxbs1s22u1ior/2019-osx-plug-ins.zip?dl=0
scons build log: https://www.dropbox.com/s/glonggxthhfuw3y/scons-build-log.txt?dl=0
Osx 10.14
Maya 2019
SCons 3.0.1 installed with brew
EDIT:
Further testing shows that the crash is related to the arm_2_jnt01 and leg_2_jnt01.
When these modules are deleted from the template, the build completes successfully.
Investigation continues...
EDIT 2:
Building with 'objects' mode works, any mode above will crash.
So far this actually looks like a 2019 OSX issue, and not related to the plug-ins themselves, but this is just a gut feeling.
The text was updated successfully, but these errors were encountered: