Topics by tag:
Recently published articles by Dave G:
Now that Mari 2.6 and Maya 2015 are out, I think it’s time to release Mari Me 2 that is a complete rewrite of the MEL version that is now much more powerful than that old script was. Aside from being able to send stuff from Maya to Mari, the new version has a ton of little goodies that aid working between Maya and Mari without the need to look at a single dialog box. Mari Me 2 can both send and receive objects to Mari, updating metadata-tagged materials for identification across sessions. It works great as a quick way to jump back and forth for stuff like Mari 2.6’s texture transfer feature that bakes textures between different mesh topologies or UV sets:
The transfer feature is better than it looks from those results – I was just kind of lazy about my alignment of the two different meshes in Maya. Mari Me also has a smart way to update your existing materials that is renderer agnostic. It doesn’t care what type of material is used on the mesh and will simply update it based on the channel name within Mari. If your material’s emissive channel in Maya is “blinn1.incandescence”, just name the channel “incandescence” in Mari and when you send it back to Maya, it will link up to that channel in the material:
That’s why I created a AddNewChannel-VRayMtl.txt setting preset for standard V-Ray Materials that you can paste into the channel presets section your Mari.ini file – those are pre-named to link up with the slots of a V-Ray Material and it would be very easy to make one for Arnold, RenderMan, etc that you could share on the Github page. If you send a texture to Maya from Mari without having sent anything from Maya to initiate those material metadata tags, it will just import the textures and you’ll see the file nodes in the Hypershade. Mari Me’s metadata tags don’t create any sort of plug-in dependency so nothing will break and you won’t receive any warnings if you send a scene to someone without it installed.
Automatic UDIM sending and loading
Mari Me 2 has robust support for UDIM-tiled textures:
If you are running Maya 2015 or above, that supports the UDIM file name variable, Mari Me will use that instead of importing and manually tiling all the UDIM textures. It will also recognize these 2015 UDIM names when you send tiled textures to Mari. It should also work fine with multiple meshes and a mix of tiled and non-tiled UV meshes. I tried to make it smart enough not to break with these production workflow variables but it’s possible stuff slipped through so let me know if you see anything and I’ll see if I can find some time to fix it in the near future.
Mari 2.6v1 got support for Alembic animated meshes and the Python import syntax is the same as importing OBJs so I added support for exporting animated meshes from Maya to Mari via Alembic:
As you can see in the interface, there are a bunch of other little tools and tricks in Mari Me 2:
There are no file format options so everything is sent back and forth as TIFF, since that format can accommodate all bit depths and all working files are in a projectpath/MariMe/ folder so there is no risk of clobbering your existing assets.
Released under a BSD3 license
I started the Python version of Mari Me as a “Pro” version that was going to be monetized but decided not to after getting a new job that I’ll get into later. Because I’m going to be super busy with this new gig, I’m going to have to release Mari Me as unsupported but I released it as open source under the BSD3 license for studios or individuals that want to change the code and use it for their own and they can decide whether or not they want to fork it or not on the Github page for Mari Me:
The old MEL version is no longer on Creative Crash. Read the Read Me file because that explains the setup.
6 notes | Permalink
save the MEL script to any of your Maya script folders (~/Library/Preferences/Autodesk/maya/scripts being the one that is accessible to all versions) and then enter this in the MEL command line at the bottom left of the window and hit enter:
That will initiate the batch render script. If you want to save a shelf item for it, look here:
So Maya 2015 is out now on the subscription site and it gets a texture displacement deformer à la iDisplace, and I thought I’d show a quick workflow for using it with paint masking of deformer weights:
As you can see, it’s a great way to build procedural shapes with the friendliness of painted masking. If you’re using Maya 2014 or earlier, iDisplace is an essential (and free) plug-in that offers similar functionality, so go grab it.
Here’s the invite to my coming show with Luc Paradis, an exceptional artist and friend with whom I’ve always wanted to show.
If you’re in Montreal, swing by for the art and free booze. I’ll also be showing the interactive Oculus Rift/Unreal Editor 4 piece that I’ve been building for it.
2 notes | Permalink
If you work with particle animations, you probably know about Nimble Tools Uninstancer. It’s been around for years and unfortunately the developer stopped working in VFX but he posted the source scripts (the pre-built Python plug-in broke recently) but they have been updated and posted here:
It’s the best uninstancer around so look no further. Verified working in Maya 2014 and 2015 late beta.
I’ve been working with the Mac version of Unreal Editor 4 for a week or so now and am really loving it. I had some experience using UDK3 found the workflow and interface less than great, and it seems they agreed with me because the changes in UE4, as far as workflow go, are almost perfect. And, even though there are a few bugs with the launch version that are being actively squished, the Mac version is no half-assed port. While gaming on the Mac will never replace gaming on the PC, Epic is clearly bullish on the future of Mac and iOS as gaming development and gaming platforms respectively.
Pretty much everything you want is there. Multithreaded light map baking, Matinee, Blueprints (the stuff that replaces Kismet), those GPU-accelerated particles with vector grid and collisions:
Performance looks worse in that video than it is due to a screencap / GPU combo.
You get that sweet shader editor:
Really nice Maya-to-Unreal material support so you can import one combined mesh into Unreal but still get all those unique shader references to edit or even replace:
Post-process volume with bokeh DOF and colour grading:
IES light profile support:
Global Illumination without tricks:
It all adds up to an impressive show considering they had to do this all for OpenGL:
The only noticeable omissions from what I can tell so far are:
- Displacement tessellation for OpenGL shaders
- Oculus Rift Mac Support (this is in Unity already so I hope this comes soon)
- The auto-UV reconstruction stuff isn’t ported yet
Edit: Unreal Me stuff removed
I took down the Unreal Me script because Unreal Engine now lets you import baked animation without bones with the following workflow:
1: Group your baked key animation objects in Maya.
2: Export to animated FBX 2013 with the group selected
3: Import the FBX with the following settings:
Make sure that Import Animation and Import Rigid Mesh is set. From then you’ll get your non-joint based animation imported correctly.
Oh, the joys of scripting for a program you’re still learning :p
4 notes | Permalink
There is a ton of info on that around the net (if it’s for Max, it’s fine since the settings that affect flicker are the same in Maya) so look around.
1 note | Permalink
Make sure you’re running it in the MEL command line and not Python.
Most people know that I do my modelling in Maya but it’s not much of a secret in the industry that MODO is hard to beat as a modeller. One of the main things missing though from MODO’s powerful toolset was a procedural, non-destructive workflow for building models. This is where the recent MeshFusion comes in and The Foundry gave me a copy to try out for a bit and it’s pretty impressive bit of kit. There’s a really good rundown of how it works on here so I don’t need to go through the basics of setup for you:
As you can see from the video, the MeshFusion Booleans are very capable and you’d have a hard time breaking it with complex combinations, which can be a problem with some Boolean implementations, like Maya’s pre-2014 Extension Carve lib-based Bool ops.
Aside from the intuitive tree or schematic views, the really nice features are the procedural bevel controls which also make this Maya user envious:
Maya’s bevels are a bit of a weak point in the software so, if you’re looking to get really good hard-surface tools but avoided MODO because of the previously destructive workflow, you might want to check out MeshFusion. If I did more of this kind of inorganic model work, I’d likely have a hard time staying away from it. With that said, I do think the MeshFusion stuff should be part of the MODO base package because MODO is playing catch-up to Maya for the procedural part.
3 notes | Permalink
There are a lot of texture sites out there and I have a ton of stock images that I already use for texturing but I recently discovered texturelib.com and it is hands down the best site for textures I’ve seen. The quality and resolution of the images are great but what really stands out about their images is that they are exceptionally shot, without uneven lighting, wide-angle distortion or bad perspectives. They must be using long focal lengths and cameras mounted on remote-controlled helicopters for most of these because you just can’t shoot stuff like this without some special setup:
Anyway, I just had to spread the word because I just bought the year’s subscription for a paltry $29. Seriously, run don’t walk to get on that stuff.
3 notes | Permalink