Request: Proxys

[SSmolak]

Wow this ProxSi is powerful and support Octane !

[fLuppster]

Octane has not any proxy support, it's probably same as our orbx loader system. Show me if you think that's different.

3ds Max - Octane Proxy = same size as the poly object
3ds Max - Octane Orbx = three times the size of the poly object

https://docs.otoy.com/3DSMaxH/3DSMaxPlu ... eProxy.htm

Hopefully we all agree, that there are proxys in Octane. So that would be such a great feature for the C4D version. Right now it is not possible to create really large scenes with Octane because of that restriction.

[aoktar]

Because it's not working as render instances. You can use C4D's render instances without full display in viewport.

[SSmolak]

Different size for Octane proxy and Orbx in 3d max is probably because orbx support only triangulated geometry

[fLuppster]

Because it's not working as render instances. You can use C4D's render instances without full display in viewport.

If you have tons of geometry in a C4D and display them as a box in the viewport, C4D will still be super slow, since the the geometry is still loaded.

The importance is to understand the huge advantages of real proxys. Geometry is not loaded in the scene and given to the renderer without needless ballast. Maybe you have a look at the Redshift proxy to understand what we are requesting? There you can load proxys in miliseconds, they speed up the viewport insanely fast and there is like no parsing for them. We are not talking about normal viewport optimization like "show as box" or "use renderinstances". :/

[SSmolak]

But if you use "render instances" only one copy of object is loaded into memory - the rest are instances But I know that in specific situation where are tons of objects like different hi-poly cars in large scenes even these one-copy objects can be slowly to operate.

Another thing is that Cinema instancing system is very slow compared to Octane Scatter.

[fLuppster]

But if you use "render instances" only one copy of object is loaded into memory - the rest are instances But I know that in specific situation where are tons of objects like different hi-poly cars in large scenes even these one-copy objects can be slowly to operate.

Yes of course. Doesn't matter if you do this with Polys, Proxys or Orbx. That is not what i am talking about. I am talking about to get high poly geometry into C4D via proxys. And not just one of them and make 10.000 copies of it. You can obviously do that without losing VRAM.


I am talking about to have 10 different trees with 2 mio polys each. If you do that with normal polygon models, you can not handle Octane anymore. With Proxys (in Redshift for example) this is not even a big deal. Because the proxys work very good there.

[SSmolak]

Right, this is why real proxies are very important.

[fLuppster]

They are not just important, they are vital if you want to create real environments. And most ArchViz artists want to do exactly that. So... no chance of real proxys in C4D Octane? Can't do projects with Octane then. Meh..

[SSmolak]

It seems that all assets must be loaded before using them as instances. This is of course wasting huge amount of resources.

In my tests adding Orbx doesn't increase Vram but they doesn't work with multi-instances, only render instances so with huge amount of them Cinema can be very slow even while disabling them in viewport. The Orbx simplified point-cloud preview doesn't work with render instances and multi instances