Hey guys, I’m experiencing a weird issue with GPU and bucket rendering. I am getting a discrepancy in buckets. All textures are mapped appropriately and when doing IPR or progressive, its fine.
I’m running Vray or max - update 3 , 3ds max 2020 -
Ive tried RTX with just GPU’s - 1080ti and a Titan RTX
Ive tried Cuda with all gpus and CPU
Last test could be just CPU on Next but I really dont want to go that route..
Could you send the scene to support@chaosgroup.com so we can take a look? Mention this thread in the e-mail as well and also share your graphics card driver version.
While AdaptiveDome works well in most situations it still give me the same bucket issue from time to time ,1.5 year after its official release . V-RayNext CPU for Maya here.
Hey I just found this post when I googled for a solution. I´m having the exact same problems as it seems. I´m trying to render an ocean scene from PhoenixFD 4 with VRay 4. I found a thread where georgi.zhekov wrote that we could use a VRay Instancer node for the foam particles which I tried and which worked perfectly! But I can´t render my scene now because of these damn bucket errors so I had to switch to VRay Next CPU for now but now the whole animation takes 300 hours to render with a 16-core threadripper. Is there already any fix or workaround for this? What I already tried was re-installing both VRay and PhoenixFD which didn´t help unfortunately. I tried rendering some other scenes I created earlier and they gave me similar bucket errors.
After a whole day of testing (Removing single objects from the scenes, merging objects into a new scene, installing an older GPU driver, etc.) I figured out that in all the scenes where the bucket errors occured it was a material or a texture which caused it! Maybe because I imported purchased objects into these scenes which had anything applied to them which isn´t supported by GPU. So maybe this helps someone who has similar issues.