Update- almost there! 303 south hallI believe.
A blog about technical art, particularly Maya, Python, and Unity. With lots of obscurantist references
We've Moved
The blog has been retired - it's up for legacy reasons, but these days I'm blogging at blog.theodox.com. All of the content from this site has been replicated there, and that's where all of the new content will be posted. The new feed is here . I'm experimenting with crossposting from the live site, but if you want to keep up to date use blog.theodox.com or just theodox.com
Tuesday, February 24, 2015
GDC on the horizon
For folks who'll be attending GDC this year, I'll be doing a talk on Technical Art for Art Directors at the Art Director's bootcamp on Monday at 2:15. Hope to see some of you there!
Saturday, February 14, 2015
Poll tax
I'm experimenting with Blogger's (not super impressive) poll support. So please check out the poll on ScriptCtx on the right hand side of the page. If the survey produces good results I'll do more as way of getting more sense of what the community is doing out there....
Thursday, February 5, 2015
What The...?
Like many Maya heads I have long wrestled with the problem of filtering lists to get what I'm interested in. You're probably familiar with the use of the type flag in cmds.ls() to filter on types: for example this will give you only the transforms in your current selection:
cmds.ls(sl=True, type = 'transform')
This works for any node type (the list is quite long: it's basically the whole maya node class hierarchy) and is a handy way to
However I just noticed today that this works a little for component selections as well. For some reason Maya 2014+ seems to treat faces, edges and vertices as if they were nodes of a "float3" type (uv's are "float2"s) . This means you can get the components from a mixed selection with:
cmds.ls(sl=True, type = 'float3')
Not the most earth-shattering discovery of the 21st century, but handy nonetheless.
Subscribe to:
Posts (Atom)