Ok. I think I will just keep looking for different HDRI and continue experimenting. Thanks for the link. Very interesting. I already started thinking about the lack of shadows in my render but wanted to tackle the size problem first. Thank you for helping me. You have a very interesting blog and many great renderings. Best regards niX.

I'm guessing you have a material in particular that is hanging it up. You can choose which materials can be overridden, which will allow you to override all materials, and then enable each on individually until you find the one that is causing the huge slowdown. That could help people troubleshoot the issue with you.

The 2.0 beta is over, please update to the latest service release that is available on our website. This may have been addressed in the service release.

thanks. i fixed it in photoshop.

Is your Layer 0 unchecked?

You don't have to save to a separate vray material (vrmat), you can just save the SU material (skm file) to a library. Look in the SU help documentation about saving a material to a library.

yes thx, 'make unique texture' is works now

I think I may have a solution. Don't mess with the transparency in the refraction layer, unless you have more than one refraction layer. Just leave it black

Thanks Ludnid. I had the same problem and your trick seems to work!

@maeglin1 said: Vray 1.6 You really should be using vray 2.0. Vray 1.6 is beta build that has expired. There have been a lot of improvements anyway since 1.6 @unknownuser said: and it works as it should. I have even located the Vrimg Converter which is very handy.... a plugin I would never have discovered if I did not have this problem. Glad to hear you've fixed your installation and were able to follow the tutorial

Not sure if everyone got the newsletter, but the service release is up on our site now.

Are you using 2.0? I see a huge boost in rendering times even with just 2-3 computer slaves. There really isnt a whole lot to setup. Have the slaves on and running the spawner. Make sure all of your licensing is setup correctly, click render. Assets are transferred quickly and I see a boost in both my LC pass and IR passes. If it's working, you will see more render buckets at final pass time. If your machine is running low on RAM, just open the 64 bit spawner on your machine and check "Dont Use Local Machine" and just make sure localhost is checked on in your DR setup. With this method, you will not see you LC pass, but it is essentially 64 bit rendering on your local machine because you are no loner confined by SU's 32 bit environment. Now this is all assuming you are on 2.0, if not, then DR is pretty busted and I wouldn't recommend it. For more info on DR, see the manual http://help.chaosgroup.com/vray/help/sketchup/150PB/distributed_rendering.htm

You can create a custom channel in the VFB. For example, if you want a channel of a 2-sided curtain material for post processing. You can use this feature with lights also, so you can get the result of a single or multiple lights for post work.

Sorry to sound crass, but if you need help loading a preset, then you really need to look at the manual and some tutorials. V-Ray is not a magic rendering engine. You will never have clean noise-less renders if you don't learn the parameters of the engine and understand them clearly. If you are using 2.0, then this is how you load a preset. http://help.chaosgroup.com/vray/help/sketchup/150PB/tutorials_preset.htm Bookmark this page and reference it... a lot. http://help.chaosgroup.com/vray/help/sketchup/150PB/

I've heard rumor that we might get environment fog in 3.0 but its a no no in 2.0. You can try faking it with a ZDepth pass maybe?

If you are using an HDRI as a dome light, you only need to disable the GI and BG in your Environment. You should exposure in PC. I dont know why you would ever disable this.

In general, there are far fewer options exposed in the vray interface in vfs than the other versions. You may have to wait until 3.0 comes to vfs to really get better convergence.

Thanks. I knew that but I forgot to put it in there.

good to hear, would love to see the final result if you can share!

apparently this problem has been fixed in version 2.00.24