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 ?!
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.
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
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.
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.
I think this is mainly a language issue here. Altough he has a strange way of expressing himself
He answered the question Paul, in the next build it will also only last a few seconds, just like in max. Then you can be happy again and start adding materials to your scenes.
The fact that you shade your viewport has nothing to do with the raycaster calculations. In max your viewport is also shaded and vray for max also uses a few seconds to calculate raycaster thing.
heh, I’m sorry if I seemed rude, I assure you that I really was just mad at myself for making such a mistake. I’m sorry if you felt insulted by my post, but I am not mad at anyone, and you don’t need to apologize to me. Its ok! =)
