date:20151112

Re: [Maya-Python] script for measuring framerates?

2015-11-12 Thread Marcus Ottosson

Here is one way of doing it.

import timefrom maya import OpenMaya as om

time.__previous = time.time()def callback(*args, **kwargs):
current = time.time()
fps = 1 / (current - time.__previous)
time.__previous = current
print("%.1f" % fps)  # Show only 1 decimal

job = om.MDGMessage.addTimeChangeCallback(callback, 'transform')

The additions to the time module were to maintain a reference to the
previous_time variable, which apparently gets lost in a callback like this.

Output.

28.622.227.822.228.622.727.023.328.622.228.6

Alternatively, you could also use a script

node, or an expression. Both of which are capable of listening in on
timeChanged.


On 12 November 2015 at 13:43, Ravi Jagannadhan  wrote:

> Sorry, playback in Maya.
>
> "There are no dumb questions" - Carl Sagan.
>
> On Nov 12, 2015, at 00:10, Marcus Ottosson  wrote:
>
> Frame rates of what?
>
> On 12 November 2015 at 04:51, Ravi Jagannadhan  wrote:
>
>> Hi all, does anyone have any scripts handy for measuring frame rates (one
>> that's not in the GUI)?
>>
>> Thank you for your time,
>> Ravi
>> --
>> Where we have strong emotions, we're liable to fool ourselves - Carl
>> Sagan.
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/python_inside_maya/CADHeb2Z8NXCQVc79PODDY80qj6Szp27NN%2BhZ_8%3Dt0SYiv1xBLw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> *Marcus Ottosson*
> konstrukt...@gmail.com
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAaAJ6G1teCW%3D8gbMnrmEUqE25zPGfG_ZWbRV%2B2muHdNA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/2BDEC120-2AB2-4625-BE4B-9BC342AFE10A%40gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Marcus Ottosson*
konstrukt...@gmail.com

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODHxumN0zfqCin_n1C185z0rNXpkO4mUvV_A6tr6v4rMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] Unable to get UI to work

2015-11-12 Thread Justin Israel

I tried to give this a test... but I am seeing a problem in the UI file. It
seems like formLayout_3 object is trying to use API calls from both the
QFormLayout, and a QGridLayout? I get errors about QFormLayout not having
some of the addLayout() calls it is trying to do. Also, I would think that
after you had fixed those PySide vs PyQt4 mismatches...you would have
gotten different errors. Is that not the case?


On Fri, Nov 13, 2015 at 7:40 PM yann19  wrote:

> Thanks for getting back. I tried correcting the imports, however it is
> still not working, unfortunately.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/a3edc895-cd17-417c-b4aa-3baf38793e73%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2w_-qepsJ4G7uHO0-xJbEKABAsEdviBYuo_mpkNTw_%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] Unable to get UI to work

2015-11-12 Thread yann19

Thanks for getting back. I tried correcting the imports, however it is 
still not working, unfortunately.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/a3edc895-cd17-417c-b4aa-3baf38793e73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] pymel crashing maya.standalone

2015-11-12 Thread Robert White

So I've been running into this a lot with 2016. 

The fix I've been using is:
def crash_fix():
import maya.cmds as cmds
try:
cmds.quit()
except AttributeError:
pass
atexit.register(crash_fix)

I usually throw that in either userSetup.py or sitecustomize.py, mostly so 
I don't need to think about it.

>From what I remember when I tried to really dig into this, during shutdown 
maya is trying to run maya.app.finalize, but by the time it tries to run, 
the system seems to have unloaded whatever libraries that function is 
depending on. 



