Announcing the V-Ray.exe project

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 ?

You know, I’m not trying to complain, and I’m not scared, and if it works that way then fine, I’ll stick to vray. I just hope you are right. Maybe I didn’t undertand what a standalone means. I thought it was an external program where you have to import a file from another program to work on it JUST FOR RENDERING and not for modellisation, the way lightscape was working.

The only thing i don’t understand, is why there’s another one file format? Why not using RIB or MI standards?

Well…there’s couple of questions i got:

1. Maya 6.0 is current, but only Maya 5.0 available…i think it’s not so hard to recompile this plug-in for Maya 6.0?
2. What about multiple objects in single vrmesh file? Now it exporting only single selected object per file.
3. Types of geometry other then polys? Subdivision surfaces, NURBS, particles, renderable curves?
2. Current feature set is simply frightening…how fast you plan to add other ones?
3. Why proprietary file format, why not RIB or MI files?(asked previously)
4. Any plans to support some Shading Language in future?

PS: Little addition from me…it’s the script to export object from Maya and immediately render it…just don’t forget to setup VRAY_LOCATION env variable on you system, and just execute vray_export() in script editor:

global proc vray_export()
{
    string $cam = `getCurCam_j`;
    if ( !`size $cam` ) $cam = “temp”;

string $temp = `getenv “TEMP”`;
    if ( !`size $temp` ) $temp = “c:/temp”;
    string $fName = ($temp + “/” + $cam + “_.vrmesh”);

eval (“doVRayMeshExport -filename “” + $fName + “””);

string $vray = `getenv VRAY_LOCATION`;
    if ( !`size $vray` )
    {
        print ("vray_export(): Can’t find VRay.exe executables, probably VRAY_LOCATION environment variable is not set, exiting.
");
    }
    system ($vray + "\v-ray.exe -vrmeshfile " + $fName);
}

global proc string getCurCam_j()
{
    string $cam, $panel, $curCam;

$panel = `getPanel -wf`;
    if (`getPanel -typeOf $panel` == “modelPanel”)
    {
        $curCam = `modelPanel -q -cam $panel`;
        return $curCam;
    }
    else return “”;
}

Few minutes after that: Very funny to see how model shades interactively, tuning various parameters on-the-fly…maybe it’s worth to leave this mode for future releases? :wink:

Khm…i mean parameters like “sampling”, AO parameters, etc, i.e. ones, which usually can’t be visualised with IPR renderers.

You know, I’m not trying to complain, and I’m not scared, and if it works that way then fine, I’ll stick to vray. I just hope you are right. Maybe I didn’t undertand what a standalone means. I thought it was an external program where you have to import a file from another program to work on it JUST FOR RENDERING and not for modellisation, the way lightscape was working.

From what I understand, it will be somewhat like that, but not in the lightscape sense. It will be standalone in the mentalray/renderman sense.

Meaning, the rendering engine can be installed independently of the 3d application. That way, you can have a farm, and it doesnt matter whether you use maya or max for creating/sending jobs.

I love the idea of this.

I’ve been using sketch up more and more because I find it much faster than modeling in acad and or max. My only drawback is the clucnky method of getting it into max to render. The ability to be able to render a native skp file would be brilliant! I’m sure the people over at @last software would be more than willing to share code with the chaos coders

yeah I find that sketch up is growing faster and faster in the arch viz and design community…zI think it will become a contestant against major ups like viz/max in the arch community…so a port from sketchup to vray would mean that a lot of people wouldn’t have to use max/viz as a middle man :smile:

btw, great work peter and vlado :!:

paul.

//there are some simple rules to follow in skecthup modelling, (if u are going to render in other app)then you’ll have no problems with the exported mesh normals (mostly this is the problem)
But it doesnt mean it wont be cool for it! :slight_smile:

Still no luck getting the syntax right on the vray exporter for MAYA… I used this and got no luck:

doVRayMeshExport -filename “c:/temp/test.vrmesh”;

Anyone want to give me a hint? I even tried to reverse the slash…

Hope there be a C4D connection in the near future.

Behold the awesome power of Maya and VRay!!

Hehe, well it’s a start anyway. The interactiveness is cool to an extent, but the ability to hit a render button instead will be a nice option. It’s only crashed once for me which is pretty good really.

Oh, and a nice fix would be to make it that when you change resolution, the camera stays relative to the objects.

Great work guys!!

:wink:

don´t know what could be the reason, but im not coding a renderer. :slight_smile:

i love to see a working maya version! we use maya more and more.

this will be exiting months to come.
brazil in rhino and im pretty sure in maya too.

fR for maya.

vray for maya.

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.

correct.

and now thing about the missing DR in max 6!

how long will it take that a standalone rendere will support all new features when discreet and alias release new versions every 12 month?

how much time they have to spend on bugfixing for 2 different plattforms?

look at the delay of 1.5 we see right now.
do you think things will get better or worse when you have to support maya and max?

max has more third party plugin developer then any other 3d app.

do you think a standalone renderer will support all these third party plugins?

look at MR.
you can´t use 70% of the plugins you can use with vray, fR or brazil.

to make it clear, i love to see a maya version!

but i think that a standalone version has, beside all the positiv effects, also negativ effects. imo the specific support for an application will not be that good anymore.

to make it clear, i love to see a maya version!

but i think that a standalone version has, beside all the positiv effects, also negativ effects. imo the specific support for an application will not be that good anymore.

I asked before and I ask again - please - do not mislead people. I value your personal opinion, BUT, I did say the MAX support will not suffer - and I do mean it. We will still support eveything one has in MAX. The developement will not get slower. More people are joining the group.

ok, sorry.

but seeing renderman and mental ray i still have some fears.

i hope that it will work well but it´s a lot more work to keep vray up to date when you support more applications.

it´s not only the application, it´s also more plugins that need to be supported.

see…seee. :stuck_out_tongue: hehe. awsome stuff by the way. i cant wait to be able to export more stuff from our modeling packages like the cameras, lighting and materials (hehe i know thats a long way down the line)

ok, sorry.

but seeing renderman and mental ray i still have some fears.

i hope that it will work well but it´s a lot more work to keep vray up to date when you support more applications.

it´s not only the application, it´s also more plugins that need to be supported.

I do understand your fears, as history has shown most of this type of products to be problematic. I hope we can prove history to be wrong… again…

hey, ambient occlusion ? i want that, too in the advanced version. nono, i don´t mean skylight…