V-Ray Next for Maya – Update 1 – Available Now

V-Ray for Maya

V-Ray Next for Maya has been updated with great features and a number of important fixes to improve your rendering experience, including:

  • Support for Maya 2019
  • New memory tracking, with memory usage reports so you can optimise your scene
  • Cryptomatte support for VRayProxy sub-objects
  • Faster time to first pixel for quicker render startup
  • ALSurface support on GPU
  • Improved light sampling on scenes with thousands of lights

V-Ray Next for Maya is available now at CAD Software Direct as a perpetual, monthly or annual license.

Read on below for the full changelog.

 

Changelog – New Features

V-Ray

  • Improved light sampling on scenes with thousands of lights
  • Added memory tracking options to V-Ray Render Settings
  • Added peak memory consumption in EXR metadata
  • Added an option for consistent render elements for better compositing. Enabled by default on new scenes
  • Faster translation of mesh geometry
  • Added AppSDK with Python binding to installation
  • Added Lighting Analysis Render Element
  • Added efficient instancing for hair with “dynamic hair tessellation” and “stored in global hair tree” disabled
  • Added matte backfaces output to the surfaceLuminance mode
  • Added inverse exposure texture shader for compensating changes in physical camera
  • Command line interface tool for selecting rendering devices
  • Added an option to automatically exit vray -server if idle after a specified amount of time

Cryptomatte/VRayProxy

  • Cryptomatte support for V-Ray Proxy sub-objects

V-Ray GPU/VRayAISurface

  • AlSurface support on GPU

Chaos Cloud

  • Cloud window allowing direct submit from Maya

VRayLightSelect

  • Added new light select indirect modes

V-Ray GPU

  • Resumable rendering with GPU bucket sampler
  • VRayCurvature support on GPU
  • Support of Glossy Fresnel feature on GPU
  • Added support for CUDA-CPU rendering to the GLSL and MDL plugins
  • Added subpixel mapping checkbox for GPU bucket rendering
  • Support for multiple map channels for TexBitmaps in MtlGLSL
  • Support for the frame offset of the Maya file node when an image sequence is used

Cryptomatte

  • Cryptomatte support for all deep merge modes

vdenoise

  • Ability to apply lens effects in vdenoise

VRayMultiSubTex

  • Added a random “Seed” and “Loop Textures” parameters to MultiSubTex

VRayMtl

  • Added the anisotropy axis and anisotropy derivation controls to the VRayMtl

VRaySun

  • Added the color mode option to the VRaySun

VRayToon

  • Added support for VRayToon in glossy refractions

VRayFastSSS2

  • Added “Color Mode” dropdown in the VRayFastSSS2 material

VRayMtl/V-Ray GPU

  • Self Illumination GI for VRayMtl now visible in GPU-dependent UI

VRayToonMtl

  • Added support for spline interpolation in VRayToonMtl ramps

Misc

  • VRayTriplanar/Viewport 2.0 Triplanar texture projections support for viewport 2.0
  • VRayOSLMtl/VRayMDLMtl Material select support for MDL and OSL

V-Ray IPR

  • Faster updates in IPR when moving heavy geometry

 

Modified Features

VRayProxy

  • Optimized proxy visibility list controls for better proxy node performance in Maya
  • The VRayMeshPreview node will be created during the vrayCreateProxy command, not on an idle callback, making scripting easier
  • Removed unnecessary file reads when loading scene
  • Shader names list generation no longer happens on idle and is now more script-friendly
  • Removed the deprecated “use Maya shader” option from the VRayMesh node
  • Fixed slowdown and many warnings printed when instancing a VRayMesh with missing filename
  • XML material assignment override will now appear in the filepath editor
  • The vrayCreateProxy command will now return a string with the newly created node
  • The Maya Archive cmd will now take into account .vrmesh assets

Cryptomatte/VFB

  • Cryptomatte data channels will not be visible in the VFB, only the preview channel