On Thursday, November 12, 2015 at 8:09:08 PM UTC-6, elrond79 wrote:
>
> Hmm... well, not sure I know exactly what's going on, because I can't 
> reproduce your issue on my linux box, but we've seen some similar stuff 
> before - basically, issues where when using 
> mayapy + maya.standalone.initialize(), maya fails to clean up properly on 
> exit, and segfaults.  It's an issue we've reported to autodesk before, 
> since it messes up the return code, but I don't think it's high on their 
> priority list to fix.
>
> A few things to try:
>
>- instead of importing pymel, import maya.cmds, and do something that 
>will trigger actual loading of some of the commands / libraries (maya.cmds 
>uses some fancy delayed loading stuff), and populate the scene, and see if 
>it still crashes on exit - ie:
>   - import maya.cmds
>   - maya.cmds.polyCube()
>- add these lines to your script:
>   - import pymel.internal.startup
>   - pymel.internal.startup.fixMayapy2011SegFault()  # we first 
>   encountered the problem in maya 2011, but it still happens as of 2015 
> at 
>   least...
>
> Even if the first non-pymel test doesn't trigger the crash, my guess is 
> it's still this same issue - it just may be a different library that 
> triggers the issue (libOpenMayaFX, or OpenMayaRender, etc).  Pymel may 
> import some of these to do some basic inspection stuff, which is why you 
> see the crash on import of pymel.
>
> Last thing you can try doing - instead of doing an explicit 
> maya.standalone.initialize(), simply import pymel.core.  This will trigger 
> maya.standalone.initialize() if it hasn't been done already, and also tries 
> to run a startup sequence that more closely mirrors that of a normal gui 
> maya session - for instance, come to think of it, I think it runs 
> pluginPrefs.mel (which maya.standalone doesn't do) - so it could be a 
> plugin that's causing problems. You can test that by executing that mel 
> script yourself...
>
> On Fri, Nov 13, 2015 at 11:11 AM Chad Vernon  > wrote:
>
>> Anyone with experience using pymel and maya.standalone experience any 
>> Fatal Errors when the process ends?  I don't have any experience with pymel 
>> and am looking into running a setup in standalone mode.
>>
>> # runtests.py
>> import maya.standalone
>> print 'initialize maya'
>> maya.standalone.initialize(name='python')
>> print 'done initialize maya'
>> import pymel.core as pm
>> print 'done import pymel'
>> # pm.i_hate_you()
>>
>> I've cleared my prefs, Maya.env, MAYA_SCRIPT_PATH, MAYA_MODULE_PATH, and 
>> PYTHONPATH variables to make sure there were no conflicts.  This is what 
>> happens:
>>
>> C:\Users\cvernon\Documents\Development>"C:\Program 
>> Files\Autodesk\Maya2015\bin\mayapy.exe" runtests.py
>> initialize maya
>> done initialize maya
>> pymel.internal.startup : DEBUG : startup.mayaInit: called
>> pymel.internal.startup : DEBUG : startup.mayaInit: maya already started - 
>> exiting
>> pymel.internal.factories : DEBUG : Loading api cache...
>> pymel.internal.startup : DEBUG : Loading the API cache from u'C:\\Program 
>> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApi2015.zip'
>> pymel.internal.startup : DEBUG : Loading the API-MEL bridge from 
>> 'C:\\Program 
>> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApiMelBridge.zip'
>> pymel.internal.factories : DEBUG : Initialized API Cache in in 0.22 sec
>> pymel.internal.factories : DEBUG : Loading cmd cache...
>> pymel.internal.startup : DEBUG : Loading the list of Maya commands from 
>> u'C:\\Program 
>> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaCmdsList2015.zip'
>> pymel.internal.factories : DEBUG : Initialized Cmd Cache in in 0.13 sec
>> pymel.core.uitypes : DEBUG : could not determine node type for AETemplate
>> pymel.internal.factories : DEBUG : MFnDagNode.model is deprecated
>> pymel.core : DEBUG : Adding pluginLoaded callback
>> pymel.core : DEBUG : Adding pluginUnloaded callback
>> pymel.internal.startup : DEBUG : finalizing
>> pymel.internal.startup : DEBUG : initMEL
>> pymel.internal.startup : DEBUG : running: createPreferencesOptVars.mel
>> pymel.internal.startup : DEBUG : running: createGlobalOptVars.mel
>> pymel.internal.startup : DEBUG : running: 
>> C:/Users/cvernon/Documents/maya\2015-x64\prefs\userPrefs.mel
>> pymel.internal.startup : DEBUG : running: initi

Re: [Maya-Python] Unable to get UI to work

2015-11-12 Thread Justin Israel

So did that fix it for you? If not, I was going to try out your code, with
the imports corrected.

On Thu, Nov 12, 2015 at 5:51 PM Justin Israel 
wrote:

> I still haven't tested it yet (need to find a moment), but right off the
> bat I can see you are mixing PySide and PyQt4 in your import statements.
> Fix that and give it a shot.
>
> On Thu, Nov 12, 2015 at 5:15 PM yann19  wrote:
>
>> Here you go, very much appreciated for the help
>>
>> Main :
>> https://gist.githubusercontent.com/anonymous/a3a001275688df939c41/raw/c98e00e3b50a07a867eb7569e830a765478aaf11/gistfile1.txt
>> UI :
>> https://gist.githubusercontent.com/anonymous/d2c1277bd67c779b92aa/raw/5c21ed9ac4f8fb940fe0ddf10783a2e62be6f739/gistfile1.txt
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/python_inside_maya/4f81361d-3c73-42d8-a6ba-8b347b13940b%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0EAhj5wp1rAeLPrShnWohvj1x55JuRrvOEs_dCObMsXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] pymel crashing maya.standalone

