A lot of things are absolutely amazing in V5 but the essentials are those who causes xtreme headaches to me.
1. Rendertimes in General 2. Renderstart-Times.
2. I dont know what or why this happens but on my current scene when I hit the renderbutton (production render in VFB) than watching my taskmanager: It uses about 5% CPU and like 2-3 MB/s Networktraffic and i can wait (for real) about 10-20 minutes before Vray even start the rendering. I mean: Once this ridiculous time has passed it begins to “Prepare” Scene for frame and compiling geometry.
Iam really exhausted to nerd crack through those conditions.
Iam unfortunately limited to show anything because of NDA to my clients. But I can explain the scene:
Its an Office from outside. Ramusage 60GB.
CPUs: Threadrippers 32 Cores 2x and 1x Ryzen 9, 12 Cores. So in sum: 64 + 64 + 24 = 152 Threads.
AA 1:24
LC 3000
Rez: 5000*2800 pixel
Renderingtime was 10hrs.
Theres one change which could have impacted this rendertime a lot and it could be my fault. I changed max transparency depth to 200.
But thats not the topic. I send a video (which I will speed up) and the Vray Log in about the next hour.
About Materials: Nothing Special here. I used two HDRIs because of that amazing new feature to render once and via Light Mix disabling/enabling the HDRIs.
Materials are PBR and 1000px. I have also a lot of displacement.
But I cant even imagine what that has to do why Vray does start the rendering after 15 minutes.
Imagine this in an animation.horrible.
Also there are no indications in the statusbar or VFB what is happening in those 15 minutes.
I have to stress out that iam not even an usual user of Vray. Iam a completely nerd and know a lot of things under the hood of Rendering and Vray and coding. But even for me its an extreme hassle with Vray 5. I thought everything will be more easy. Not at all. Its currently horrible for me and I have a lot of employees.
From what I read it could be a bad displacement setup. Vray displacement is an amazing tool and it’s incredibly efficient, unfortunately if you do not tune that properly it can easily lead to long preparation time, RAM consumption and slow render time. I must add to this that default setting for displacement are not ideal, it could be easily tuned to get a lot more speed, and I really mean a lot! I guess developers decided to set it like that so that it can always produce good detail but as far as efficiency/speed a lot can be done.
I already said: BEFORE even V-Ray is compiling geometry (which is preparing the displacement), it does not even start the rendering.
But I will test that too. I doubt that is the case however
Hi @PdZ , from what I read, it really sound like the displacement may be the culprit for the long renderstart, while the max transparency level may be the cause for the overall long rendertime.
As @sirio76 mentioned, tweaking the quality settings of the displacement may change the preparation time.
I must add to this that default setting for displacement are not ideal
We have also had some internal discussions for the current defaults and we may tweak them in the future to provide better startup and render times while having good quality for most of the scenes.
Last but not least - if the displacement in the scene is located in parts that may not participate in the rendering, changing the geometry generation to “On The Fly” might improve startup time, but it may impact rendertime.
Doesnt help at all. I disabled all displacementtags and also globally. I even deleted almost everything out of the scene. Scene does not start until a long amount of time…
Yes.
I maybe think to have found what is the culprit. Maybe its my materials are in the network drive also proxies. Maybe V-Ray have to load them before starting rendering and this takes so long. I will check that.
Hi @PdZ , something caught my attention and it may reveal the cause:
Maybe its my materials are in the network drive also proxies.
Do you have the materials and/or the proxies stored as an asset in a content browser library?
@deyan.hadzhiev No. They are just in the network and accessed by a shared drive.
There no Assets in the contentbrowser used. I think I will figure out later what cause this but now iam very much in Deadline-panic.
@Doger Yes, as I said. Iam using V-RAY 5 Proxies too. Why are you asking? They are also stored in the Network. But Currently I think its not related to the network, displacement, proxies or contentbrowser.
Because there is definitely still a bug with VRay proxies when they are scattered. Apparently the textures of the proxies are duplicated more and more which leads after a while to the scene getting bigger and bigger after each save. Sometimes my 300mb scene became 7gb and it took forever to open it or start rendering.
Here is a small video showing the bug:
Maybe this leads to the huge render start times?
If you take a proxy out of the cloner and turn off all cloners you can open the proxy manager. Then everything is corrected until the next save.
Weird bug. But thats not what I experience. Its that when hitting the Production Render Button it takes about ten minutes or so then V-Ray decides to start to prepare the scene and so on. Thats horrible. Its so slow
I am happy to see that I am not alone with this problem. Heavy scenes sometimes really start a few minutes later to render.
I have this, too on several kind of scenes… Once with many and large displacements, also once without any displacement but a lot of polygons… or for example with big terrains and grasskit… (multinstances olny without grasskit works better)
For example the scene with large displacement starts indeed earlier to render when displacements are switched off…
But sometimes it drives you crazy, compiling geometry starts after a few minutes ( and yes sometimes after 10 minutes)… IPR is in such cases much faster..
@PdZ : Maybe you can confirm… take such a scene with default render settings, but reduce the Noise Treshold to let’s say 0.05 just for testing. I experienced, then it starts earlier to render… I know it is not an ideal value, but maybe it shows CG where to look for this problem? I am not a programmer, only what I am experiencing…
@haniel1107 I will check that. But it seems something else is going on. Pls watch the video. V-Ray starts after 5 minutes and 30 seconds. Before that seemingly nothing happens. There is a bit of networkusage at the start and then 5% CPU (1 Thread is running). Nobody knows what happens. Its horrible because imagine waiting always 5 minutes before V-Ray even starts…
I will know make tests to figure out what is going on here. Seems veeeeeeeeery weird. Displacement is off btw.
