Disappoint regarding SP1

[absolute3d]

I would like to comment the last update release for the 2.0 version of vray...

1) that release came out 1 month after the release of 3ds max 2012 (cebas final render was released the same day..like other plugins)

2) the cracked version came out BEFORE the official one..that's awful

3) there were no updates other than the compatibility

Those are just some points to let you improve the customer service, so i hope my words can make our life better

Cheers,
Thomas

[muoto]

I have to dissagree.
Vlado gave internal build if requested.
And v2 is quite new, so you cannot expect a new version every 2 months
And customer service is allready amazing. Are you able to discuss directly with the coders of Autodesk products ?

my 2cents

[stellwagenc]

1) then buy final render...

2) the crack is not SP1 - i think the crack is based on the internal build

3) no updates??? is this not enough?

Build 2.10.01 official (3 May 2011)
==============

New features:
(*) Separate VRayFlakesMtl material with just the flakes from the VRayCarPaintMtl material;
(*) Added VRayGLSL material for direct rendering of GLSL shaders with V-Ray extensions;

Modified features:
(*) The V-Ray RT render server prints out some more information in GPU mode (useful for troubleshooting);
(*) Added access to the V-Ray material override exclude list from MaxScript;
(*) Support for the four FumeFX render elements;
(*) Ability to call the "Calculate" and "Save to CSV file" operations on the VRayLightMeter from MaxScript;
(*) The "Browse" button for the "Split channels" file name now opens the folder with the currently selected name (if any);
(*) Added an environment override slot for VRayCarPaintMtl material;
(*) Added bump slot for the base layer of VRayCarPaintMtl material;
(*) Ability to turn off "trace reflections" for separately for each layer of the VRayCarPaintMtl material;
(*) Added MaxScript function, vrayEditDRSettings(), to open the DR settings window;
(*) Added possibility to specify user command-line options to 3dsmax.exe when started from the V-Ray DR spawner;
(*) VRayMtlID and VRayObjectID render elements now have an option to generate colors instead of integers for proper antialiasing;
(*) XML output for the VRayRenderID render element;
(*) MaxScript-only option "dome_visibleOriginal" for dome lights to control filtering of the light texture for glossy rays;
(*) Added an option to VRayToon to compensate the camera exposure;
(*) Ability to map the radius in VRayDistanceTex with a texture;
(*) Option in VRayDistanceTex for a solid inside color;
(*) Custom V-Ray materials now work in the Hair&Fur modifier;
(*) Hair&Fur now produces the same object ID as the emitter object;
(*) The V-Ray bitmap to VRayHDRI converter script did not take into account the input gamma of textures;
(*) Crash with particular pre-render script that turns off V-Ray lights before rendering;
(*) VRayBlendMtl material blocks the material IDs of its sub-materials;
(*) V-Ray RT: Added support for RPManager material;

Bug fixes:
(*) Noise with "Clamp output" option enabled produced noisy renders;
(*) Hilights from the base reflection layer of VRayCarPaintMtl material were darker than they should be;
(*) Slow rendering with many overlapping VRayProxy primitives;
(*) Randomly missing gizmos when rendering VRayEnvironmentFog;
(*) VRayLights that exclude an object could still affect that object through GI;
(*) Rendering with GI may use more detailed texture mip-map levels than necessary;
(*) VRayHDRI may not respect the specified memory limit for tiled textures;
(*) Crashes with particle systems with 3d displacement and motion blur enabled;
(*) Spikes with 3d displacement with "Keep continuity" enabled and particular bad geometry;
(*) Incorrect velocity element with VRayFur;
(*) Image copied from VFB to clipboard had the first column of pixels swapped for the last one;
(*) Loading an image in the V-Ray VFB with a different resolution did not work correctly;
(*) img2tiledexr used wrong formula when converting images from sRGB color space;
(*) vrim2exr did not preserve the pixel aspect information in the resulting .exr file;
(*) ply2vrmesh can convert RealFlow .bin files to .vrmesh files;
(*) VRayExposureControl was not accessible from MaxScript;
(*) Script error when there is a VRayPlane object in the scene;
(*) VRayPhysicalCamera in "Movie" mode was not exported correctly;
(*) Mesh lights were not exported with the .vrscene exporter script;
(*) Fringes on the edges of flakes in VRayCarPaintMtl material;
(*) Crash with VRayCarPaintMtl material when rendering of texture maps is globally disabled;
(*) Warning about "Retrace threshold" and "Use light cache for glossy rays" was printed even when not using the light cache;
(*) Exception after rendering when the "V-Ray raw image file" is chosen and the V-Ray VFB is not enabled;
(*) The V-Ray presets did not load if they were saved on a system where the decimal symbol is ",";
(*) The file save dialog for .vrimg/.exr files was not resizable;
(*) The VRayFastSSS2 material was not exported by the .vrscene MaxScript exporter;
(*) The VRayLightSelect element allowed the user to pick meshes instead of just lights;
(*) Incorrect velocity element when rendering Hair&Fur natively;
(*) The .dra file exported from the Hair&Fur plugin is now moved to the temporary 3ds Max folder instead of the root one;
(*) Wrong spelling for "affect specular" option in VRaySun;
(*) Slow rendering of VRayEnvironmentFog with animated Noise texture;
(*) V-Ray RT: Objects could disappear in animation;
(*) V-Ray RT: When used as production renderer, animation of deforming objects was ignored;
(*) V-Ray RT: Wrong exposure when physical camera type was "Move cam" or "Video cam";
(*) V-Ray RT: VRayEdgesTex was listed as incompatible with V-Ray RT;
(*) V-Ray RT: 3ds Max froze if V-Ray RT was working as an ActiveShade renderer and the user attempted to run V-Ray RT as production renderer;
(*) V-Ray RT: .vrscene export was not correct if the system decimal symbol was ",";
(*) V-Ray RT: When V-Ray RT was used as production renderer and max. paths per pixel was 0, it was always reset to 64;
(*) V-Ray RT: ActiveShade rendering is now paused when doing normal production rendering;
(*) V-Ray RT: Render restarted when changing a perspective view, even if the ActiveShade window was locked to using another camera;
(*) V-Ray RT: Scene was empty if motion blur was enabled;
(*) V-Ray RT: Problem with canceling batch render of animations;
(*) V-Ray RT: Adding new objects/lights is not reflected in the ActiveShade window in 3ds Max 2012;
(*) V-Ray RT: Standard camera FOV animation was not working;
(*) V-Ray RT: Support for the "Camera map per pixel" texture;
(*) V-Ray RT: ParticleFlow systems did not update when an animation with V-Ray RT as production renderer;
(*) V-Ray RT: Camera target distance was not updated correctly when rendering through Backburner;
(*) V-Ray RT: Issue with VRayLightMtl material inside a VRayBlendMtl material;
(*) V-Ray RT GPU: Textures for the color of VRayLightMtl material did not work;

