Topics by tag:
Recently published articles by Dave G:
Someone requested my handy V-Ray Tuner Presets setting feature for the soon-to-be-outdated V-Ray Tuner for V-Ray 2.4 so I added that feature to the 2.4-compatible version that’s on Creative Crash. This will be the last update to V-Ray Tuner for V-Ray 2.4 so be sure to grab it now if you’ll be sticking with that version for a while. If you haven’t seen the V-Ray Tuner Presets in action, here is a rundown of why it’s handy, from the changelog:
Added V-Ray Tuner Presets manager for render settings in the Render menu. This is a nice way to create render presets that don’t affect EVERYTHING like Maya’s render presets do. This only affects the toggles you see represented in the V-Ray Tuner interface, so you can use a universal “Draft” setting for different resolution documents and click the load for final render settings that you prefer and only have the relevant quality features changed.
Here it is in a workflow:
Otherwise, if you’re using the V-Ray 3.0 betas, be sure to check out the awesome GGX-based BRDF that’s been added to the V-Ray 3.0 release candidate:
If you want to read up on GGX, there are good examples by a talented coder who wrote his own GGX shader here – he sums up GGX like this:
It is very good for use with more accurate metals.
After returning from a very good SIGGRAPH, I’ve found some time to put up the latest version of V-Ray Tuner that has been cooking for the last number of months. I have been beta testing V-Ray 3.0 and I’ve added a lot of features that should cover the 3.0 user well from the beta to the release versions and beyond. Grab it here.
Warning: V-Ray 3.6 was the last version to support versions of V-Ray 2.x so it’s possible that you can get errors if you use it with version 2.4. Some of the features use things like V-Ray’s query options that are 3.0 only:
So, here are some of the additions to V-Ray Tuner 4 that I think will be well liked by V-Ray 3.0 beta and release users:
See all those new things above in action here:
Another cool feature that I think will save people a lot of time:
Anyway, enjoy and I’ll post the final on Creative Crash once V-Ray 3.0 is released.
2 notes | Permalink
I’m waiting to move into my new place in San Francisco tomorrow and noticed that someone asked me on Twitter if I could share this sand shader that I made for some of my Turbosquid assets. So I figured, “why not?,” so here is a download for both procedural shaders for Maya (V-Ray and mental ray):
Here’s a preview of what they look like:
Enjoy. And may Will Smith save all your nations by injecting a VBScript virus into the gooey organic innards of an invading alien race’s mother ship.
5 notes | Permalink
I tried to compile this a while back but couldn’t get it to build but someone else took the time to get it working, so here is the link to download:
You can get the source here:
Well it’s been a hectic month here since I moved from Montreal to San Francisco. I found a little time between working, getting a car – loving this Ford Fusion Energi SE – and getting a place in the Mission (sweet Jesus, the rent here!) to add a requested feature to this script. You can now add or update the frustum for all selected cameras in version 1.2 of Make Frustum for Maya. Go get it:
ya, sure. It was easy to do so here is a new version of the script with a button to make a new camera with the geo frustum already attached:
The 3.2 update to Facer is up on Creative Crash. The changelog:
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
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