Vray 1.5 R4 Demo only in download section

[neoVisual]

Hello, I just noticed that brand new build with many important bug fixes is available, but it is only DEMO and shows Vray signs all over the rendering. Do we have to sign some different way for R4 version ?
In the support section there is still only R3 production version for download.

Many thanks for bug hunting, Vlado, can you tell us when and how there will be production version of R4 ?

thanks, neovisual

[GregM]

That does seem odd... have they done that in the past?

[instinct]

Yes they have if i recall right.

Thorsten

[neoVisual]

No, it is quite unusual for me. That is why I am posting about it. New version is fully functional version 1.5 R4 with many bug correction and with all announced improvements, so thanks for that.

It just renders Vray logo and watermarks over the rendered image like Vray free version I guess.

see for yourself

neovisual

[GregM]

I would think that R4 will be posted soon

[instinct]

That has been like that for earlier Builds too. RC2 was available as Demo earlier too for example.
See here:
http://www.chaosgroup.com/forum/phpB...light=rc1+demo

Regards,
Thorsten

[neoVisual]

OK, from the previous posts I assume that either new build will be released some time after the DEMO (time is not specified), or we have to send some mail to Chaosgroup and they will add full version to our download page. Is that so ? Isn't it complicated a bit ?

I just want to know some date when we can use R4 version, because our studio is delaying transition to 1.5 version due to major bugs in R3 version.

thanks for understanding

neovisual

[DaForce]

Its rather simple. It will be out when it is.. probabaly soonish.

And there WILL be an annoucement about it. Until then wait
There is always an announcement when a new build is properly release.. just wat for that.

[RErender]

well it is pretty frustrating that the demo is out before we get it, not sure I really understand that bit. But yeah I expect it will be out soon.

