Hello! I’m working on a scene in which there is vegetation, the scene is a bit heavy but it works well. Now it turned the trees into proxies and it’s impossible to render; compiling geometry and loading bitmaps. I’m not a great expert on proxies but they have always worked well for me. I still have a lot of vegetation left to include in the scene and at this point I can no longer work with the proxies.
I am working on R21 and with 7.00.01.32953
Thank you!
Hey, Juan
Thank you for the report. I am not sure how you are using a proxy with a cloner or scatter, but here are some workarounds to speed up your render time: 1/ If you are using it with a cloner, please change the instance mode to Render or Multi-instance mode. 2/ If you are using with scatter for now convert the proxy to editable geometry.
Cheers,
Hello Boyan, thanks for the quick response. I am using Scatter and I have converted the proxies to editable (with the C key? is OK?) and now I can render.
My question is, what is the difference between using the edited proxies or using the objects directly? Isn’t it the same? Or is it better to make proxies and then edit? I’m a little confused. I’m sorry but I’m not very expert using proxies for forests and things like that.
Thank you!
I’ll tell you something else that may be important:
The proxies that are giving me problems are the ones I have made myself from Maxtree, but if I use a grass proxy from Cosmos it renders without a problem.
When I make the proxies I leave the default values and I have never had any problems, but maybe there is something I am doing wrong that affects when there are thousands of pxoys in the scene
Hey @Juan_Ferreira , there is currently a known regression when Scatter is used for V-Ray Proxies or Cosmos assets. We are currently working on a fix, but in the meantime, to workaround this issue, you can use a simple Cinema 4D instance object (in render instance mode - referencing the proxy) and use it as the scattered object. Sorry for the inconvenience this causes - we will write here once the fix is available.
Hey, Juan,
We have logged the issue in our bug-tracking system and expect soon to be in the stable branch. With Scatter, converting to editable geo is the easiest way. Meanwhile, you can use a more procedural workflow with the Cinema instance and set it to Render Instance.
Cheers,
Thanks Boyan, thanks Deyan
Hey, Juan,
The fix is added to the latest stable so you can render with cosmos assets or proxies as well.
Cheers,
Great! I Will try. Thaks!