VRayAlSurface

  • Fixed AlSurface GI contribution going into the SSS channel
  • The global SSS toggle will now affect AlSurface

Chaos Cloud

  • Pre/Post Render MEL scripts are now executed when exporting for Cloud

V-Ray

  • Faster time to first pixel with V-Ray Fur
  • Changed the default frame number separator char to . in PTex baker
  • Automatic conversion from Color to AColor when using -parameterOverride in V-Ray Standalone
  • Added extra attribute for controlling 3dProjection’s number of motion blur samples
  • More informative error messages for image file errors
  • In DR, automatically delete cache_info_portNum.txt on render end if VRAY_LOCAL_CACHE_LIMIT_VALUE=0
  • Fixed inconsistencies with the merge by z-depth mode of deep rendering
  • Temp files are now created with read/write permissions for all users
  • Fixed VRayPlaceEnvTex Ground Projection not respecting Up Vector
  • The Up Vector default value now respects Maya Preferences
  • No longer force-switching to progressive sampler when changing the production engine to GPU CUDA
  • Faster export of user attributes

VRaySoftbox

  • Fixed Softbox not having a swatch preview

VRayMultiSubTex

  • MultiSubTex indexing will start from 1 for new scenes, making randomization work correctly

VFB

  • Save current channel from VFB no longer appends the channel name to the user-defined file name

VRayMtl

  • Fixed some VRayMtl attributes not being listed in the channel box

V-Ray GPU/VRayEdgesTex

  • Show the “Show subtriangles” option in VRayEdges texture on GPU

V-Ray GPU

  • Dome lights will contribute to ZDepthRE

V-Ray IPR

  • More responsive IPR for heavy scenes

 

Bug fixes

V-Ray IPR

  • Fixed crash when stopping IPR while compiling geometry
  • Fixed crashes when switching the viewport subdivisions ON/OFF while rendering
  • Fixed a crash and wrong subdivision of geometry in specific cases
  • Fixed changed material on instanced object not reflected in IPR
  • Fixed a crash with IPR if rounded edges attribute is added to a mesh-clipper
  • Fixed changing the “Use Image Sequence” parameter in IPR crashing Maya
  • Fixed slowdown with viewport IPR caused by an animation rig
  • Fixed flickering in IPR
  • Fixed unhandled exception in IPR when VRayPlane is shaded with direct VRayLightMtl

VRayAlSurface

  • Fixed incorrect render of ALSurface if lighting render element is enabled

V-Ray

  • Fixed Streak particles having wrong transformation
  • Maya on remote desktop crashes on loading specific file
  • Fixed last user attribute not exported correctly in some cases
  • Maya drag’n’drop: added a special case for Windows file share paths
  • Fixed V-Ray not saving output image when data region is empty
  • Fixed wrong export of referenced render elements in batch
  • Fixed fatal error in some cases when starting DR if the host is not found
  • Fixed V-Ray printing an incorrect success message for writing output image with a missing asset in DR
  • Fixed noisy reflections with V-Ray Next for objects with cast shadows on, but visible in reflections/refractions off
  • Fixed refractive objects rendering darker with photon caustics from a dome light
  • Set a min limit of 1.0 to the AA Filter size
  • Fixed incorrect reporting of primitives with embree hair
  • Fixed crash when enabling/disabling reference scenes while running IPR
  • Fixed OSL crashes on post-Haswell processors
  • Fixed EXR files loaded in the VFB not having their integer REs displayed
  • Fixed slowdown on many-core machines with light linking
  • Fixed flickering of distant light sources with the adaptive lights and many light sources
  • Fixed slower adaptive lights with V-Ray Next compared to V-Ray 3.6
  • Fixed incorrect full light select element with VRayFastSSS2
  • Fixed -velocityAttrName parameter of ply2vrmesh not working for Alembic input files
  • Fixed resuming a bucket render resetting the progress to zero
  • Fixed artifacts with matte (matte for refl/refr = off) and adaptive dome light
  • Fixed super bright lens effects when using the NVidia AI denoiser
  • Fixed crash when enabling Bloom/Glare in the VFB while A/B compare is also enabled
  • Fixed bucket artifacts with adaptive lights
  • Fixed error with AI denoiser “Optix does not support cross-frame denoising”
  • Fixed DR may have watermarks if licenses are unstable
  • Fixed transparent objects with “cast shadows”=off rendering black when there is a VRayDomeLight behind them
  • Fixed “Direct visualization” option for caustics not working
  • Fixed aborting render after the last bucket skips saving img_file, keeping unfinished resume file

