Vray 2.0 Proxy issues
-
Hello,
I am new to working with Proxies. On Friday I created a few proxies of a gabion and built a wall with them. Unfortunately, I lost that file. I recreated that same file today, but my file is huge! Each proxy file is 1.8M and my file with the wall is 13M. Also, I had to copy the proxy from the original that i had created. When I use the import function, the move tool appears and tells me to place the proxy, but no matter where I click nothing shows up. If I go to the component window afterwards, I can see the proxy, but I have the same issue when I try to place it.
Thanks in advance for any help!
-
Hi Amanda,
I've run into some issues with materials missing in some very large proxy files, causing errors in loading the proxy back in. If you can, you should send an email to support with information about your setup. If the file is large, I'd suggest using a file transfer service (like dropbox) to send your file to them.
Andy
-
Chaos group told me that the importing and placement of proxies is a bug they are working on. I was able to work around it by creating a new file, creating a new proxy and then copy and pasting it into my model.
After that I had huge problems rendering. The Rendering spawner just would not start or respond, or the rendering would just stop in the middle somewhere. Then I noticed on one render that got to about 50% that I could see a pattern on something that shouldn't have had one. It was my displacement map! When I turned my displacement maps into bump maps it rendered without issue. Hopefully this is something Chaos will address in the future because the displacement looks much better than the bump.
-
Ha! There's a separate bug where displacement and bump maps are getting applied to subgroups within a group even if its a different material. Hope Chaos is fixing that one too
-
Amanda, this is not a bug. Displacement maps inside of Proxies is never a good idea. At the moment, because of the way V-Ray handles Displacement and Proxies, you should never use a displacement map inside a proxy unless you want the entire proxy to have that displacement applied to it. Normal mapping and bump mapping are best used inside proxies.
Andy, could you elaborate on the bug you are referring to? Have you submitted a bug report and steps to reproduce the bug? When you say a bump is getting applied to a group and subgroup, are you talking about inside a proxy or are you talking about generic groups inside of Sketchup? If you have a file that clearly shows this issue please submit it to support@chaosgroup.com and Ill take a look at it and see whats wrong.
-
@tedvitale_cg said:
Andy, could you elaborate on the bug you are referring to? Have you submitted a bug report and steps to reproduce the bug? When you say a bump is getting applied to a group and subgroup, are you talking about inside a proxy or are you talking about generic groups inside of Sketchup? If you have a file that clearly shows this issue please submit it to support@chaosgroup.com and Ill take a look at it and see whats wrong.
Well, I had submitted a bug report - or thought I had. I went to check, and it doesn't look like it went through. I sent it again, so you should have the files, etc. related to this.
The error I have does not involve proxies, but considering that everything in a scene is converted to proxy in the background for rendering, I'm sure this affects proxies as well. The issue is that if a group has a material applied with displacement, if there is a subgroup with one material that is a different material, it will get the displacement applied to it even though it's got another material applied. It should be pretty clear in the example files.
Andy
-
@Ted, did you find the bug report yet? Can you confirm there are issues with displacement maps affecting sub-groups?
-
@andybot said:
@Ted, did you find the bug report yet? Can you confirm there are issues with displacement maps affecting sub-groups?
Hey Andy,
Yes this occurs. But we don't currently support nested displacement inside of V-Ray Proxies. Displacement is an all or nothing game because its actually creating geometry at render time. Because a proxy is created from geometry, displacement will either effect nothing, or everything in a proxy object and its hard to tell when and what it will effect.
My workflow suggestion would be to separate the displaced geometry into its own proxy. For example a tree that has leaves, branches and a trunk. Lets say the trunk has Displacement applied to the bark material. When saving out the proxy, group the leaves separately from the trunk and branches. Select the groups, and create the proxy. When you get the proxy dialogue, choose "Export each selected object in a separate file" the trunk and branches will be a proxy, and the leaves will be a proxy. Now group that proxy, make it a component, and you're good to go, you can array it through your scene quickly and easily.
What this does is allows the displaced geometry to be applied to the proxy globally, since the leaves are their own proxy, you no longer have the problem of displacement effecting everything.
Hope that helps!
-
I'm not saying there's no workaround - it's just that this effects regular groups in a model, not just when you make a proxy. I think best practice when modeling is to not add material properties to top-level groups, only low level groups or faces only.
Advertisement