2015-11-12 Thread Paul Molodowitch

On Fri, Nov 13, 2015 at 12:10 PM Justin Israel 
wrote:

> Is it possible to use GDB to figure out what exactly is crashing? I don't
> use PyMEL either, but does PyMEL have any compiled bits that are
> conflicting with that version of Maya (or maybe its all pure py)?
>

There's nothing compiled, it's all pure python. It does have some cached
data stores that it reads (which contain metadata about all the various
commands), but that's it.

> Maybe it has installed atexit hooks and is hitting a bad reference to
> something at shutdown. If all else fails and you simply need to work around
> it... you could use  "os._exit(0)" to do a hard exit that bypasses pythons
> atexit hooks.
>

By default, pymel doesn't install any atexit hooks.  The
fixMayapy2011SegFault()
workaround installs one, which basically just calls os._exit() as you
suggested (except with some extra logic to attempt to return a meaningful
exit code).

- Paul

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAAssL7ZW-T7r%2BKb%2BXMKC-Pi%2Bqz6rSh7JGFLtGNidkX9QEH-hkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] pymel crashing maya.standalone

2015-11-12 Thread Paul Molodowitch

Hmm... well, not sure I know exactly what's going on, because I can't
reproduce your issue on my linux box, but we've seen some similar stuff
before - basically, issues where when using
mayapy + maya.standalone.initialize(), maya fails to clean up properly on
exit, and segfaults.  It's an issue we've reported to autodesk before,
since it messes up the return code, but I don't think it's high on their
priority list to fix.

A few things to try:

   - instead of importing pymel, import maya.cmds, and do something that
   will trigger actual loading of some of the commands / libraries (maya.cmds
   uses some fancy delayed loading stuff), and populate the scene, and see if
   it still crashes on exit - ie:
  - import maya.cmds
  - maya.cmds.polyCube()
   - add these lines to your script:
  - import pymel.internal.startup
  - pymel.internal.startup.fixMayapy2011SegFault()  # we first
  encountered the problem in maya 2011, but it still happens as of 2015 at
  least...

Even if the first non-pymel test doesn't trigger the crash, my guess is
it's still this same issue - it just may be a different library that
triggers the issue (libOpenMayaFX, or OpenMayaRender, etc).  Pymel may
import some of these to do some basic inspection stuff, which is why you
see the crash on import of pymel.

