Hey wow. In my first test, the VRayInstancer kicked Multiscatter's ass for rendering a forest of 20,000 trees. The "Updating Instances" stage took a little while but in the end it was nearly twice as fast.
Announcement
Collapse
No announcement yet.
V-Ray 3.10.01 available for download
Collapse
X
-
...and upon further experimentation, if you use VRayProxys instead, you don't have to wait for the Updating Instances, but the render takes nearly twice as long. Still slightly faster than Multiscatter, though.
Anyone want to see how it compares to ForestPack?- Geoff
Comment
-
Wow, this is a nice update, loving it (esp. the new GGX Shader and overall rendering speedup).
I really would get my hands on that Chaosgroup logo scene with the ice material.
Vlado, is in this vast universe the smallest single possibility you would share it?
Thanks to Chaosgroup for this SP1 release; I regard is as a huge x-mass gift!
Cheers
Ale
Comment
-
Originally posted by reinaldo_handaya View Postyes it happened with me too, on vray 3.00.08.
Comment
-
Hey there, i can´t update right now, but I´m very interested in the Vray Instancer. Since I also couldn´t find the documentation for it, maybe you could answer me some questions:
I´m working on a scene right now, where I need to render about 100-500.000 Particles I´m scattering on the floor. The objects are around 500 verts each. But everytime I try to render, my memory starts maxing out and the render fails/crashes.
There is probably a way to limit the amount of particles to the ones actually seen in the camera view, but I´m not advanced enough in Pflow to do that...
So...
How does the instancer work?
Right now I´m using a shape instance operator in my Pflow, which is picking a group of different objects to scatter.
Can I use the Vray Instancer to achieve a renderable result?
Comment
-
Pflow was never properly updated due to autodesk being rather silly people and it hasn't been updated or optimised since the start. What you can do in pflow is in the very first event in your flow, there are options to choose how it calculates the geometry to render. You can dump out one large mesh for the lot, a series of meshes each containing a certain amount of polys, or a single mesh per particle. If you're got a shape instances with a lot of polys and tonnes of particles, trying to calculate one great big dumb mesh can be a bit nasty memory wise so it can be slow and somewhat unstable, mesh per particle can be a bit faster to process. The issue still remains that particle flow is generating a lot of mesh to hand over to vray who can then start to render the polys. With the vray instancer, you can keep your particles with no shape at all and just use the various transform, rotation and scaling calculations so it doesn't have to handle the geometry side at all. Vray is taking over in the generation of the actual polys and it can do this in a far more efficient fashion with everything being properly multithreaded. If you've got memory worries then you've the option of using proxys as the instance at the expense of performance, otherwise you can use normal geo as your instance and get lots of speed options. One caveat is that you lose the option of changing the shape of a particle in different events though no doubt this'll get added in as time goes on.
Comment
-
Yeah, Autodesk beeing slow is the main reason I´m spending so much time here in these forums...
I´m still not quite sure how the vray instancer handles geometry from my Pflow: Does it actually replace all shape instances with the according shapes, but as proxies/instances? Or do you have to pick one object (like a proxie) as an instance and tha instancer replaces all shape instances with that one? the later case would mean I couldn´t use it, since I couldnt´pick multiple objects as instances.
I already used the "mesh per particle" option,even though I don´t consider 500 verts "Hipoly", but still: 200.000x 500 verts is still a lot to process...
Comment
-
Originally posted by ben_hamburg View PostCan I use the Vray Instancer to achieve a renderable result?
Best regards,
VladoI only act like I know everything, Rogers.
Comment
-
Originally posted by ben_hamburg View PostI´m still not quite sure how the vray instancer handles geometry from my Pflow: Does it actually replace all shape instances with the according shapes, but as proxies/instances? Or do you have to pick one object (like a proxie) as an instance and tha instancer replaces all shape instances with that one? the later case would mean I couldn´t use it, since I couldnt´pick multiple objects as instances.
Comment
-
Originally posted by ben_hamburg View PostThat looks great...still not sure if I can use it to instance a group of objects and not just one object...
Comment
-
Hm. not sure if this would work then. Lets say I have a mParticles setup where the particles react to the surface and to each other, for that to work I do need some shape instances in there and as far as I have understood, the vray instancer wouldn´t replace the individual objects created by pflow with an instanced copy of those exact objects, but rather instanced random objects from that list. But I guess if I can live with no collision detection and just want to create the huge mass, this could work.
Comment
-
Originally posted by deneb26 View PostI really would get my hands on that Chaosgroup logo scene with the ice material.
Best regards,
VladoI only act like I know everything, Rogers.
Comment
Comment