It very much depends on the direction your light is shining from. The more perpendicular your light source is to your surface, the more washed out your bump map will be. If you have your light closer to parallel, you'll get a more raking light and show up your surface texture much better. Can you post an image perhaps?

@dkendig said: I hope you get up to speed in time for beta to start. The next version has a bit more pep in it's step. yes looking forward....

Quick question to the OP. Did you use the same vismat for both instances? The reason I ask is because I know that there have been some issues using older vismats with the newer version of the VRaySU. You could try re-building your material from scratch in the newer version to see if that works better. Rob

Change your GI to just use Irradiance Map - no second engine Change your Image Sampler to fixed set it to 1 Turn off any displacement mapping Change your DMC Sampler Subdivs multp to .5 Your render will look like crap, but will render fast - good for test. CANT WAIT FOR RT!!!!!

No, not that I know of. You can setup DR Spawner if you have a network (up to 10 machines), but it does have bugs in the latest version and is not stable.

Thanks for the link. Wish I had that 3 months ago when I worked on past project. I should mention that I did not have much luck with Zorro with a very complex high poly model imported from Revit.

the idea of turning of the light is meant especially for the beginner..the sun is a super strong omni light and to compensate it you need to balance the exposure with vray physical camera. THis balancing act creates a different effects with IES light even. and many users becomes even frustrated... therefore so that you are not solving many things at the same time and you are only looking at IES light effects, its useful to turned off your sun and the camera. this time you only have to take care of your IES lighting. I have done lots of tutorial with VRAY IEs lighting and they are everywhere. One piece of advise,, units affects the ies data. vray working unit is inches. so be sure your unit is in inches...

ok I will use the study material in sketchup ... I hope that in future versions should offer a clearer preview from the ... 100x100 we understand little. I agree with valerostudio... the magic word "preset", add "library materials" and "realistic preview" (at least 600x600 see indigo render). thanks to all friends

@andybot said: Does it say if it's APS-C or full frame sensor? Does the SU lens length assume 35mm film? AFIK - yes. For matching photos from digital cameras (without using PhotoMatch) I've been using conversion tables that convert the digital lens to 35mm and that seem to work. But note that SU might some times work on the vertical size instead of the horizontal or diagonal size - and it's pretty much impossible to tell.

@thenajsays said: have light as an emissive material currently, but I've experimented with various setting, IES lights and spot lights, and I still see the same issue. Did you try rendering the scene with no emmissive material? Try to get your lighting right without the emm. mats to make sure you have enough light in your scene. @panixia Increasing the HSph. subdivs in the irradiance map settings will help reduce the splotchiness, but it won't fix the emissive "sparkles" that we see.

This test below is a box 5mx2mx1m (sorry, I'm metric). Base wood texture image set at 1mx1m it looks as though its all dependent on the scale of the base image used in the texgrid fill colour. If the base image is say 1mx1m (as defined in the sketchup material editor)then that is the size of one panel. [image: rmSx_test07.jpg] in this one I have adjusted the TexGrid repeat to 0.5, so each grid is 500mmx500mm [image: uJ2l_test08.jpg] and in this one I set the base image size in the sketchup material editor to 2mx2m (UV repeat back to 1.0) [image: TgBp_test09.jpg]

Thanks Oli! Superb!

the idea is that with a model, we can look at your vray settings and see if there's a solution.

@thomthom said: Really looking forward to get my hands on the beta! Me too. I hope they're finally going 64-bit.

could it be that the png is not being saved as interlaced?

Bug is VRay. Rumor is that this has been fixed in the next release already. We just are waiting for it to beta.

@stefanq said: That doesn't look to me like a correct mapped hdri image. Doesn't matter if it's big, small, blurred etc. You probably mapped it like "spherical" as type, and it's not a spherical map. Try "angular" instead. Notice that you cannot zoom in the HDRI. It's like you try to make some objects in an image to look closer. When you choose a HDRI, think about your camera position in the scene, how far you are from the object you're rendering, and try to find a HDRI image with similar shooting conditions. Finally, almost 2 weeks... I've a little bit understanding about HDRI. I try to browse some free "spherical HDRI map" and match with my model, then apply it to my environment. I get a better result. But, I just thought HDRI was not one of the best environment setting, there is many ways to do it. Thank you so much guys... Thank you stefanq... Jr

check the color slot in GI settings, also make sure you're using vray sky, otherwise you won't have sun shadows in your render

skip to 5:00 to see it in Rhino which will be the same as SU http://www.youtube.com/watch?v=PbMykOA04Ac

Thanks for your responses....yes i've changed the angle of my camera and reduced the amount of grass but still quits :S... my dynamic memory limit is 5000 .. it seems ill have to use photoshop instead