Jump to content

Vray for 3ds max 9 ?


volkane
 Share

Recommended Posts

VRay 1.5 RC3 for 3ds Max released

 

VRay news

 

Posted by Torgeir Holm [18.10.2006]

 

A new VRay build for for 3ds Max 8 and 9 (both x86 and x64 versions) has been released.

 

Image © VRay.info

Log in to your account on the chaos group site to download.

http://www.chaosgroup.com/support/

 

Build 1.50.RC3 (18 Oct 2006)

==============================

 

New features:

# Support for 3dsmax R9 32- and 64-bit versions.

# The V-Ray shading SDK is now a part of the V-Ray installation.

# Added "Guess vertical shift" button to the VRayPhysicalCamera.

# Added "Distortion type" for the VRayPhysicalCamera. The "Cubic" distortion type is used in programs like SynthEyes or Boujou and allows exact camera matching with these programs.

# Added an option "Invisible" for the VRaySun to avoid speckles on mirror surfaces.

 

Modified features:

# The DOF planes of the VRayPhysicalCamera match more closely the actual DOF effect.

# The V-Ray presets file name can now be changed from the default.

# Better memory management for large HDR maps in VRayHDRI.

# VRayLightMtl has an option to use an opacity map.

# The V-Ray converter script now supports the standard 3dsmax Blend, Shellac, DoubleSided and Architectural materials and converts them to the respective V-Ray counterparts.

# VRayMtl now can show the diffuse texture map in the viewport.

# The V-Ray license server is registered in "Automatic" service mode instead of "Manual".

 

Known issues:

# "Affect shadows" and "Affect alpha" options do not work for VRayMtl's inside a Multi/subobject material. This will be fixed as soon as possible.

 

Bug fixes:

# Hiding a VRayPhysicalCamera immediately after its creation did not hide the target.

# When cloning a V-Ray material or texture, any custom attributes were not copied to the clone.

# Particle Flow material IDs were not taken into consideration.

# VRayFur crashed when the source object did not contain a mesh.

# V-Ray could crash when saving a preset if the presets file could not be opened for writing.

# Some problems when creating a VRayLight with Dome type were fixed.

# Fixed a potential crash with the viewport display of the VRaySun.

# Using the light cache with crop/blowup rendering could cause a crash.

# The "%camera" keyword for the frame stamp did not work in the V-Ray VFB.

# The VRayLight in dome mode blocked shadows from VRaySun passing through transparent objects.

# In ppt mode the alpha channel for transparent objects was not correct.

# V-Ray now fills in all nodeID/mtlID/velocity render elements rather than only the first one.

# Replaced the '·' character for automatically generated UIs with regular '.' since '·' may be a special character on some versions of Windows (e.g. Japanese).

# The sub-materials of VRayBlendMtl did not show up in Track View; VRayBlendMtl did not allow wiring of the sub-materials.

# If a standard 3dsmax skylight object is present in the scene, V-Ray will print a warning and ignore it, rather than crash.

# VRayLanczosFilter produced black images with Fixed or Adaptive QMC at 1/1 image samplers.

# The renderer did not list environment maps and the override material as subanims.

# The irradiance map viewer would crash when merging maps from the command line.

# The dome light did not list its dome texture map as sub-anim for Track View.

# Crop rendering did not work in the V-Ray VFB.

# If the VFB resolution was different from the 3dsmax one, crop and region rendering rendered a wrong part of the image.

# Rendering will be aborted if an error occurs while writing a .vrimg file.

# vrimg2exr failed if -dataWindow option is specified and the image is empty.

# In some intermediate RC3 builds, V-Ray could take a render license when network rendering.

# Creating an un-targeted VRayPhysicalCamera and moving it crashed 3dsmax.

# The "Split render channels" option for the V-Ray VFB did not set the pixel aspect ratio for the resulting images.

# Renamed the "VRayShadow" render element to "VRayShadows" as the name clashed in MaxScript with the VRayShadow shadow type.

# Added an option "Invisible" to the VRaySun to avoid the bright speckles that may happen on reflective surfaces if a single hits the sun.

# Export to a .vrmesh file did not take edited normals into account.

# "Affect shadows" and "Affect alpha" options of a VRayMtl did not work if it was inside a VRayBlendMtl.

# A Falloff map in Shadow/Light mode caused some render elements (e.g. Diffuse filter) to be rendered incorrectly.

# If a render slave is used in DR mode and it does backburner rendering at the same time, the backburner 3dsmax crashed.

# The VRaySun "Size multiplier" produced wrong results when set to 0.0 or a very low value.

# RPC objects did not render correctly with the VRayPhysicalCamera.

# VRayWireColor element produced wrong results with transparent objects.

# VRayLight in Dome mode produced wrong results with matte/shadow objects.

# VRayLight in Dome mode could produce jagged results when visible and mapped with high-resolution HDR maps.

# Some of the new materials (VRay2SidedMtl, VRayBlendMtl etc) did not work properly when used as Override materials.

# VRayLightMtl did not work with VRayBlendMtl and VRay2SidedMtl.

# Using the frame stamp with "Full width" option off and "Center" or "Right" justify could lead to crashes.

Link to comment
Share on other sites

  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...