3.60.03 + Forest pack pro bug still not fixed

[ILS]

I wrote about this bug since version 3.5 came out and this still hasn't been fixed.
Was there any progress or suggestion from the development team with regards to this issue?
Using max 2018, Forest pack pro 540 and vray 3.60.03.

[Svetlozar Draganov]

It turned out that this is not be a bug but not very well made change from our side.
In version 3.x a new parameter has been introduced to V-Ray Proxy, it's initial name was One Voxel Per Mesh which later was renamed to Optimize For Instancing.
This option is enabled by default when exporting new proxies but all the already exported proxy files from earlier V-Ray versions like 2.x for examples doesn't have it enabled.
Because of that and the changes in version 3.x V-Ray needs more time to unload memory at the render end, this becomes extremely visible with lots of proxies.
As for now you can fix that slowdown by re-exporting V-Ray proxies with Optimize for Instancing option enabled, for the future we might find a more elegant way to handle proxy files created with earlier V-Ray versions.

Would you please test on one of your scenes the above tip and let us know if the unloading times at render end are reduced?

[anthonyh]

What about scenes where we have no control over the original proxies i.e from turbosquid etc ? are they just at the mercy of whether the original user decides to update it ? What if it doesn`t make financial sense for them to do so because of the time involved. We use Multiscatter would this also be affected ? (sorry if it`s off-topic)
anthonyh

[Svetlozar Draganov]

Probably every scattering plugin including Multiscatter will be affected if that's the case. Let's first anyone confirms that the slowdown is indeed caused by that option, we do not exclude other possibilities.
Like mentioned above we'll try to find a way to solve this without the need of user input.

[ILS]

Thanks Svetlozar,
We will check that. Hopefully that works.

[ILS]

What about scenes where we have no control over the original proxies i.e from turbosquid etc ? are they just at the mercy of whether the original user decides to update it ? What if it doesn`t make financial sense for them to do so because of the time involved. We use Multiscatter would this also be affected ? (sorry if it`s off-topic)
anthonyh

you can always convert proxy back to mesh and convert back to proxy using this option, this is probably the method we will have to use, most likely we will write a script to automate that if this is indeed a solution.

[ILS]

It turned out that this is not be a bug but not very well made change from our side.
In version 3.x a new parameter has been introduced to V-Ray Proxy, it's initial name was One Voxel Per Mesh which later was renamed to Optimize For Instancing.
This option is enabled by default when exporting new proxies but all the already exported proxy files from earlier V-Ray versions like 2.x for examples doesn't have it enabled.
Because of that and the changes in version 3.x V-Ray needs more time to unload memory at the render end, this becomes extremely visible with lots of proxies.
As for now you can fix that slowdown by re-exporting V-Ray proxies with Optimize for Instancing option enabled, for the future we might find a more elegant way to handle proxy files created with earlier V-Ray versions.

Would you please test on one of your scenes the above tip and let us know if the unloading times at render end are reduced?

That did the trick with our problem test file.
It would be nice to have a tool that would convert old proxies to these new ones with that option enabled. Is this option like a metadata in the file or is the mesh created with this option on somehow different from the one created without it?

[anthonyh]

you can always convert proxy back to mesh and convert back to proxy using this option, this is probably the method we will have to use, most likely we will write a script to automate that if this is indeed a solution.

Doesn`t seem to work for animated proxies ? or am I doing something wrong ?

[ILS]

Doesn`t seem to work for animated proxies ? or am I doing something wrong ?

You might need to write animated point data to a point cache first then collapse your proxy to mesh and apply that data back on top and then make a new proxy. Haven't tried but that seems like it should work.

[KiboOst]

Does we have to convert back all our proxies (thousands of assets...), or could we have a setting that apply this instancing optimize setting to old proxies ?

[anthonyh]

Hmm, sounds like it might take a while for many objects, `time vs cost` and i`m no scripter to automate it. As ILS and Svetlozar said I think it would be nicer if vray had something to sort it since the proxy change has caused it. Here`s hoping.