[absolute3d]

I'm glad to see that i was thinking wrong about that, i have to admit it.

Cheers,
Thomas

[3ddesign]

Thomas, You'll find out that long time users are almost fanatically loyal to Vray and Vlado because they have treated us better than any software company I have ever dealt with, period. Can you imagine AwfulDesk CEO hanging out at the Area Discussions giving out as much free help as Vlado does? These guys are a rare breed and Vray rules.

Craig

[Dave_Wortley]

Chaosgroup also announced their intentions to switch to a release systems of Service Packs just being bug fixes, then a 0.5 release halfway through the year to bring some good new features to Vray.

We've always had an amazing amount for free in our Service Packs in the passed but now these will be in the .5 update, I think the .5 update is free and there will be some excellent features in this I'm sure.

[prateekvishwa]

thomas, you'll find out that long time users are almost fanatically loyal to vray and vlado because they have treated us better than any software company i have ever dealt with, period. Can you imagine awfuldesk ceo hanging out at the area discussions giving out as much free help as vlado does? These guys are a rare breed and vray rules.

Craig

i agree! During their visit to India i got a chance to meet Vlado. He & their team is superb!, Software 10/10, customer service 10/10

[Deflaminis]

There was a few updates, one of them cleaned up noise I was getting in dark areas quite well. I had an interior scene where I couldn't use pure black because it would get too noisy, and I had to darken all my black objects in post... that has also been fixed.

There's quite a few good things in this service pack. It's not uncommon for pirated versions of things to be available before the final release, just ask Microsoft. Ever OS they've ever made appears in the wild before in the stores. Think of it not as awful, but as a sign of how big you are getting. No one pirates Martha Stewarts Home and Garden... savvy?

Additionally, I worked at a studio briefly that pirated Vray for a few months (when I found out I quit) and let me let you, it does *not* work right. I would have to go home to fix scenes that seemingly changed settings at random at this job. Just because you saw it on some web site doesn't mean that version is working properly.

Vlado works pretty damn hard to communicate with us, answer posts, emails, debug scenes, etc. I don't think he deserved what you just gave him. I know I have bad days too where I like to bash Autodesk (and I feel bad afterwards) but Vlado and Chaosgroup deserve nothing but praise.

[absolute3d]

Yes, you have all right I check better what i saw before posting and wal almost all wrong

I agree with you guys, when you write that Vray and Chaosgrup are great, absolutely. In fact after entering the profesional field i decided to buy Vray instead of others engines

[stevesideas]

I have to say that Chaosgroup products and support including the user base are a great experience all round. The quality and support is fantastic and the forums always have someone able to help or at least try to. A number of other companies could do with taking a leaf out of their books.

[plastic_]

Chaos support is great.
There is a lot of value in the product, and I don't feel being ripped off, as with most other plugin developers sadly.
You get free recompiles and bug fixes, even for ancient max versions, what more can you expect?

[Deflaminis]

Yes, you have all right I check better what i saw before posting and wal almost all wrong

I agree with you guys, when you write that Vray and Chaosgrup are great, absolutely. In fact after entering the profesional field i decided to buy Vray instead of others engines

Not to worry, we all have our moments. You won't be sorry about buying Vray, because if you have any troubles we are all here to help you and so is the developer! Cool beans...

[muoto]

OK, almost forgiven, now just buy 10 more licences and you will be completely forgiven

[rajdarge]

I can't believe the amount of whining and carrying on in this thread. And why are we discussing pirate software here at all?
Support is sometimes sporadic, but always a shining light compared to other software that I own. Be thankful is all I can say.
Raj

[PsychoSilence]

The FumeFX Velocity render element doesnt work when wavelet turbulence was added. Is this a known issue? Can someone with 2.2 test please? 1.5sp5 here still. vector mblur is a big deal since vray doesnt blur the itnerna motion.