Hi,
I´ve just updated from Vray5 to Vray 6.
I´ve open a scene that I was working on already, and then when start to make any kind of render (ex:IPR or just render with with lower settings), the only thing that happens is that the frame buffer opens, and it just keep on updating instances…and doesn´t make the precalculation or build the light…don´t render. It crashed.
I´m working with Studio Max 2022.
Thanks in Advanced
Same problem with me.
i upgraded from vray5 to vray6 on a subscription this morning. Firstly it appears to take longer to load my files on open and then, as you say, it stalls (and sometimes crashes all together) on ‘updating instances’ when rendering.
I am working on very large scenes but it worked ok with version 5 and i have now reverted back to version 5.
Version 6 is useless to me until this problem is solved and i would ideally like a refund of the £387.94 i paid for the subscription until fixed.
ps: using max2023
Hello,
Do you have any third party plugins installed like ForestPro or RailClone - if so they need to be updated to a version supporting the official V-Ray 6.
If that is not the case - when Max crashes it should create a crash dump 3dsmax_minidump.dmp in your temp folder - can you attach one here ?
Best regards,
Yavor
Hello Yavor,
Yes I have ForestPro & RailClone, indeed they had update their software also on the next day Vray 6 was officialy released. I have already updated, now it works fine.
Thanks for your help.
Cheers
I’m not getting crashes, I just get “Updating Instances” for several minutes before an IPR Progressive render will begin to be visible. This nullifies the efficiency of “interactive” viewing. I updated all iToo Software. Is this just how IPR works now, waiting for Instances to update?
It should be quite fast (not many seconds) - can you share a scene (with our support) takes several minutes to start IPR ?
I am experiencing the same, or very similar issue. Thought it might be an issue related to TyFlow, but testing a scene that only contains the (merged) Phoenix items still gets stuck at “Updating instances”. Oddly, this only happens with Production Rendering, or when submitting to Deadline. Single-frame (max “iterative”) rendering works fine.
I’m wondering if Phoenix is not reading the cache, and re-running the sim … so I’m going to test with like, 1,000 particles and see what happens. In the meantime, my problem scene is attached; let me know if anything else would be helpful.
Edit: after a test, I don’t think it’s a re-sim issue. I created a 30-frame scene with a very coarse grid that took about 12 seconds to simulate. I parked the timeline slider at frame zero. The first frame (frame 0) from a “Production” render was created normally. Frame 1 was still “Updating Instances” after one hour.
scn_02-02-ladle-FG_05.zip (135 KB)
Update for my use case: I updated to Chaos 60006(hotfix), Phoenix 5.01, and TyFlow 1.007, still using Max 2022. Rendering works as expected, locally and via Deadline, so problem solved for me, at least.
Same issue here. I have the latest Forest Pro and RailClone. I have been trying to render a pre-6 model for the past 4 hours. The buffer sits there at Updating instances. I delete what it looks to be stuck on, and it gets stuck on the next. I also tried GPU render, and it sits at Compiling geometry, and I can’t stop or cancel.
I globally turned off displacement, and it is rendering now. At least I have direction. I’ll track down the displacement culprit when I can.