Here is a problem I have some difficulties to identify.
When using V-Ray VFB, while rendering, if we touch some settings like white balance, max hangs, change active windows with each it can find (render setting, main ui, vfb etc) and no change can be seen. I doesn’t crash but can tak minutes to come back responsive.
Sometimes, even zooming in vfb with mouse wheel cause white vfb and takes age to come back, if it does. Same on some render slaves via BB, the rendering finish fine but the vfb stay white.
Also, sometimes cancelling the render also do such windows activate everything/white vfb and takes minutes to come back responsive.
This doesn’t seems to happens with max vfb.
Working on heavy scene, millions polys/thousands objects
Windows 7 Pro x64 SP1+performance update
nVidia 1070
3dsmax 2018.2
V-Ray 3.60.02 (3.60.03 in deployment, let’s see tomorrow)
RailClone Pro, Forest Pro, PhoenixFD up to date
If someone has idea where to look at to identify from where it could come …
I should add, I had a massive scene that after rendering finished (11 hour render) froze for hours and I eventually had to give up on it. Also using 3.6.
I have not had this happen before; it might be specific to 3ds Max 2018. How easy is it to reproduce it? Does it happen every time? What if you turn on the “low thread priority” option?
It happens a lot but not everytime, which is hard to identify.
low thread priority is checked on all our machines (it is in a startup script, with max priority low)
I have check setting max process affinity to cores number -1, it does the same
… VRay 3.6.03 and Max 2018 sp2 … win 10 latest updates … dual proc
create a plane, put a sphere on it, create a dome light
open vray VFB, hit start interactive rendering … vfb shows a strange preview … but is not updating at all
vfb is frozen … have to quit max by task manager
if i do exactly the same in 2017 it works as expected
in 2018 i had tried the latest nightly when i run into that problem
i deinstalled all vray inst. for all max versions and after that installed new ones for max 2017 and max 2018
I can’t replicate that on my test scenes.
Does it only happen with multi-million polygons scenes? Can you try to replicate it on a very simple scene with a few basic primitives without any premade data?
If it doesn’t happen on the elementary scenes would it be possible to send us a scene that replicates the issue and some guides what we have to do in order to trigger the issue?
We can’t reproduce it here… so please, next time it hangs, create a dump file and send it over (right click on the 3dsmax.exe in the task manager and then “create dump file”)
