Compiling geometry and scene prep takes forever on a top spec machine

[mienda]

Hi,

I have a big scene to manage, but unfortunately i have the same issue with Vray 3.5: Compiling geometry and scene prep takes forever with displacement on ( and all is ok when displace off).
Have you got an idea about whan you you could fix it because it is very uncomfortable.

Thank you

mienda

[stilgarna]

I've got the same kind of issue, with compiling geometry and Proxies.

Rolling back to previous version.

Best regards.

[glorybound]

Me too. 30 minutes of Compiling Geometry for a 10 minute render.

[vlado]

We have already fixed the displacement issues for the upcoming 3.50.04. If you have the issue even when *not* using displacement, then I'd love to get a scene to vlado@chaosgroup.com so that we can fix it.

Best regards,
Vlado

[salvadoresz]

Hello everyone,
Very happy to see this getting fixed in 3.50.04. I thought i'll add my own observations on the matter, it may or may not help. Vray RT GPU 3.50.03, 3ds max 2017, win 10 home, 2x gtx 1080, i7 4790k, 32gb ram.
I have a simple scene, a box with a logo displaced at 1 px edge length (16bit tif at 4k). When i press render, it starts compiling geometry, and occupying CPU RAM. Two scenarios can happen: 1. After 10 minutes it starts rendering the image, but cpu ram usage is at 16GB, and gpu ram usage at 6.7GB. 2. Cpu ram usage runs out of control and fills up all my 32GB, crashing 3ds max. I also sent the scene to support (ticket #810124).

[anthonyh]

hi,
sorry a bit off topic but with 3.50.04 upcoming how come in the 3.5 release movie the version number was 3.55.01 ? just curious.
ta
anthonyh

[Mnietek2707]

Is this possible to get this update sooner?
I have scene with a lot of displacement and I can't render it.

[hubmer3]

Bump!

I also struggle with this problem :-/

[vlado]

We have a fix for this in the 3.50.04 patch, which should be coming out in a few days, but if you want to test the fix sooner, please email me to vlado@chaosgroup.com

Best regards,
Vlado

[hubmer3]

Jap! Problem is solved for me!

Compiling Displacement (3D)
3.50.01: 43,8s
3.57.01: 1,6s

Total Rendertime
3.50.01: 7m9,1s
3.57.01: 6m57,7s

Specs
Win7, 3ds Max 2016 sp3
DUAL E5-2683 V3 28/56 @2,6Ghz
64GB Ram

Thx!

[salvadoresz]

Just tested vray 3.50.04, and the GPU displacement problem didn't go away for me. Too bad, i can't render anything with displacement. This is what i observe: i have a simple scene, a box displaced with simple logo, a 16bit *.tif, 4k res, @1px edge length. I switch to GPU rendering, and press the render button. Within a minute, 100% of my 32GB system ram is used up and either max crashes or it just keeps on going, BUT the actual rendering never actually starts.
If i switch t cpu, everything renders smooth, so it's a gpu issue.
I also sent the scene to support (ticket #810124).

Thank you

[vlado]

Thanks a lot for the scene - will take a look.

Best regards,
Vlado

[salvadoresz]

Thank you very much Vlado.

[MegaPixel]

Has it been confirmed that the .04 build solves this issue? We have 2 brand new top end boxes using Max 2017 and Vray 3.5 and have recently started experiencing crashes during the render process - I usually see the crash during the "Building Embree Static Accelerator" part - Scenes usually have displacement and seem to run ok when turned off. Thanks!

[yavor.rubenov]

Hello,

The general issue in this thread is that in some scenes the compiling geometry phase took more time on machines with more threads than on machines with fewer threads. That I hope is fixed in .04 builds.

When you see crashes during the "Building Embree Static Accelerator" part - do you have enough free RAM ? Displacement can add a lot to the memory requirements of a scene.
If there is enough memory then there could be some other problem - in that case can you share one such scene here or with our support ?

Best regards,
Yavor