Last thing you can try doing - instead of doing an explicit
maya.standalone.initialize(), simply import pymel.core.  This will trigger
maya.standalone.initialize() if it hasn't been done already, and also tries
to run a startup sequence that more closely mirrors that of a normal gui
maya session - for instance, come to think of it, I think it runs
pluginPrefs.mel (which maya.standalone doesn't do) - so it could be a
plugin that's causing problems. You can test that by executing that mel
script yourself...

On Fri, Nov 13, 2015 at 11:11 AM Chad Vernon  wrote:

> Anyone with experience using pymel and maya.standalone experience any
> Fatal Errors when the process ends?  I don't have any experience with pymel
> and am looking into running a setup in standalone mode.
>
> # runtests.py
> import maya.standalone
> print 'initialize maya'
> maya.standalone.initialize(name='python')
> print 'done initialize maya'
> import pymel.core as pm
> print 'done import pymel'
> # pm.i_hate_you()
>
> I've cleared my prefs, Maya.env, MAYA_SCRIPT_PATH, MAYA_MODULE_PATH, and
> PYTHONPATH variables to make sure there were no conflicts.  This is what
> happens:
>
> C:\Users\cvernon\Documents\Development>"C:\Program
> Files\Autodesk\Maya2015\bin\mayapy.exe" runtests.py
> initialize maya
> done initialize maya
> pymel.internal.startup : DEBUG : startup.mayaInit: called
> pymel.internal.startup : DEBUG : startup.mayaInit: maya already started -
> exiting
> pymel.internal.factories : DEBUG : Loading api cache...
> pymel.internal.startup : DEBUG : Loading the API cache from u'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApi2015.zip'
> pymel.internal.startup : DEBUG : Loading the API-MEL bridge from
> 'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApiMelBridge.zip'
> pymel.internal.factories : DEBUG : Initialized API Cache in in 0.22 sec
> pymel.internal.factories : DEBUG : Loading cmd cache...
> pymel.internal.startup : DEBUG : Loading the list of Maya commands from
> u'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaCmdsList2015.zip'
> pymel.internal.factories : DEBUG : Initialized Cmd Cache in in 0.13 sec
> pymel.core.uitypes : DEBUG : could not determine node type for AETemplate
> pymel.internal.factories : DEBUG : MFnDagNode.model is deprecated
> pymel.core : DEBUG : Adding pluginLoaded callback
> pymel.core : DEBUG : Adding pluginUnloaded callback
> pymel.internal.startup : DEBUG : finalizing
> pymel.internal.startup : DEBUG : initMEL
> pymel.internal.startup : DEBUG : running: createPreferencesOptVars.mel
> pymel.internal.startup : DEBUG : running: createGlobalOptVars.mel
> pymel.internal.startup : DEBUG : running:
> C:/Users/cvernon/Documents/maya\2015-x64\prefs\userPrefs.mel
> pymel.internal.startup : DEBUG : running: initialStartup.mel
> Warning: file: C:/Program
> Files/Autodesk/Maya2015/scripts/startup/initialStartup.mel line 195: Y-axis
> is already the Up-axis
> pymel.internal.startup : DEBUG : running: initialPlugins.mel
> pymel.core : DEBUG : Plugin loaded: modelingToolkitExt
> pymel.core : DEBUG : Plugin loaded: modelingToolkit
> pymel.core : DEBUG : Plugin loaded: dx11Shader
> pymel.core : DEBUG : Adding command: dx11Shader
> pymel.core : DEBUG : Running plugin-loaded nodes callback
> pymel.core : DEBUG : Adding node: dx11Shader
> pymel.core : DEBUG : Adding node: coneAngleToHotspotConverter
> pymel.internal.startup : DEBUG : running: namedCommandSetup.mel
> pymel.internal.startup : DEBUG : running:
> C:/Users/cvernon/Documents/maya\2015-x64\prefs\userNamedCommands.mel
> pymel.internal.startup : DEBUG

Re: [Maya-Python] pymel crashing maya.standalone

2015-11-12 Thread Justin Israel

Is it possible to use GDB to figure out what exactly is crashing? I don't
use PyMEL either, but does PyMEL have any compiled bits that are
conflicting with that version of Maya (or maybe its all pure py)? Maybe it
has installed atexit hooks and is hitting a bad reference to something at
shutdown. If all else fails and you simply need to work around it... you
could use  "os._exit(0)" to do a hard exit that bypasses pythons atexit
hooks.


On Fri, Nov 13, 2015 at 1:11 PM Chad Vernon  wrote:

> Anyone with experience using pymel and maya.standalone experience any
> Fatal Errors when the process ends?  I don't have any experience with pymel
> and am looking into running a setup in standalone mode.
>
> # runtests.py
> import maya.standalone
> print 'initialize maya'
> maya.standalone.initialize(name='python')
> print 'done initialize maya'
> import pymel.core as pm
> print 'done import pymel'
> # pm.i_hate_you()
>
> I've cleared my prefs, Maya.env, MAYA_SCRIPT_PATH, MAYA_MODULE_PATH, and
> PYTHONPATH variables to make sure there were no conflicts.  This is what
> happens:
>
> C:\Users\cvernon\Documents\Development>"C:\Program
> Files\Autodesk\Maya2015\bin\mayapy.exe" runtests.py
> initialize maya
> done initialize maya
> pymel.internal.startup : DEBUG : startup.mayaInit: called
> pymel.internal.startup : DEBUG : startup.mayaInit: maya already started -
> exiting
> pymel.internal.factories : DEBUG : Loading api cache...
> pymel.internal.startup : DEBUG : Loading the API cache from u'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApi2015.zip'
> pymel.internal.startup : DEBUG : Loading the API-MEL bridge from
> 'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApiMelBridge.zip'
> pymel.internal.factories : DEBUG : Initialized API Cache in in 0.22 sec
> pymel.internal.factories : DEBUG : Loading cmd cache...
> pymel.internal.startup : DEBUG : Loading the list of Maya commands from
> u'C:\\Program
> Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaCmdsList2015.zip'
> pymel.internal.factories : DEBUG : Initialized Cmd Cache in in 0.13 sec
> pymel.core.uitypes : DEBUG : could not determine node type for AETemplate
> pymel.internal.factories : DEBUG : MFnDagNode.model is deprecated
> pymel.core : DEBUG : Adding pluginLoaded callback
> pymel.core : DEBUG : Adding pluginUnloaded callback
> pymel.internal.startup : DEBUG : finalizing
> pymel.internal.startup : DEBUG : initMEL
> pymel.internal.startup : DEBUG : running: createPreferencesOptVars.mel
> pymel.internal.startup : DEBUG : running: createGlobalOptVars.mel
> pymel.internal.startup : DEBUG : running:
> C:/Users/cvernon/Documents/maya\2015-x64\prefs\userPrefs.mel
> pymel.internal.startup : DEBUG : running: initialStartup.mel
> Warning: file: C:/Program
> Files/Autodesk/Maya2015/scripts/startup/initialStartup.mel line 195: Y-axis
> is already the Up-axis
> pymel.internal.startup : DEBUG : running: initialPlugins.mel
> pymel.core : DEBUG : Plugin loaded: modelingToolkitExt
> pymel.core : DEBUG : Plugin loaded: modelingToolkit
> pymel.core : DEBUG : Plugin loaded: dx11Shader
> pymel.core : DEBUG : Adding command: dx11Shader
> pymel.core : DEBUG : Running plugin-loaded nodes callback
> pymel.core : DEBUG : Adding node: dx11Shader
> pymel.core : DEBUG : Adding node: coneAngleToHotspotConverter
> pymel.internal.startup : DEBUG : running: namedCommandSetup.mel
> pymel.internal.startup : DEBUG : running:
> C:/Users/cvernon/Documents/maya\2015-x64\prefs\userNamedCommands.mel
> pymel.internal.startup : DEBUG : running:
> C:/Users/cvernon/Documents/maya\2015-x64\prefs\pluginPrefs.mel
> pymel.core : DEBUG : Plugin loaded: retargeterNodes
> pymel.core : DEBUG : Running plugin-loaded nodes callback
> pymel.core : DEBUG : Adding node: CustomRigDefaultMappingNode
> pymel.core : DEBUG : Adding node: CustomRigRetargeterNode
> pymel.core : DEBUG : Plugin loaded: mayaHIK
> pymel.core : DEBUG : Adding command: HIKComputeReference
> pymel.core : DEBUG : Adding command: HIKInitAxis
> pymel.core : DEBUG : Adding command: GetHIKMatrixDecomposition
> pymel.core : DEBUG : Adding command: GetHIKNode
> pymel.core : DEBUG : Adding command: hikGetNodeCount
> pymel.core : DEBUG : Adding command: GetHIKNodeName
> pymel.core : DEBUG : Adding command: hikGetNodeIdFromName
> pymel.core : DEBUG : Adding command: GetHIKEffectorCount
> pymel.core : DEBUG : Adding command: GetHIKEffectorName
> pymel.core : DEBUG : Adding command: hikGetEffectorIdFromName
> pymel.core : DEBUG : Adding command: GetHIKChildCount
> pymel.core : DEBUG : Adding command: GetHIKChildId
> pymel.core : DEBUG : Adding command: GetHIKParentId
> pymel.core : DEBUG : Adding command: GetFKIdFromEffectorId
> pymel.core : DEBUG : Adding command: LoadHIKCharacterDefinition
> pymel.core : DEBUG : Adding command: SaveHIKCharacterDefinition
> pymel.core : DEBUG : Adding command: LoadHIKCharacterState
> pymel.core : DEBUG : Adding command: Loa

[Maya-Python] pymel crashing maya.standalone

2015-11-12 Thread Chad Vernon

Anyone with experience using pymel and maya.standalone experience any Fatal
Errors when the process ends?  I don't have any experience with pymel and
am looking into running a setup in standalone mode.

# runtests.py
import maya.standalone
print 'initialize maya'
maya.standalone.initialize(name='python')
print 'done initialize maya'
import pymel.core as pm
print 'done import pymel'
# pm.i_hate_you()

I've cleared my prefs, Maya.env, MAYA_SCRIPT_PATH, MAYA_MODULE_PATH, and
PYTHONPATH variables to make sure there were no conflicts.  This is what
happens:

C:\Users\cvernon\Documents\Development>"C:\Program
Files\Autodesk\Maya2015\bin\mayapy.exe" runtests.py
initialize maya
done initialize maya
pymel.internal.startup : DEBUG : startup.mayaInit: called
pymel.internal.startup : DEBUG : startup.mayaInit: maya already started -
exiting
pymel.internal.factories : DEBUG : Loading api cache...
pymel.internal.startup : DEBUG : Loading the API cache from u'C:\\Program
Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApi2015.zip'
pymel.internal.startup : DEBUG : Loading the API-MEL bridge from
'C:\\Program
Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaApiMelBridge.zip'
pymel.internal.factories : DEBUG : Initialized API Cache in in 0.22 sec
pymel.internal.factories : DEBUG : Loading cmd cache...
pymel.internal.startup : DEBUG : Loading the list of Maya commands from
u'C:\\Program
Files\\Autodesk\\Maya2015\\Python\\lib\\site-packages\\pymel\\cache\\mayaCmdsList2015.zip'
pymel.internal.factories : DEBUG : Initialized Cmd Cache in in 0.13 sec
pymel.core.uitypes : DEBUG : could not determine node type for AETemplate
pymel.internal.factories : DEBUG : MFnDagNode.model is deprecated
pymel.core : DEBUG : Adding pluginLoaded callback
pymel.core : DEBUG : Adding pluginUnloaded callback
pymel.internal.startup : DEBUG : finalizing
pymel.internal.startup : DEBUG : initMEL
pymel.internal.startup : DEBUG : running: createPreferencesOptVars.mel
pymel.internal.startup : DEBUG : running: createGlobalOptVars.mel
pymel.internal.startup : DEBUG : running:
C:/Users/cvernon/Documents/maya\2015-x64\prefs\userPrefs.mel
pymel.internal.startup : DEBUG : running: initialStartup.mel
Warning: file: C:/Program
Files/Autodesk/Maya2015/scripts/startup/initialStartup.mel line 195: Y-axis
is already the Up-axis
pymel.internal.startup : DEBUG : running: initialPlugins.mel
pymel.core : DEBUG : Plugin loaded: modelingToolkitExt
pymel.core : DEBUG : Plugin loaded: modelingToolkit
pymel.core : DEBUG : Plugin loaded: dx11Shader
pymel.core : DEBUG : Adding command: dx11Shader
pymel.core : DEBUG : Running plugin-loaded nodes callback
pymel.core : DEBUG : Adding node: dx11Shader
pymel.core : DEBUG : Adding node: coneAngleToHotspotConverter
pymel.internal.startup : DEBUG : running: namedCommandSetup.mel
pymel.internal.startup : DEBUG : running:
C:/Users/cvernon/Documents/maya\2015-x64\prefs\userNamedCommands.mel
pymel.internal.startup : DEBUG : running:
C:/Users/cvernon/Documents/maya\2015-x64\prefs\pluginPrefs.mel
pymel.core : DEBUG : Plugin loaded: retargeterNodes
pymel.core : DEBUG : Running plugin-loaded nodes callback
pymel.core : DEBUG : Adding node: CustomRigDefaultMappingNode
pymel.core : DEBUG : Adding node: CustomRigRetargeterNode
pymel.core : DEBUG : Plugin loaded: mayaHIK
pymel.core : DEBUG : Adding command: HIKComputeReference
pymel.core : DEBUG : Adding command: HIKInitAxis
pymel.core : DEBUG : Adding command: GetHIKMatrixDecomposition
pymel.core : DEBUG : Adding command: GetHIKNode
pymel.core : DEBUG : Adding command: hikGetNodeCount
pymel.core : DEBUG : Adding command: GetHIKNodeName
pymel.core : DEBUG : Adding command: hikGetNodeIdFromName
pymel.core : DEBUG : Adding command: GetHIKEffectorCount
pymel.core : DEBUG : Adding command: GetHIKEffectorName
pymel.core : DEBUG : Adding command: hikGetEffectorIdFromName
pymel.core : DEBUG : Adding command: GetHIKChildCount
pymel.core : DEBUG : Adding command: GetHIKChildId
pymel.core : DEBUG : Adding command: GetHIKParentId
pymel.core : DEBUG : Adding command: GetFKIdFromEffectorId
pymel.core : DEBUG : Adding command: LoadHIKCharacterDefinition
pymel.core : DEBUG : Adding command: SaveHIKCharacterDefinition
pymel.core : DEBUG : Adding command: LoadHIKCharacterState
pymel.core : DEBUG : Adding command: LoadHIKEffectorSetState
pymel.core : DEBUG : Adding command: LoadHIKPropertySetState
pymel.core : DEBUG : Adding command: pushPinning
pymel.core : DEBUG : Adding command: popPinning
pymel.core : DEBUG : Adding command: isDescendentPulling
pymel.core : DEBUG : Adding command: HIKUiControl
pymel.core : DEBUG : Adding command:
GetProperty2StateAttrNameFromHIKEffectorId
pymel.core : DEBUG : Adding command: hikBodyPart
pymel.core : DEBUG : Adding command: hikManip
pymel.core : DEBUG : Adding command: hikRigAlign
pymel.core : DEBUG : Adding command: hikRigSync
pymel.core : DEBUG : Adding command: ResetProperty2State
pymel.core : DEBUG : Adding command: HIKGetRemote

Re: [Maya-Python] script for measuring framerates?

2015-11-12 Thread Ravi Jagannadhan

Sorry, playback in Maya.

"There are no dumb questions" - Carl Sagan.

> On Nov 12, 2015, at 00:10, Marcus Ottosson  wrote:
> 
> Frame rates of what?
> 
>> On 12 November 2015 at 04:51, Ravi Jagannadhan  wrote:
>> Hi all, does anyone have any scripts handy for measuring frame rates (one 
>> that's not in the GUI)?
>> 
>> Thank you for your time,
>> Ravi
>> --
>> Where we have strong emotions, we're liable to fool ourselves - Carl Sagan.
>> -- 
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/python_inside_maya/CADHeb2Z8NXCQVc79PODDY80qj6Szp27NN%2BhZ_8%3Dt0SYiv1xBLw%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> Marcus Ottosson
> konstrukt...@gmail.com
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAaAJ6G1teCW%3D8gbMnrmEUqE25zPGfG_ZWbRV%2B2muHdNA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/2BDEC120-2AB2-4625-BE4B-9BC342AFE10A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] script for measuring framerates?

2015-11-12 Thread Marcus Ottosson

Frame rates of what?

On 12 November 2015 at 04:51, Ravi Jagannadhan  wrote:

> Hi all, does anyone have any scripts handy for measuring frame rates (one
> that's not in the GUI)?
>
> Thank you for your time,
> Ravi
> --
> Where we have strong emotions, we're liable to fool ourselves - Carl Sagan.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/CADHeb2Z8NXCQVc79PODDY80qj6Szp27NN%2BhZ_8%3Dt0SYiv1xBLw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Marcus Ottosson*
konstrukt...@gmail.com

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAaAJ6G1teCW%3D8gbMnrmEUqE25zPGfG_ZWbRV%2B2muHdNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Maya-Python] script for measuring framerates?

Re: [Maya-Python] Unable to get UI to work

Re: [Maya-Python] Unable to get UI to work

Re: [Maya-Python] pymel crashing maya.standalone

Re: [Maya-Python] Unable to get UI to work

Re: [Maya-Python] pymel crashing maya.standalone

Re: [Maya-Python] pymel crashing maya.standalone

Re: [Maya-Python] pymel crashing maya.standalone

[Maya-Python] pymel crashing maya.standalone

Re: [Maya-Python] script for measuring framerates?

Re: [Maya-Python] script for measuring framerates?

11 matches

Site Navigation

Mail list logo

Footer information