Announcing the V-Ray.exe project

As there has been a lot of speculation regarding the fact that a new project has slowed us down and that we have abandomed our MAX customers etc I want to make something clear.

The people working on the VRAY for MAX have nothing to do with the EXE version. Not yet. Their top priority is the MAX version and their resources were not used for the making of this simple EXE project.

What do you meaaan! :cry: Could u write the string exactly as you would in Maya? Do it as an image if it doesn’t display properly as text. Thanks :sweat_smile:

Doh… Got it now ^^ Very exciting stuff, can’t wait til full support for Maya!

Maybe all should work on the Max version first? :wink:

Maybe all should work on the Max version first? :wink:

I don’t want to go into details, but history proves this to be very wrong.

:slight_smile:
excellent news very exciting…
HughG

Maybe all should work on the Max version first? :wink:

I would think working on a standalone version should be top priority, as the code and technology will then be directly beneficial to all users regardless of 3d suite. Give me one reason they should maintain several different evolutions of the same renderer for these different suites instead of one main, and focus only on the bridges to the suites as needed?
Why do some max users think they have more to say than others that work in a mixed environment?

trixian,
most max users will not benefit from a standalone version.
instead, we will lose support for 3rd party plugins and unsupported max features.
threads like “why are my RPC’s blurry?” will disappear, instead it will be like “where are my RPC’s?”.
look at mental ray…the connections are in development for years, and they still suck…except with XSI…
the only advantage i imagine would be the option to use linux systems for rendering.

Above all, the plugin system allows one to have constant model modifications and see the impact directly without having to import geometry and reset materials, stuff like that. I can it may not be that important in some practice, but for architectural vizualization, especially in the architecture competition context where the project changes a lot during the modelization procedure, and you only have a week to do three images, it’s very useful. I would definitely miss that and switch to another plugin.
I remember the old days with lightscape where we had to do that. Using GI plugins has been such a relief. It would suck if we go back 5 years ago and readapt our workflow to a standalone version that’s not FULLY compatible. The time gained in the rendering would be completely lost in the porting from max to the vray.exe program.

trixian,
most max users will not benefit from a standalone version.
instead, we will lose support for 3rd party plugins and unsupported max features.
threads like “why are my RPC’s blurry?” will disappear, instead it will be like “where are my RPC’s?”.
look at mental ray…the connections are in development for years, and they still suck…except with XSI…
the only advantage i imagine would be the option to use linux systems for rendering.

As I stressed above - MAX users will not lose anything, unless they want to render a MAX scene in MAYA or somewhere else. Please, do not mislead people with false information. The MR problems have nothing to do with V-Ray problems, so please, do not make wrong conclusions based on other products. MR architecture has nothing to do with V-Ray’s architecture, so the problems and benefits in both packages differ a lot.

sounds great peter. but you know you’ve just now thrown down the gauntlet. Alot of people will infer alot from your post. Since at the moment Im just a hobbyist, Ill just chill and see what happens, others that depend on vray for their jobs and livelihood, probably have cause for concern considering poor implementation of previous standalone renderers. Ive been waiting for this for quite awhile so that I can move on from max into packages that will better benefit me when I choose to become a professional.

peter,

noted…
i’m dying to see how you will work this out.
standalone version without the limitations of other standalone solutions?
sounds too good to be true. :smile:

I think this is a great announcement. It seems like the news out of Cebas may have forced an early reveal of this product but we all knew it was coming.

Can’t wait to give it a go. This is also one of the best reasons I can think of for getting up to speed on Maya.

V Miller

V-Ray standalone for itself - will have more or less the same limitations.

However, V-Ray for MAX that connects to the standalone - will not have those. The MAX connection will work with the satndalone and take care of all the MAX stuff.

But if you want to use V-Ray for MAX and render somewhere else, without having your MAX around - you will be limited as to what can be exported and what not. But we have a solution for some of the limitations as well. Anyway, its a bit too early to go into further details.

There is absolutely no reason why you should have to manually export and import scenes and models for a standalone version. In fact, I guess if the chaos guys feel up to it, they can design the architecture of the standalone version so any bridge coded by them or any 3rd party to max or maya will fit seamlessly in the native environment. Might have a few secontds more time at the beginning as you press the render button, and the bridge translates and parses the scene info to a readable format, but other than that I’d wager you could have an ui and workflow pretty identical to what you have now.
Or am I way off base here Peter/Vlado ?

hmm…where is my edit button?

A standalone version available for more renders than max is of course a smart move since you will have a far larger customer base. It’s also good to hear that not the same people are working on the .exe version. Good luck with it and looking forward to seeing renders done with Maya etc in the future.

/Andreas

Hi Peter,

Will it eventually be possible for someone like me to code their own interface to VRay.exe from Rhino or another modeler (such as FormZ)? I did this for another renderer using the Rhino SDK.

Hmm.. impressive.

~40,000 polygon object rendering in near realtime with ambient occlusion and raytraced shadows. Not to mention, antialiasing that doesn’t seem to increase the render time much.

Can’t wait to see what the future holds for this project.

[quote="trixianThere is absolutely no reason why you should have to manually export and import scenes and models for a standalone version. In fact, I guess if the chaos guys feel up to it, they can design the architecture of the standalone version so any bridge coded by them or any 3rd party to max or maya will fit seamlessly in the native environment. Might have a few secontds more time at the beginning as you press the render button, and the bridge translates and parses the scene info to a readable format, but other than that I’d wager you could have an ui and workflow pretty identical to what you have now.
Or am I way off base here Peter/Vlado ?[/quote]

I encourage the Vray people to look at the way Max has set up its DWG file link extension. I am modeling in FormZ, linking the file via extension into max, and rendering with Vray. In several instances I am using Vray as a standalone right now, with Max as the go between.

Something changes in my model. I change it in formz, hit update in max, and hit render in Vray. All of my textures, UVW maps, adjust automatically using the DWG file link.

Will I be setting up lighting and cameras in the Vray standalone version, or will this be handled by the app that I am using for the modeling?