New beta release when ?

[SaadUrRahman]

New beta release when ?

You should be using the defaults settings and then tweak based on how tight/small your fillets and edges are, at least this is what I do...


/BlueShift

[Paul Oblomov]

New beta release when ?

I'm not the new one to Rhino. . .

Can you tell me how's Vr f Rh tesselation work?

[flipside]

New beta release when ?

There is no vray for rhino tesselation. Tesselation is based on the rhino settings, it has nothing to do with vray.

[Paul Oblomov]

New beta release when ?

If it's based on Rhino settings . . .

tesselation is based on

- you mean vray tesselates NURBS anyway ?

We need developers say smth.

[flipside]

New beta release when ?

Ok I'm really not following anymore.

Let's say you install rhino without any plugin. You draw some objects and you turn on shaded mode. Rhino now converts the nurbs into polygons (the collection of polygons is called a 'mesh'). The conversion from nurbs to mesh is called 'tesselation'. When you hit render, rhino uses this same mesh from your viewport to render the image. When you save, the mesh is stored in the file. (except when you hit 'save small')

Now you install for example a render plugin, for example flamingo. Flamingo also uses this mesh for its rendering process. The mesh creation is a rhino setting, it is not related to whatever render plugin you may have installed.

Same for vray for rhino. The render mesh is the same as in example 1, there is no special vray for rhino mesh, vray uses the mesh created by rhino to render. So you set your tesselation settings in the rhino properties, there are no vray settings for tesselation!

Between the mesh creation and the actual rendering, something else is happening, which is displayed by the 'building scene' message in the render window status bar. This is an optimisation to speed up rendering. It divides the scene into regions of x amount of polygons and all kinds of other stuff so that rendering can start as efficient as possible (to figure out which parts of the scene contains the most ploygons, or to see which objects get blocked in view by others, etc...). This process van take some time and it takes longer of course if your scene contains more surfaces.

That's why the mesh settings are so important.

Sorry if you knew all this already, the main point is that there is no vray tesselation going on. I guess all this is just a confusion of terms (tesselation/mesh/building scene/...)

[Paul Oblomov]

New beta release when ?

Tesselation is "building MESH from NURBS for render" (it may be viewport render or whatever). When Vray starting to "analyze" scene, it makes Accel. Tree, where polygons (triangles) are divided in blocks (it may be 4x4 or smth) for raytracing or whatever!

Why Vray for Rhino so slow, comparing Vray for 3dsMax. Why processing mesh (objects) in 3dsmax lasts several seconds (not tens of minutes) and after those seconds render process is starting, but for VRay for Rhino pre-builded mesh (we're already knew that) reads so long?! Why there's so big difference in time ?!

It's the question I asked first, in my post!

[flipside]

New beta release when ?

Well in max, your objects are also already meshed also in the viewport. The optimisations will not go quicker because of that.

But in max, the mesh has usually much less polygons than in rhino. The rhino mesh settings create a lot of polygons, it is not efficient at all. So if you import a complex iges model into rhino, and use the preset mesh settings, rhino will make extremely lot of polygons. Maybe that causes the delay in 'building scene'?

Also note that this is an early beta, and the asgvis people already said in one of the posts that they are working in this problem.

BTW the question in your first post was about tesselation taking place multiple times. This is not the case. The analysing part happens each render again (acceleration tree), but not the meshing itsself.

[Paul Oblomov]

New beta release when ?

Well, I noted already, that this is an EARLY beta
Just got missed

that they are working in this problem

.

P.S. Try to export ANY Rhino object to Max. There's as much polys, as you need to! And I can't agree that max mesh (imported from rhino) is much lower on polys.!. IGES - it's a native NURBS data.

O.K. if it does start anytime I render - why it's so slow?

BTW the question in your first post was about tesselation taking place multiple times. This is not the case. The analysing part happens each render again (acceleration tree), but not the meshing itsself.

Pardon me. I might not mmmm ... damn... I meant smth another

[flipside]

New beta release when ?

Ok to finalize, I agree that the building scene thing takes longer in vrayforrhino than in vray for max

But give them some time to take a look at this problem.

For now, just believe that the reason for the slow down is because this is an early beta.

Meanwhile, don't render scenes with thousands of objects

All the renders I put in the gallery took 5 to 15 minutes (except the appartment scene) and the building scene was never longer than 1 minute.

Don't know what kind of models you're trying to render, but start with simple things for now and apply materials to these simple things, you will find more bugs that way.

You can also use very coarse mesh settings while test rendering to reduce the building scene time.

[Paul Oblomov]

New beta release when ?

Heh

Never told, that I blame devvelopers for this.... mmm slowdon. Just never read their comments on this

Tell me, how much surfaces and polysurfz you got in your the most complex scene ?

155 min for me (1k surfaces) - you saw it in gallery

BTW - can't render closeups with coarse set-z.

[flipside]

New beta release when ?

Which render took 155 minutes?

[Paul Oblomov]

New beta release when ?

DAMN!!!!!

Not min=minutes

155 POLYSURFACES minumum
(155 min for me -=- 155 polysurfz MINiMUN TO ME)

[flipside]

New beta release when ?

Ok

That latest hifi thing are 28 polysurfaces, made up from a total of 2485 surfaces (all small fillets etc...)

[Paul Oblomov]

New beta release when ?

Well done!

But... damn it's a flood.

CYpm

[joe_b]

New beta release when ?

Sorry it took me so long to post on this one. There is an ENORMOUS slowdown caused by my idiocy. I was doing things rather stupidly when sending the render mesh to vray. So that slowdown is 90% my doing. This is all resolved now.

Just to clear up the flow of geometry...

Rhino NURBS->Rhino Render Mesh-> VRay For Rhino PlugIn -> VRay

Rhino tessellates its NURBS for me and gives me the Render mesh. But what I was doing with it was slowing it down terribly, sorry, next build will not have this problem.