Misc

  • SamplerInfo Fixed Sampler Info relative coordinate system not working correctly

V-Ray GPU

  • Fixed crash when baking textures with GPU
  • Fixed wrong rendering of rounded edges in Next GPU
  • Fixed wrong Cryptomatte in animation with V-Ray GPU
  • Fixed Volume Grid crashes with VRayFastSSS2 on GPU
  • Fixed missing secondary reflections on CUDA CPU with Stochastic flakes
  • Fixed VRayClipper not working correctly with disabled clip lights geometry and dome light
  • Fixed buckets different in sampling (noise level) with bucket sampling enabled
  • Fixed unhandled exception loop on specific scene when rendering with IPR and turning off lights
  • Fixed wrong worldNormals RE for SSS material hits in V-Ray GPU
  • Fixed a crash when a V-Ray Fast SSS2 material is used inside a V-Ray Override material
  • Fixed wrong normals of VRayLight Plane in V-Ray GPU normals render element
  • Fixed hybrid rendering failing with AI denoiser
  • Fixed Environment ZDepth color not matching V-Ray CPU
  • Fixed crash on render end
  • Fixed DiffuseFilter render element for FastSSS2 rendered incorrectly with V-Ray GPU
  • Fixed crash with XGen

VRayLightSelect

  • Fixed Light select not respecting alpha of a textured light when the texture is constant

VRayProxy

  • Fixed crashes in proxy export of multiple meshes caused by missing UVs
  • Fixed crash when loading huge alembic file with many color sets
  • Fixed a crash when importing alembic with degenerate faces
  • Fixed XML material assignment file not getting transferred in DR
  • Fixed crash when opening a scene with alembic layers
  • Fixed preview bugs with multiple proxies with different settings pointing to the same file

VRayLightDome

  • Fixed error when using Resumable rendering with Adaptive Dome light

VRayMtl/VRayAlSurface

  • Fixed compositing with BlendMtl not matching Beauty

Viewport IPR

  • Fixed slowdown when Hypershade is opened
  • Fixed slowdown when the “Selection Mode” is set to “Box”

VRayMeshLight

  • Fixed artifacts with LightMesh and LightMtl with EnvironmentFog

VFB

  • Fixed Lens effects settings not resetting on a new scene

VRayScene

  • Fixed crash when V-Ray accesses UV-coordinates from an imported .vscene

 

V-Ray Next for Maya is available now at CAD Software Direct as a perpetual, monthly or annual license.

Should I Buy or Rent V-Ray?

Rent V-Ray

“Subscription” and “Rental” can sometimes be considered bad words when it comes to software, but they can actually be incredibly handy. Did you know that V-Ray, one of the most powerful and popular renderers for a wide range of industries, is available perpetually, annually and monthly? For example, if you’re looking to buy V-Ray for 3ds Max, but only need it for a few months, or don’t have the budget for the full license – you can rent V-Ray for 3ds Max instead!

Perpetual licenses that you pay for once and allow access to the software forever are nice and simple. If you’re running a business and a certain software package is essential to your daily operation, a perpetual license might make the most sense for you. V-Ray for SketchUp, V-Ray for Revit, V-Ray for Rhino and other “flavours” can all be purchased as perpetual licenses.

