Unhandled exception when trying to render large res (10kx5k) - Very urgent

V-Ray V-Ray for 3ds Max Issues
1

Getting a 3589 error when preparing server.

It is a fairly large resolution with a fair bit of displacement (all 3d displacement).

I have 64gb.

Do I have to raise the vray edge distance to get this to work or is there some kind of setting I need to change ?

UE.JPG
UE.JPG509×212 16.6 KB

vraylog.zip (1.83 MB)

2

Hello,

Can you check the available memory when you start the render - maybe you are running out of RAM ?
If that happens - raising edge length could help. Also if you turn OFF the static displacement option - then the displacement will be dynamic geometry and you can limit it. Rendering will be slower but memory should be enough.

Another thing you can check - if you’ve added render elements that you don’t need - at 10kx5k each element consumes quite some memory..

Best regards,
Yavor

3

Cheers. I’ll try turning off the static displacement option. No render elements for this shot. I also converted some forest items to vrayproxies. Fingers crossed.

4

So it manages to get through to rendering now which is great but now I’m getting continual errors: Invalid geometric normal (-0 -0 -0) for “Vraylight”.

Also, it was rendering now but even rendering the HDRI sky I’ve used as a light source was taking forever. Normally with the sky HDRI it zooms through it very quickly and only when rendering geometry does it slow down.

5

Okay. I tried rendering again with no geometry. I’m using camera type: BOX by the way. I still displays the same error without any geometry in the scene!!??

Also, the renderer seems to be rendering the black areas (very slowly) of the long/lat box render. Why is this ?

6

This is a small grab of the render with no geometry. The circle inidicates where vray starts rendering very slowly…even with no geometry in the scene.

long_lat.JPG
long_lat.JPG1286×659 35.6 KB

7

So, when I switch back to default camera type the normals errors stop and the render is much quicker. My client requires this type of box lat/long render.

8

This is a bug; we have a fix for it in the nightly builds and we can get you a build, but I’m not quite sure if it’s usable. In any case, email me to vlado@chaosgroup.com and we’ll figure something out.

Or you can render a cube 6x1 camera and rearrange the views manually. Or just render the 6 views separately with a perspective camera with 90 degrees FoV and put the, together.

Best regards,
Vlado

9

I had to render out a spherical and then convert it to long/lat in the end. Good to know it’s a bug that has been sorted. Thanks