Chris Cunningham
Chris Cunningham
having the same issue on local builds as well, was also the same issue had to edit my Podfile and changes it to explicitly target `11.1.0` instead of `~> 11.0`
yeah all of you assumptions there are correct, i will try and find time on the weekend to make it recognize mayapy2.exe properly as well as getting the connect logic...
fixed the attach script bit to be both python 2 and 3 friendly in 8621f2ad421d96dfc28b9e5d051a6c046f9e84fc the other changes will be later, since i will need to rethink a few things...
Yeah where it's hitting the issue, is currently when you try to attach, it searches for running maya instances, for each one it finds, it tries to compute the path...
could try that, if i did it would be check for that var first in maya's env then default to the old way to get that data if not defined....
am at work, so can't test on windows right now, but it looks like i can `ps eww ` on mac to get the env vars assuming i can find...
notice in that code that executablePath is private, and i have to access it via getExecutableCannonicalPath, and from my experience working with it, it i have never been able to...
There is a good chance things are not setup enough yet for some things to work during the userSetup calls. Have you tried using `evalDeferred` in your startup code. if...
any progression on getting this merged in?
unless someone else has taken it, over i was never able to get mac support fully working