Hi,
I have an issue with instancing VRay proxies (alembic files).
I’m creating 100.000 instances with Mash using the standard Instancer (not Repomesh).
When motion blur is disabled, the translation time is 5x longer than when motionblur is enabled.
It seems like the slowdown is happening when VRay is building the “Embree static trees”.
I have attached a debug scene, with an alembic proxy of a highres helix.
https://drive.google.com/open?id=1u-…N6-zwnk5yumbi6
--
Jacob
Thanks for the files, we’ll have a look.
What’s the V-Ray and Maya versions and the OS?
Also is this the regular V-Ray or V-Ray GPU?
We’re using VRay 4.3 for Maya 2018 - Linux. We have tried a few different nightlies. Same result.
We are rendering with regular V-Ray, not GPU.
--
Jacob
This is one of our biggest sore points when working with VRay, time to first pixel can be painfully slow. I only recently did an Arnold job that required dense jungles, which opened my eye on how slow this is in VRay.
David.
Any update on this?
We’ve spent some time profiling the scene and we’ve identified where we can make improvements to speed things up.
We’ve already done some optimizations and we can further improve things in the future.
Any changes, however, will not be compatible with the latest available version (Update 2), so they will have to be included in future releases.
Thanks for the reply Yolov,
Does this mean that these changes with be part of the Proxy 2.0 loader, or what do you mean about it not being compatible with the latest version of Vray?
This is completely unrelated to proxy 2.0. The changes that improve this case are mostly in the translation of the scene. They are not compatible to port to the latest available release (4.3) as they rely on many other changes introduced since then, which have the potential to break a lot of things, if ported. This is why we’ll have to include it in the next release.
Will these changes be available in the nightly releases of Vray?
At some point - yes, but it’s hard to say when.