Re: [Maya-Python] Re: Viewport 2.0 issue with readColorBuff

2015-02-25 Thread Bay
Maya 2015. It's maya python api 2.0 though So try this: import maya.api.OpenMayaRender as apiOMR -- 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

Re: [Maya-Python] Re: Viewport 2.0 issue with readColorBuff

2015-02-25 Thread David Moulder
What version of Maya is this? renderer = apiOMR.MRenderer I don't have MRenderer in the Python API? On Tue, Feb 24, 2015 at 12:59 AM, Bay wrote: > Well after reading the documentations it appears that writecolorbuffer is > obsolete and it is advised that rendertarget should be used to obtain t

[Maya-Python] Re: Viewport 2.0 issue with readColorBuff

2015-02-23 Thread Bay
Well after reading the documentations it appears that writecolorbuffer is obsolete and it is advised that rendertarget should be used to obtain the information. This is the solution you just need to substitute the path variable with your output. def create_viewport_render(self, path):

[Maya-Python] Re: Viewport 2.0 issue with readColorBuff

2015-01-20 Thread tomp_blue
I m running into this issue with a pose library also. *cmds.ogs*Render seems to still work. I had tried getting the QWidget from PySide but this always came out garbled. TomP -- twitter.com/blue_zoo

[Maya-Python] Re: Viewport 2.0 issue with readColorBuff

2014-11-07 Thread Janos Hunyadi
Btw.I'm not sure if you can do it in python in VP 2.0. It's possible that its only implemented as C++ atm. On Tuesday, November 4, 2014 11:44:41 PM UTC+1, Bay wrote: > > Hi guys, > running into a strange issue with viewport 2.0 that I was > wondering if there's a solution to. I of