so the long compiling times are not scene specific, i get them in other scenes too.
doesnt look like its single threaded cos all the cores are operating but the slowness is really weird.
We are having massive issues with compiling of geometry as well. But we have a large scene with 6 displacement maps at 4k resolution. However, we have never seen compiling geometry take as long as it has been doing now. It would crash my entire farm in distributed render even. Our machine too is top of the line.
its so strange because i can clearly see all the cores running at the top speed…cant imagine why woudl it také 56 threads to compute a few displacement maps with basically unlimited ram. Furthermore, i am pretty sure its not been taking so long on my previous rig…
i will probably try the beta 2 to see if its doing the same.
i ve tried playing with pagefile in Windows too…but since i have so much RAM i doubt its writing anythign to the ssd it woudl nto make sense.
i have also noticed some sudden performance drops while compiling. Hopefully this gets sorted because i cant imagine waiting for a test render for 20 minutes only to begin rendergin :-/…and doing this repeatedly after every change.
In Martin’s case, it’s due to the code that generates displacement, which seems to multithread poorly. We think we have a solution for it and hopefully it will go into 3.50.04
I have no idea about ILS’s case. It seems different (the displacement issue is in 3.40 as well), but he didn’t provide a scene so I don’t know.
I get about 300,000 warnings saying "warning: invalid normal index found on face ##### - “-1” replacing with normal index 0.
I says it takes 352 seconds to set up the scene. In the previous version there was no problems.
It seems that the vray warning window only comes up when the scene is xrefed, if you merge the scene and render, the warning window does not pop up but the 300,000 warnings are still there taking up loading time.
That seems a different issue. I think we have a report for this in JIRA, but just to confirm the potential fix, can you get me a scene to vlado@chaosgroup.com ?
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.
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.
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).
