Autodesk has released Arnold 7.5.1. The headline feature is Flow Render, a new cloud rendering tech preview that gives Arnold users 2,400 render minutes per month for testing. Beneath that, and arguably more useful once actual shots arrive, the update also fixes a long-standing gap in volume AOVs, adds MIKKTSpace normal mapping, and squeezes some extra CPU performance out of Windows.

Flow Render is here, with sensible limits and no magic involved
The loudest part of Arnold 7.5.1 is Flow Render, Autodesk’s new cloud rendering tech preview for Arnold. During the preview, users get 2,400 render minutes per month. That is 40 hours, which is enough to test the service properly, but not enough to start behaving like a streaming platform.
The basic idea is simple: submit Arnold jobs to the cloud, free up local machines, and run more variations in parallel. Autodesk pitches this as a way to speed up rendering, look development, and simulation work without tying up workstations all day.

Flow Render requires an Autodesk account login, because of course it does. Submission happens through the Arnold plugins. Autodesk lists support for Houdini, 3ds Max, Cinema 4D, and Maya, while Katana support is still listed as coming soon. The backend runs on Autodesk Platform Services through the Flow Graph Engine API, which handles the cloud storage and compute side.
Autodesk says Flow Render is aimed at everyone from larger VFX and animation studios to freelance 3D and FX artists. That is the official line. In practice, the current limits matter more than the broad target group wording. A single task can run for up to 12 hours. Users can run up to 10 tasks simultaneously, subject to service-level limits. Task data is stored for 30 days.

So yes, it is cloud rendering. No, it is not a bottomless sky-farm that will lovingly absorb every pipeline problem. At this stage it looks more like a practical overflow and evaluation option, which is honestly a lot more believable.
The more important production news is in Arnold itself
The stronger part of this release is the renderer update. Arnold 7.5.1 finally adds proper custom AOV support for volume shaders. The aov_write_rgb, aov_write_float, and aov_write_rgba shader nodes now work in volume networks just as they do for surface shaders. Previously, Arnold silently ignored them in volume contexts, which is the kind of workflow detail that tends to waste time very efficiently.

Autodesk says the volume raymarcher now collects AOV closures at each step and integrates them using Beer-Lambert weighting, so the resulting outputs remain physically consistent. Flat formats such as EXR and TIFF are supported, as is deep EXR. There is a cost, naturally. Autodesk notes roughly 16% overhead with two active volume AOVs at fine step sizes. Useful feature, non-zero bill. Reality remains intact.

Arnold 7.5.1 also adds a new tangent_space_type parameter to the normal_map shader, bringing support for MIKKTSpace normal mapping. The previous mode stays in place as standard, while the new mikk mode uses MIKKTSpace-generated normal, tangent, and bitangent data from DCC tools such as 3ds Max. That should reduce shading mismatches between applications, which is not glamorous, but is exactly the kind of boring improvement people end up appreciating.
Windows users also get CPU render optimizations. Autodesk says most scenes render faster, though not all. The examples in the release notes show a 1.16x speedup for the OpenPBR shader ball, 1.08x for gtc-robot, 1.07x for Disney cloud, and 1.04x for ALab. Intel jungle ruins stays at 1.00x, apparently choosing not to participate.
There is one incompatible rendering change worth noting. Arnold now correctly supports the exponent parameter in the OSL generalized_schlick_bsdf closure for both reflection and transmission. Scenes using non-default exponent values or heavy transmission may therefore render differently. Technically correct, slightly annoying, very Arnold-point-release.
The bug-fix list covers GPU artifacts, IPR crashes, incorrect volume mipmap selection, polymesh crashes, Hydra update problems, and several USD-related issues. So this is a proper point release: one shiny cloud headline, several genuinely useful renderer fixes, and a pile of smaller changes that will matter most to the people who have already been burned by them.
Links
Autodesk Arnold 7.5.1 release notes:
https://help.autodesk.com/view/ARNOL/ENU/?guid=arnold_core_7510_html
Autodesk Flow Render FAQ:
https://help.autodesk.com/view/ARNOL/ENU/?guid=arnold_core_rendering_ac_flow_render_faq_html