synColor
Oh the memories …of segfault.
Anyway, this is something I’ve wanted to know for a while; is it possible
to switch to “legacy” from commandline somehow, prior to launching Maya or
maya.standalone? (sorry for possibly derailing the thread)
On Mon, Sep 19, 2016 at 7:42 AM Geordie Martine
Yes you CAN subprocess without viewport 2.0. I've been having the problem
as well at work.
you have to swap your preferences back to Legacy. then when
```maya.standalone.initialize()``` runs it won't search for synchronized
color settings. which is where this devil is originating from.
Legacy vie
Next piece of the puzzle, no errors this time, and a successfully created
Quicktime file.
$ yum install mesa-libGL-devel
$ export LIBQUICKTIME_PLUGIN_DIR=/usr/autodesk/maya/lib
$ mayapy -c "from maya import standalone, cmds; \
standalone.initialize(); \
cmds.playblast(filename='/root/workspa
> xvfb
Ah, that was clever!
Following this topic with interest.
--
You received this message because you are subscribed to the Google Groups
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to python_inside_maya+unsu
Sorry, that yum command should have been:
$ yum install xorg-x11-server-Xvfb
On 17 September 2016 at 17:12, Marcus Ottosson
wrote:
> Got this somewhat further, with newfound knowledge of Xvfb.
>
> $ yum install xorg-x11-server-Xorg
> $ Xvfb :99 -screen 0 1024x768x16 2>/dev/null &
> $ mayapy
Got this somewhat further, with newfound knowledge of Xvfb.
$ yum install xorg-x11-server-Xorg
$ Xvfb :99 -screen 0 1024x768x16 2>/dev/null &
$ mayapy -c "from maya import standalone, cmds; \
standalone.initialize(); \
cmds.playblast(format='image')"
In a nutshell how it works is that as fa
On Sat, Feb 27, 2016 at 11:30 PM Marcus Ottosson
wrote:
> No I did not. Doing it now, it simply says "No stack". :(
>
Maybe there was an error when gdb started up, with it not being able to
load the binary. Oh well.
>
> On 27 February 2016 at 09:42, Justin Israel
> wrote:
>
>> Did you run the
No I did not. Doing it now, it simply says "No stack". :(
On 27 February 2016 at 09:42, Justin Israel wrote:
> Did you run the 'bt' command after it seg faulted and gave you back the
> gdb prompt? The stack info may not even be helpful. I just wondered if it
> would highlight what specifically i
Did you run the 'bt' command after it seg faulted and gave you back the gdb
prompt? The stack info may not even be helpful. I just wondered if it would
highlight what specifically it was trying to do when it crashed.
On Sat, 27 Feb 2016 9:26 PM Marcus Ottosson wrote:
> I’d like to think it’s pos
I’d like to think it’s possible with mesa drivers or the like.
Grabbing the framebuffer was an interesting tip, but unfortunately did not
bear any fruit.
[root@9378ed216bc0 ~]# mayapy
Python 2.6.4 (r264:75706, Jul 27 2011, 17:36:42)
[GCC 4.1.2] on linux2
Type "help", "copyright", "credits" or "li
Yea, I wonder if it is even possible to run this on a Travis CI, unless you
can be sure there is a graphics card available on the runner and that your
environment has graphic drivers installed.
On Sat, Feb 27, 2016 at 12:37 AM Nicolas Chaverou <
nicolas.chave...@golaem.com> wrote:
> I'd have bet
I'd have bet on the graphics drivers / opengl.
Else if your Maya viewport is active, you may try to dump the frame buffer
to images and run a post process to assemble them as a video:
http://nathanhorne.com/python-api-grab-frame-buffer-to-image/
---
[image: Nicolas Chaverou - Golaem Crowd Product
Thanks Justin.
Passing the display did not make a difference, possibly because the docker
image is being run in yet another virtual machine that also does not have a
window manager installed. The goal is to run this on something like Travis.
The gdb route seems promising. I just can't wrap my hea
And also, you might get a better idea of what Maya was doing when it
crashed if you debug it with gdb?
gdb -ex run --args /bin/bash `which mayapy`
...
>>> # do stuff
[crash]
(gdb) bt
[back track follow]
On Fri, Feb 26, 2016 at 1:26 PM Justin Israel
wrote:
> Maybe you are missing video drivers
Maybe you are missing video drivers in the bare bones image? Or maybe you
need to actually pass the display to the docker container:
http://fabiorehm.com/blog/2014/09/11/running-gui-apps-with-docker/
docker run -ti --rm -e DISPLAY=$DISPLAY -v
/tmp/.X11-unix:/tmp/.X11-unix mottosso/maya:2013sp1
15 matches
Mail list logo
