DR slave renders with no texture

[puha0941]

Interesting test!

I found that whenever I write a vray proxy and then save it somewhere, open a new Rhino file and import the proxy into the file, the materials are gone and I get strange colors only.. Do you know why?

After playing around with the proxy, I've done some tests:
1. Render a scene (3 complex trees) as meshes
2. Render the same with proxy (importing the proxy correctly)
3. Render again with proxy but as adding the proxy as copy-paste from a different file
Results:
1. Heavy Rhino file (60MB) but rendered in 29sec
2. Light Rhino file (1.6MB) rendered in 45.3sec and having to relink materials
3. Light Rhino file (1.5MB) rendered in 42.6sec and no material ID issues

Great, the Rhino files difference in size are enormous though why is the render time almost double?
Anybody has any suggestions?

[fpedrogo]

I found that whenever I write a v-ray proxy and then save it somewhere, open a new Rhino file and import the proxy into the file, the materials are gone and I get strange colors only.. Do you know why?

This is normal. The proxy file doesn't support material information. What you can do is save the proxy as a Rhino file (3dm). In this way you will save all the V-Ray materials. If you want to use the proxy in other project, just import the .3dm file that contain the proxy.

Best

[puha0941]

Great! Thanks for the tip. Very smart way
Do you happen to know the offset issue between the vray frame buffer and the rhino viewport and the way to fix it temporarily?

This is normal. The proxy file doesn't support material information. What you can do is save the proxy as a Rhino file (3dm). In this way you will save all the V-Ray materials. If you want to use the proxy in other project, just import the .3dm file that contain the proxy.

Best

[fpedrogo]

Great! Thanks for the tip. Very smart way
Do you happen to know the offset issue between the vray frame buffer and the rhino viewport and the way to fix it temporarily?

This issue is on our bug list, but I'm not sure when we are going to fix that.
Best

[d77coll]

Regarding the material issue, 'fpedrogo's way is also the one I use. In fact it's useful to have a ready proxy library that you can just copy/paste the proxy from one file to the other.
Tip: I mark with a reference point (or line) the origin (and/or direction) of the proxy but do not include the ref. when writing the proxy as part of the proxy.
Then I group the proxy and the ref. This helps after to move the proxy in the 3D interface as you can snap on it and not on its vertex. (is there an other way?)
Ah, regarding the material ID: always copy only from the original proxy (or its own copies) but do not use the Import V-ray Proxy...

[Svetlozar Draganov]

After playing around with the proxy, I've done some tests:
1. Render a scene (3 complex trees) as meshes
2. Render the same with proxy (importing the proxy correctly)
3. Render again with proxy but as adding the proxy as copy-paste from a different file
Results:
1. Heavy Rhino file (60MB) but rendered in 29sec
2. Light Rhino file (1.6MB) rendered in 45.3sec and having to relink materials
3. Light Rhino file (1.5MB) rendered in 42.6sec and no material ID issues

Great, the Rhino files difference in size are enormous though why is the render time almost double?
Anybody has any suggestions?

Rendering with proxy will be always slower than geometry in the file - but it shouldn't be twice as slower.
Can you make one more test with and without proxy but this time try to duplicate this tree 1000 times - and track rendertime between proxy and non-proxy render.