anyways until we have look at what is new and fixed (Vlado's been busy ):

New features:
(*) New render elements: VRayMatteShadow, VRayTotalLighting, VRayRawTotalLighting.

Modified features:
(*) Updated WIBU-key drivers for 32- and 64-bit Windows* (including Windows* Vista*) are included with the installation;
(*) VRaySun is now compatible with the 3dsmax Daylight system and can be selected as a sun type;
(*) VRayDisplacementMod now supports high-dynamic range textures for displacement in "2d landscape" mode;
(*) VRayPhysicalCamera supports horizon line in the viewports, clipping and environment near and far ranges;
(*) Distributed rendering can now be started as a BackBurner job;
(*) VRayColor texture has an option to apply gamma correction to the displayed color in the UI;
(*) "Don't affect colors" option for color mapping; useful if you only need the sampling adaptation to be performed;
(*) "Cutoff" threshold parameter for VRayLight's allows to reduce render times in scenes with many weak lights;
(*) "Envrionment priority" option added to VRayMtl to control environment override behaviour between different materials;
(*) Options for directly controlling the render mode (region, crop etc) of the V-Ray VFB;
(*) "No GI on other mattes" and "GI surface ID" parameters added to VRayMtlWrapper;
(*) Matte objects with the "Shadows" option checked will now generate VRayRawLighting, VRayRawShadow and VRayMatteShadow elements;
(*) If "Check for missing files" option is checked, DR will now fail on the render slaves if some maps cannot be found, instead or rendering wrong buckets;
(*) If there are several VRaySun nodes in the scene, VRaySky will now pick the first one that is enabled (rather than the first one at all);
(*) V-Ray will now force multithreading when 3dsmax is in slave mode, regardless of the 3dsmax multithreading option;
(*) When rendering to texture (RTT) the 3dsmax VFB is now always generated, regardless of whether the V-Ray VFB is on or off;
(*) VRayFur can now generate motion blur with more than 2 geometry samples;
(*) The irradiance map viewer will print out the progress of merging irradiance maps;
(*) The autosave file names for irradiance/light cache/photon/caustics maps are now updated at each frame, rather than only at the render start;
(*) The irradiance/light cache/photon/caustics maps are auto-saved as soon as they are computed, rather than at the end of the frame/rendering;
(*) The "Save maps per frame" option has been removed from the GI rollout;
(*) VRayProxy will now re-link the .vrmesh file at each frame, rather than only at the render start;

Known issues:
(*) When rendering a 3dsmax Raytrace material applied on VRayProxy objects, V-Ray will crash;

Bug fixes:
(*) "Affect shadows" and "Affect alpha" options did not work for VRayMtls inside a Multi/subobject material (RC3 bug);
(*) Moving VRayPhysicalCamera caused spurious MacroRecorder events about the target distance changing;
(*) Problems with 2D displacement (RC3 bug);
(*) Automatically created VRaySky did not have a name;
(*) Horizontal scrolling problems with the V-Ray messages window;
(*) VRayOverrideMtl could cause 3dsmax to crash;
(*) Multi/subobject material inside a VRayBlendMtl etc. did not render;
(*) 64-bit V-Ray could fall into an infinite cycle when rendering 2d displacement;
(*) Some rare raycaster precision errors were fixed;
(*) Starting/finishing rendering could be extremely slow in 3dsmax R9;
(*) VRayHDRI always took at least 10 MB of memory, regardless of actual image size (RC3 bug);
(*) Incorrect irradiance map density and texture sharpness when using camera clipping planes;
(*) Missing files (textures/VRayProxies etc) were not always detected correctly;
(*) Distributed rendering between mixed 32/64-bit V-Ray versions did not work properly;
(*) Standard materials with transparency did not render properly (RC3 bug);
(*) No motion blur for ParticleFlow on 64-bit 3dsmax;
(*) Color corrections from the V-Ray VFB were applied to the alpha channel when splitting the render channels to files;
(*) Crash with the "Show map in viewport" option for VRayMtl when using Direct3D (RC3 bug);
(*) Textures with mapping channels greater than 1 are now correctly shown in the Material Editor;
(*) The "Global light level" options from the Environment dialog now affect the color of VRayLights and standard 3dsmax lights;
(*) VRayBlendMtl did not list the blend textures as sub-anims;
(*) If "Render to raw image file" option for the V-Ray VFB was ON, but the file name is empty, V-Ray would freeze while rendering;
(*) The parameters of VRayMtlWrapper did not have proper names in Track View;
(*) If the primary GI engine was light cache or photon map but GI is turned off, standard materials would render black;
(*) VRayMtl materials with low glossiness inside a VRayBlendMtl could produce polygonal artifacts on shadow/light boundaries;
(*) The pixel aspect ratio from the Render Scene dialog was ignored when rendering with DR to the 3dsmax VFB;
(*) A low-dynamic range 3dsmax frame buffer was used even when saving to a high-dynamic range file format (.exr, .hdr etc);
(*) Problems when rendering animations in DR mode with light cache as both primary and secondary engine;
(*) Small rectangle area lights could produce artifacts for points lying close to the light plane;
(*) Somewhat better memory management for proxies and dynamic meshes;
(*) Crashes with VRayFur on animated objects when using motion blur;
(*) Incorrect environment color with several VRayLights in "dome" mode;
(*) "Crop" render mode with the V-Ray VFB did not work for animations;
(*) Sporadic crashes when using the "Camera Map Per Pixel" texture inside V-Ray materials (VRayMtl, VRayLightMtl etc);
(*) VRayBmpFilter did not always display its bitmap texture successfully;
(*) VRayBmpFilter could produce invalid colors;
(*) Photon mapping could produce wrong GI on transparent surfaces;
(*) Crashes with interpolated glossy reflections/refractions if there is only 1 sample in the interpolation map;
(*) Irradiance map produced incorrect results when used with VRayLight in "Light portal" mode;
(*) Faceting on low-poly geometry when using anisotropic reflections with UV-channel mapping;
(*) Incorrect sampling with gamma color correction when some of the pixel RGB components is zero;

[DaForce]

hahah cool my 2 bugs made it into the fix list.
(*) Automatically created VRaySky did not have a name;
(*) Horizontal scrolling problems with the V-Ray messages window;

Sure there not exactly show stoppers.. but still
Then 2nd one had apparnetly been around since early 1.09 days atleast.

[MegaPixel]

Well I'm excited. I hope we hear something about the new release shortly. Thanks for the heads up Eric

[jacksc02]

compiling the build with the installer and the sdk and all the extra tools takes some time, so be patient

[vlado]

The R4 demo was somewhat rushed out; there are a few things more that we wanted to do for the official RC4, but we were pressed to get the demo on the site. With that said, the final release is nearly done.

Best regards,
Vlado

[bluescreen2]

rc 4 sounds really good. nice work.

[priad]

Always the same song:
We want the last, we want the last, please, please, please, please, hehehe
We have seen the last in some render window stamp etc ....
funny thread again