You are trying to position joints in your scene with the Move tool, and you notice that Maya is changing the orientation of the selected joint's parent joint.
Continue reading "When I move a joint, its parent changes orientation" »
You are trying to position joints in your scene with the Move tool, and you notice that Maya is changing the orientation of the selected joint's parent joint.
Continue reading "When I move a joint, its parent changes orientation" »
Posted by Owen Burgess on 14/05/2012 at 11:57 AM in animation, modeling, rigging, UI | Permalink | Comments (0) | TrackBack (0)
Tkinter is a Python GUI package which operates on top of Tcl/Tk. The Tkinter .so is included with Maya’s packaged Python folder. For users on Linux running distributions like Redhat Enterprise 6 or Fedora 14 you will notice that the default version of Tcl and Tk are 8.5. Running any Tkinter call within Maya’s ui will automatically prompt an error:
from Tkinter import *
root = Tk()
# Error: TclError: Can't find a usable init.tcl in the following directories:
/usr/share/tcl8.4 /usr/aw/maya2011-x64/lib/tcl8.4 /usr/aw/lib/tcl8.4 /usr/aw/maya2011-x64/library /usr/aw/library /usr/aw/tcl8.4.13/library /usr/tcl8.4.13/library /usr/share/tcl8.4
You will notice Maya is pointing to a version Tcl which is not installed and looking for directories which are not on the system.
The reason this occurs is because we compile Maya on the lowest possible setup for compliance. Maya 2012 is based on Redhat Enterprise 5. This simply means that the default Tcl and Tk version on this distribution are 8.4. Unfortunately, this information is hardcoded into the _tkinter.so file included in the Maya python "lib-dynload" folder. This cannot be changed. So your only option at this point is to install the 8.4 version of the app.
There is no need to remove your current Tcl or Tk versions and the 8.4 version can be installed without any issues. You will need to source these based on your distribution and get the rpm’s installed and Maya will than grab the proper directories in /usr/lib.
Let’s now focus on some actual work. Below is a sample script which will build a GUI window with a button to build a sphere. You will notice I added some threading commands. The reason for this is to make sure that the Maya UI is still available and updated without having to wait for the python UI to close before updating the viewport.
import maya.utils
import maya.cmds as mc
import Tkinter as tk
import threading
def makeSphere( radius ):
print "WOW that Sphere is great!"
mc.sphere( radius=radius )
def makeMySphere():
maya.utils.executeInMainThreadWithResult( makeSphere, 5 )
def UI():
app = tk.Tk()
btnCube = tk.Button(app, text="Make a special Sphere", command=makeMySphere )
btnCube.pack()
app.mainloop()
class MyThread ( threading.Thread ):
def run ( self ):
UI()
MyThread().start()
I hope this is helpful for anyone using Tkinter on Linux. Please remember this was only tested on Linux so I am not sure what the behaviour is like on Windows.
There are also other options for building python GUI’s. We have details in the Maya devkit for pyQt and I have also seen folks use wxPython.
Cheers!
Nelson
Posted by Nelson Cruz on 09/03/2012 at 05:11 PM in linux, python, UI | Permalink | Comments (0) | TrackBack (0)
Every now and than we get requests from users who mention that they have installed True Type Font on Linux but Maya's Create text feature is not picking them up.
The main reason this occurs is because Maya only uses the Type 1 .PFA fonts. These are postscript fonts. So to get TTF format to work you will need to get them converted. There are a couple of tools to get this done.
The first option is simple but involves uploading your current TTF to a online server which converts them and makes it available for download.
http://onlinefontconverter.com/
While this is easy to use I would use caution if the fonts you are converting were purchased.
The second option is to download a simple little application from http://ttf2pt1.sourceforge.net/ which will allow to locally convert your TTF to PFA on your Linux box.
I have used this application plenty of times without many issues getting fonts converted. I generally run a simple command like.
ttf2pt1 -e location_off.tff
This will convert the TTF and save the PFA into the same directory. After that you simply need to copy the file into one of the following directories.
“/usr/share/fonts/default/ghostscript”
“/usr/share/X11/fonts/Type1”
“/usr/share/fonts/Type1”
“/usr/X11R6/lib/X11/fonts/Type1”
Hope this helps!
Posted by Nelson Cruz on 08/07/2011 at 09:31 PM in linux, UI | Permalink | Comments (0) | TrackBack (0)
We are aware of UI clicking issues with Maya 2012 users running tablets that have been set to function in mouse mode instead of the default pen mode. At the moment we have only seen reports of this problem from Windows users.
While Maya 2011 did not have these tablet problems, Maya 2012 is running on a newer version of Qt which seems to have introduced this problem.
We are working on the issue with all the parties involved and hope to have it resolved in the near future. In the meantime if you are running into tablet issues in mouse mode please revert them back to pen mode in your Wacom tablet settings.
Cheers!
Posted by Nelson Cruz on 13/04/2011 at 03:59 PM in UI | Permalink | Comments (7) | TrackBack (0)
This video is a technology preview. Autodesk wishes to caution you that this preview reflects technology research, and that actual events or results could differ materially from the preview. Also, this preview is not intended to be a promise or guarantee of future delivery of products, services or features but merely reflects technology research, which may change. Purchasing decisions should not be made based upon reliance on this preview. Autodesk does not assume any obligation to update any statements we make to reflect events that occur or circumstances that exist after the date of this technology preview.
Posted by Nelson Cruz on 14/02/2011 at 05:01 PM in UI | Permalink | Comments (1) | TrackBack (0)
On Windows, some information about the Maya 2011 File Browser and the Maya 2011 Color Picker is stored in the registry, not the userPrefs.mel file as you may expect.
For example, the position and size of the Maya File Browser are stored in the registry location: HKEY_CURRENT_USER\Software\Autodesk\Maya\2011.5-x64\FileDialog (depending on the version it could also be in 2011, 2011.5, 2011-x64).
The syntax of 'pos' is @Point(xxx yyy), as illustrated:
If the situation arises where you can't see the Maya 2011 File Browser, you would check the value of the FileDialog key 'pos'. Try resetting this value to @Point(0 0) and then restart Maya.
Thanks to Nicolas Holst for the tip.
Owen
Posted by Owen Burgess on 26/01/2011 at 04:33 PM in fileIO, UI, Windows | Permalink | Comments (3) | TrackBack (0)
Prior to Maya 2011 there was no easy way to export data from Maya to Alias Studio, as a .wire file, if you were using a 64 bit platform.
If you have installed a 64 bit version of Maya 2011, simply load the DCExport plugin from the Plug-in Manager, then choose the SPF_DCE from the list of file types in the Export options, as illustrated.
Posted by Owen Burgess on 20/01/2011 at 11:19 AM in fileIO, UI | Permalink | Comments (1) | TrackBack (0)
Many users do not realise that MatchMover has two basic UI settings that give you access to features that you may not normally see when you first launch MatchMover.
MatchMover by default will first launch in what is called Light Mode. Light Mode was designed for users to avoid the complexity of MatchMover and use simple automatic workflows. This is great but you will sometimes need a tool or feature and realize that it is not visible. The survey features for tracks is a good example of this. These options will not be visible in the track parameters while you have the UI set to Light Mode.
Switching to Full Mode in the toolbar will open access to these options and many others. Please check the MatchMover documentation for more info.
Posted by Nelson Cruz on 14/10/2010 at 05:40 PM in Matchmover, UI | Permalink | Comments (0) | TrackBack (0)
There has been an issue that has been popping up in isolated cases. It seems to affect the use of the Hypershade where as it appears empty or partial empty and you may see the ‘Invalid Syntax’ Error.
This is being caused when you have an apostrophe (‘) in the path to your local Maya folder.
For example: C:/John’s Documents/maya/2011-x64/…”
The easiest and quickest fix would be to create a new user account without the use of an apostrophe in the name and log into that to use the application.
Posted by Ash Aiad on 31/08/2010 at 06:30 PM in installation & configuration, UI | Permalink | Comments (0) | TrackBack (0)
Today, I ‘m going to expand on the blog post that Owen wrote about the new dockControl command in Maya 2011 and look at some more advanced examples of its usage.
Mainly delete the UI when it becomes hidden, a look at the different methods, adding multiple windows and adding them to layouts.Delete the docked window when it is invisible
The first problem that will be obvious to users, is that once we create a docked generic window with the dockControl, you lose the ability to bring up that window even after the docked one is closed.
Example:The problem with this approach is that if I close the docked script editor, I won't be able to open the script editor with the main menu (I'll get // Error: line 1: No window found. /).
Using that little cross to close the window doesn’t actually delete the UI, it hides the window. And as we all know, Maya doesn't like multiple Outliner or Script editors… so it’s important to delete the UI so you can open the UI again later.
To do that, you use the –vcc (visibleChangeCommand) and the –io (isObscured) flag to query when the window is obscured and then delete it with the deleteUI command:
$customOutliner = `dockControl -area "left" -content scriptEditorPanel1Window -vcc "if (`dockControl -q -io $customOutliner`) {evalDeferred \"deleteUI $customOutliner\";}"`;Here the syntax is fairly similar except I am giving a name to the control, so I can delete easily afterwards. Secondly and most importantly, I am testing with a query when the window becomes obscured and once it is, delete it with the –vcc and the –io flag.
Doing it this way is more scripting but it will make the Outliner useable in and out the dockControl.
We can add a global procedure called by the configString to create our dock window. So it will look like this :
panelConfiguration -label (localizedPanelLabel("SPECIAL"))Posted by Annick Harmel-Tourneur on 09/08/2010 at 11:10 PM in MEL, UI | Permalink | Comments (3) | TrackBack (0)




Subscribe
Recent Comments