It's not quite clear from your post - are you using the dome light? If so, you can edit your domelight to be hidden. Further down in the light editor window there is a setting under "options" for dome light to be invisible.

@las2vc said: No, I haven't, but that looks like a good potential resource. Thank you! It's the best forum for Podium lol! I learnt sooooo much from the Podium forum. Everyone is very helpful and critical which is great if you want to improve your work. I guarantee you'll have it figured out quickly. May be a good idea to start off your post with what preset you are using and we can go from there. Do you have a problem just rendering an omni within a box? Could just be you haven't created the omnis properly because it looks like they aren't turned on.

@elibjr said: the grass doesn't even work anymore. ?!? Why?

That's great

Try to export to Blender (A, A, Remove Double see this anthology post) or Wings3D all free for easily cleaning your OBJ polygon mesh before exporting in OBJ format for Rhino! And also try for the fun Moment of Inspiration who is some ergonomic than Rhino you can make Copy Past : ctrl + c, Ctrl + v between the 2 applications (Moi Rhino, Rhino Moi) And Moi has an export SKP ! And the best export Nurbs to Polygons if wanted! And an new exceptional export PDF! By Grendel Jellybean model from CreatureBox Moi Export PDF [image: get_attachment.php?webtag=MOI&hash=0f52a9af01f8da8bbb2b107ea85f67a2&filename=JellyBean-MOI.jpg]

Thanks wind-borne, I'll check in to the cost for Pro.

ok, then... NO

thank you for your reply. but it is possible to pull the noise shader in the length? in VRAYforC4D it is possible to change the relative size! see here: [image: PbHU_2013-12-02_151713.jpg]

Hi Tom, Have you played with your Dynamic Memory Limit settings? I was having trouble with Displacement doing strange things as well, and after some testing I've found that having your dynamic Memory Limit set to somewhere between 1024 and 4096, I seem to be getting better faster renders.

Which version of Vray are you using?

you could reduce the reflection mutliplier.

I forgot to mention I have a dual core. If I add anything refractive it slows down render time....but I'm not using vray anyway, so my render time comment is wholly irrelevant.

You could make a double sided material that is Transparent on the back-face and opaque on the front-face. This will allow light to pass through without being to see out. I've done something similar (actually the reverse) for the ceilings of units so that I could get a sense of lighting by windows by look at the unit from above.

what are the error messages you are seeing - either in the vray error log or in the ruby console?

I didn't realise you could read them with a text editor, I assumed they were some form of code. Which is seems many of those I downloaded are. I also think I now realise why they don't work. In many cases the directory path from the original location is set within the vismat. So naturally when I try to use them the location is different and the vismat or Vray can't find the relevant bitmaps. Luckily many of these textures include the necessary bitmaps, so it seems as I use them I'll eventually build my own library. Thanks again for your help Andy, Regards Joe.

this shouldn't be an issue in 2.0. If anyone is still using the outdated 1.6 BETA version, please upgrade to the latest release. 1.6 was a beta only, was buggy, and was not ready for commercial use.

yeah I still have the same probleme... it creats multiples unique component when you scale a group with components inside. Any solution ?

Regrouping and reducing nested Groups did the trick.

no, the dongle is required in order to use our GUI or render.