However, if you’re finding your software needs frequently change on a project by project basis, or your budget can’t accommodate for steeper upfront costs, it might be time to look into renting. If you decide to rent V-Ray, you can expect:

Lower Upfront Costs

Perpetual software often requires upfront investments which can be difficult for new and small businesses. Renting V-Ray instead would allow access to the software and a considerably lower cost.

Flexible Payment Options

Renting V-Ray would mean you only pay for it when you need it. It is easy to scale software access throughout your projects by adding and subtracting licenses temporarily.

Billing Back to Clients

Renting any software puts you in a better position to pass the cost of software access back to clients by including it as a part of your project estimate. In a way, this would make V-Ray an operating expense, rather than capital.

Bundled Upgrades

By renting software, you’ll be given access to the latest version, rather than the outdated perpetual license you bought years ago. Depending on the cost and frequency of upgrades, renting software could represent a better deal and longer term savings.

Most versions of V-Ray come either as a perpetual license, annual subscription, or monthly subscription. V-Ray Rendernodes are also available as an annual or monthly option.

The latest versions of V-Ray and V-Ray Next are available now at CAD Software Direct .com

V-Ray NEXT for Maya beta 2 Available Now

V-Ray NEXT for Maya

The second beta of V-Ray Next for Maya is here! GPU rendering has been updated with a smart new interface and V-Ray GPU IPR is even more stable.

This beta is open to anyone, and requires SSE 4.2 compatible processor. Get the latest build and let us know how it goes.

Download Now

 

Improved IPR in V-Ray GPU

Refine the look of your scene even faster with the real-time feedback of GPU rendering. In the latest beta, V-Ray GPU IPR is much more stable.

 

New GPU rendering UI

New V-Ray GPU user interface now only shows GPU-compatible features — making it easier than ever to use V-Ray GPU in production.

 

Toon shader improvements

Improved from beta 1, the new Toon shader adds new controls for inner and outer edge outlines.

 

New Hair Glints

New glint and glitter controls in the VRayHairNextMtl more accurately simulate the way light scatters in human and animal hair.

 

New V-Ray menu

Easy access to all your favorite V-Ray tools from one place.

 

For a full list of changes, check out the release notes.

RealFlow | Maya Available Now

RealFlow Maya

Now it is faster and easier to simulate granulars, viscous, viscoelastic, rigid, and elastic materials with an even easier and faster workflow. Achieve high-end GPU-accelerated simulations from inside Autodesk Maya by using the RealFlow | Maya plugin.

Following on from the popular RealFlow | Cinema 4D, Next Limit are providing a similar solution to other 3D applications commonly used with RealFlow. This plugin lets you create fluid simulations directly in your 3D platform, so there’s no need to leave your platform and break your workflow with importing and exporting.

It is compatible with Maya 2017-2018, and provides integration with native Maya tools such as nParticles and MEL. You can simulate all Dyverso particles and have the majority of RealFlow Daemons available to achieve high-end simulations.

To find out more, take a look at the RealFlow full product comparison.

Sign up for a free 30-day trial of RealFlow | Maya today or buy now at CADSoftwareDirect.com.

 

Phoenix FD for 3ds Max and Maya updates are available now

Phoenix FD for 3DS Max and Maya

Phoenix FD for 3ds Max now supports V-Ray Next for 3ds Max, and GPU rendering of Phoenix volumes. It’s also fully compatible with 3ds Max 2019.

What’s New?

  • RGB channel simulation for foam, splash and mist particles
  • Particle texture color based on particle channels
  • Loading and rendering of sparse OpenVDB caches over 2.1 billion voxels
  • 2x faster particle rendering in bubble, cellular and splash modes using the Phoenix light cache
  • Quicker displacement fade volume and body force with complex or moving geometries
  • Faster scene interaction with complex or moving geometries
  • For a full list of changes, check out the Phoenix FD for 3ds Max and Phoenix FD for Maya release notes.

If you’re itching to get up to date right away, you can download the update here.