Tweet
example:
1. create and save a proxy of some object or other - after getting the materials mapped properly. save the sketchup file, say as 1.skp.
2. create and save a different proxy of a different object - after getting the materials mapped properly. save the sketchup file, say as 2.skp.
3. create a new sketchup file. IMPORT 1.skp, now import 2.skp.
The proxies are all mixed up - and what you see on the screen (the two proxies) is not what you get when you render (one proxy, rendered in two positions).
This is because the proxy import function applies a constant ID to the first proxy it creates. You can see this in the attributes for the proxy (use plugin Attribute Inspector). It always assigns the value "23" to the proxy. (Assets> <Asset renderer="vray" url="/23" type="geometry" layout="">....).
When v-ray goes to load the underlying vrmesh, it uses this value to identify which vrmesh to load.
This is a bug.
The fix? Manually edit the url="/23" to a random unique number. Voila - all is good.
Chaos - you should fix this.
While I'm at it, Chaos - for those of us using proxies extensively, there is also a huge amount of material proliferation that arises through the use of multi-material / child material constructs. It has two problems.
If one uses the purge function your material assignments are hosed and many critical materials are lost. If one doesn't use purge, you get a mess of duplicate materials in complex projects. There needs to be:
1. A fix for the purge function
2. A utility to merge identical materials.
3. A swap material function (load in a proxy, swap the default assignments to saved v-ray materials).
Small things - huge impact.
s.
1. create and save a proxy of some object or other - after getting the materials mapped properly. save the sketchup file, say as 1.skp.
2. create and save a different proxy of a different object - after getting the materials mapped properly. save the sketchup file, say as 2.skp.
3. create a new sketchup file. IMPORT 1.skp, now import 2.skp.
The proxies are all mixed up - and what you see on the screen (the two proxies) is not what you get when you render (one proxy, rendered in two positions).
This is because the proxy import function applies a constant ID to the first proxy it creates. You can see this in the attributes for the proxy (use plugin Attribute Inspector). It always assigns the value "23" to the proxy. (Assets> <Asset renderer="vray" url="/23" type="geometry" layout="">....).
When v-ray goes to load the underlying vrmesh, it uses this value to identify which vrmesh to load.
This is a bug.
The fix? Manually edit the url="/23" to a random unique number. Voila - all is good.
Chaos - you should fix this.
While I'm at it, Chaos - for those of us using proxies extensively, there is also a huge amount of material proliferation that arises through the use of multi-material / child material constructs. It has two problems.
If one uses the purge function your material assignments are hosed and many critical materials are lost. If one doesn't use purge, you get a mess of duplicate materials in complex projects. There needs to be:
1. A fix for the purge function
2. A utility to merge identical materials.
3. A swap material function (load in a proxy, swap the default assignments to saved v-ray materials).
Small things - huge impact.
s.
Comment