For those who don’t know the tool: Flair is a stylized renderer inside Autodesk Maya, focused on NPR looks in the viewport and rendering, with style shaders, materials, and line effects that sit upstream of comp and delivery.
macOS arrives, and it is not a footnote
Flair 1.2 adds macOS support for Maya 2024 and newer. The supported operating systems now cover Windows, Linux (Rocky), and macOS, with macOS builds on Apple Silicon only. The setup requirements are macOS 14 as minimum and macOS 26 as recommended, alongside Windows 10 and 11 and RHEL based Linux options. Linux availability is tied to specific license tiers.
Proxies stop being special materials and start being a toggle
A core workflow change in 1.2 is how proxies work. Any flairShader material can now double as a proxy with a single toggle, replacing the old ShaderFX proxy material. The new proxy behavior supports Wobble, Offsets, and multiple NoiseFX types. That matters because the proxy no longer needs to be a separate shaded thing you babysit, it becomes a mode of the same material you already use.
This is a practical fix for hard-shell proxy intersections and visible component lines when proxy geometry overlaps other geometry. With the proxy living inside the same shader, you can apply effects like Wobble Blur to introduce diffusion and gradients rather than accepting a hard boundary.Using proxy offsets to localise line thresholds, so a region can show only depth-based silhouettes while the rest of the scene keeps different line logic. That kind of localised override can be the difference between a clean frame and a late night of per-shot hacks.
You still want to test this carefully in production. Even when an update says it is seamless, changes to proxy behaviour can alter look dev deltas in ways that only show up once animation starts doing unpleasant things.
Lines get more controllable and more mischievous
Flair 1.2 adds a set of line features that target a classic pain point: outlines and inlines are not the same thing, so stop treating them as if they are. A new Canvas Override global attribute can replace the beauty pass with the canvas colour. In practice, this lets you inspect what Flair effects and line work contribute, without the underlying shaded colours distracting you. The attribute appears in the globals documentation and in the release notes as a new global control.
For outlines specifically, the update adds Outline Width Offset, letting you modify line width for outlines relative to inlines. In the video, this becomes a look-dev lever for graphic styles in which the silhouette reads as bold while interior lines stay subtle, or where outlines disappear entirely, leaving only internal structure.
Light response also gets split. There are new controls over Outline and Inline Light Response for both clean and rough lines. That separation enables a sharper art direction trick: negative light response. Negative light response shows lines in shaded parts of the scene, which the update calls out as a “noir-style” option. In the demo, that produces lines where you would otherwise get pure darkness. It is a neat tool for stylized lighting setups where you want form to read in the shadows without repainting the entire grade.
Depth based sketchiness control arrives too, via Sketchiness Depth Range and Sketchiness Depth Factor. This lets sketchiness increase or decrease along scene depth, and it is presented as a global control that works across scenes, rather than relying only on placing proxy planes at different distances. For facilities that build reusable style presets across sequences, this is the sort of knob that can save time when layout changes the scale of a set and your line breakup suddenly looks wrong.
Licensing grows up: subscription, plus options studios actually ask for
Flair 1.2 expands licensing beyond subscription to include perpetual and floating licenses, and it introduces a licensing server to manage floating seats. Online licenses can be migrated to a new machine six hours after the previous activation. The release log also calls out fixes for activation on new Windows machines where wmic is missing, and an installer fix when an older install folder path no longer exists.
Activation for floating licensing occurs by entering a hostname or IP address for the license server, after which the client fetches available licenses and activates the first one that is free. That maps cleanly to typical facility patterns where artists should not care which workstation holds a seat today, only whether the pool has one left.
Performance and saving: fewer reasons to stare at a frozen UI
The Sequence Renderer gets asynchronous saving of images to speed up rendering, with image writes moved to a separate process so they do not interfere with rendering. It also gains continuous improvement for anti-aliasing beyond 32 TAA samples up to 254 samples, and the camera list can now be unlimited.
Material handling gets several workflow improvements. Keyed attributes in flairShader materials now work in Parallel and Serial evaluation modes. All material attributes appear in the Channel Box and the Attribute Spreadsheet. There are fixes for a GPU memory leak tied to assigning materials to components while scrubbing the timeline, and several other fixes around AOV blending, vertex baking, and material conversion.
There is also a new “Sanitize Flair” button in the toolbox that unloads the plugin and tries to remove all traces of Flair from an open scene, with a confirmation dialog and no undo. That is the sort of scorched earth tool that you hope you never need, until the day you really need it.
Unreal Engine enters the chat, via beta testing
Alongside the Maya 1.2 release, the newsletter announces beta testing for Flair for Unreal Engine. The team received an Epic MegaGrant last year and that it led to a major roadmap overhaul and a late Maya update, while enabling focus on bringing Flair to Unreal Engine.
The Unreal version is not nearly as feature-rich as the Maya version yet, but it is completely modular. The modular approach is a way to mix and match different effects to create a custom style. Beta testers are recruited by replying to the email, with testing planned for April and a questionnaire at the end of the month to help prioritize features and guide future development. If you live in a pipeline where Unreal Engine sits in previs, virtual production, or realtime look dev, a modular stylized renderer could be very useful. It could also be a moving target, because beta testing exists for a reason.
One last reminder before you install anything on the main machine: validate look changes on a copy of your scene library, because even small line and proxy changes can ripple through a show. And yes, the nori lines look great in a demo, but your shots will still find a way to be difficult.
https://docs.artineering.io/flair/release-log/
https://artineering.io/
