Orbx Proxy vs. Rhino block

[v-cube]

Hello Paul,

In my projects I would love to use more orbx proxies, e.g. I hope they will help me to unclutter my material editor .
When I import a complex object like a car, I often end up with more than 20 extra materials, now lets say I need 5 different cars, 20 people , trees and so on ... you probably get the idea....

When I use an orbx object these materials do not appear on my material editor , which would make my life a lot easier.

However I have two problems, which prevent me from using the orbx proxies at all:

1. In contrast to the normal blocks the orbx proxies take much, much more time to load when I hit render, I think the time until I see a picture is sometimes 5 times longer, depending on the scene and the size and amount of proxies used of course. -> is there any chance this could be changed?

2. If I make copies of the block containers that have proxies assigned to them, I always have to use the replicate function to make them appear in the render window. This is a little cumbersome and can also take ages even for moderate numbers. Large numbers are so slow that it feels like rhino is freezing so it cannot really be used for grass or trees ...
-> can this be improved ?

If you want, I can create a test setup scene tomorrow.

Thank you for any feedback

Best regards

Andreas

[face_off]

1. In contrast to the normal blocks the orbx proxies take much, much more time to load when I hit render, I think the time until I see a picture is sometimes 5 times longer, depending on the scene and the size and amount of proxies used of course. -> is there any chance this could be changed?

ORBX proxies are being individual loaded for each block instance - so the same proxy is loaded multiple times. I will fix this in the next release.

2. If I make copies of the block containers that have proxies assigned to them, I always have to use the replicate function to make them appear in the render window. This is a little cumbersome and can also take ages even for moderate numbers. Large numbers are so slow that it feels like rhino is freezing so it cannot really be used for grass or trees ...
-> can this be improved ?

It may be possible to streamline this process. If you can put together a sample scene which has a long Replicate time, I can take a look.

Paul

[v-cube]

If you can put together a sample scene which has a long Replicate time, I can take a look.

thanks Paul , I send you an PM...

[face_off]

The reason the Replicate takes so long to run is because it is loading and voxellising the ORBX proxy for every block instance. I will resolve this for ORBX/OCS proxies in the next release, but it will need to stay the way it is at the moment for OBJ proxies.

Paul

[prehabitat]

I love this stuff; so responsive!

[v-cube]

The reason the Replicate takes so long to run is because it is loading and voxellising the ORBX proxy for every block instance. I will resolve this for ORBX/OCS proxies in the next release, but it will need to stay the way it is at the moment for OBJ proxies.

Paul

That is supercool ! I would not have dared to think that it would be fixed so fast -> thanks !
For the obj. support: I personally do not use this anyway...
If you can also try to speed up the replicate process, this could be a real gamechanger for my 3D library management !


best

Andreas

P.S. on more (small) thing: when I hit the "load orbx" button on the geometry tab to assign an orbx to the block, the default file is set to "*.ocs" ... this is a bit confusing , could you please make the default file type *.orbx or make it so that both orbx and ocs are displayed and accepted ?

[face_off]

P.S. on more (small) thing: when I hit the "load orbx" button on the geometry tab to assign an orbx to the block, the default file is set to "*.ocs" ... this is a bit confusing , could you please make the default file type *.orbx or make it so that both orbx and ocs are displayed and accepted ?

Will do.

Paul