hybrid rendering

[Makushimu]

With rendering set to progressive only cpu is used, gpu has a few% of use.
When rendering set to bucket only gpu is used, cpu bucket do not appear. In older builds, cpu buckets worked properly with gpu.
Additional, when Out of core(WIP) is enabled textures are not loaded correctly, and artifacts apearing.
In bouth cases some console errors apears.

[shaio]

Hello Makushimu ,

With rendering set to progressive only cpu is used, gpu has a few% of use.
When rendering set to bucket only gpu is used, cpu bucket do not appear. In older builds, cpu buckets worked properly with gpu.

The reason why the CPU is not used is that the Out of Core option doesn't support the CPU devices and is excluded by design. It is explained in our documentation in the following link: V-Ray Tab - V-Ray 5 for Cinema 4D - Chaos Help

Additional, when Out of core(WIP) is enabled textures are not loaded correctly, and artifacts apearing.

The out of core option is still work in progress and issues are expected. It would be great if you can share the scene producing the artifacts so we can take a look at.

I've also noticed in your log that you're using newer than the recommended driver. Please make sure to always use the recommended by us to avoid issues caused by the driver. You can find the recommended driver version in this page: V-Ray GPU | GPU rendering by Chaos

[Makushimu]

Ok, thanks for reply. But what about scenario when rendering is set to progressive and only cpu is used, even when out of core is disabled?

I don't want to go back to 461.09 as I have had issues with these drivers in other applications.

[shaio]

Ok, thanks for reply. But what about scenario when rendering is set to progressive and only cpu is used, even when out of core is disabled?

It should be utilized. I've double-checked this on my end the CPU is utilized as expected for both Progressive and Bucket rendering with Hybrid rendering. There might be something causing this on your side. Could you please check it again (keep in mind that the Light Cache is always calculated on the CPU) and maybe share the scene to check if there isn't something causing this on your side?

[Makushimu]

I tried again to use hybrid rendering in a different scene, and another error occurs when rendering starts, then C4D freezes and closes.

On the gpu page, the 461.09 driver is recommended. Does that mean I should use the Game Redy drivers? Because the Nvidia 461.09 website is a Game Ready driver.
What's the newest Studio setter supported, Shouldn't I use them?

[Makushimu]

I changed the driver from the latest studio to old gameReady 461.09. After the first long scene loading, C4d crashes. The second time around, the scene opened normally. Unfortunately, I wasn't able to render it in hybrid mode. After several unsuccessful attempts, I gave up. I managed to get the LC calculated and then the processor works at 100%, gpu at 0% and nothing is done, I waited about 10 minutes. LC on the CPU takes a short time. Something is wrong with textures, but I don't know what causes that, render works fine on CPU.

[daniele_nicolaci]

I've faced the same error in GPU mode just today, and after several tests I discovered that it was due to some missing textutes on Vray materials. It worked in CPU mode and not any warning regarding the missing textures came up, but after fixing the texture paths, everything started working fine again. I hope this can help you.

[Makushimu]

I've faced the same error in GPU mode just today, and after several tests I discovered that it was due to some missing textutes on Vray materials. It worked in CPU mode and not any warning regarding the missing textures came up, but after fixing the texture paths, everything started working fine again. I hope this can help you.

Thank you for the answer, but that's not the only problem I found.
Somehow the GPU doesn't want to render when one object has multiple selections, the same material is assigned to each selection but with a different mapping. For example, one selection has UVW mapping, the other selection has cubic mapping.
When I changed cubic to UVW suddenly rendering started and didn't crash.
The most interesting thing is that when in the same selection I switched back from UWV to cubic, the rendering still worked.
As if just clicking through the mapping type fixes the error.
Console still shows an error, but rendering works.

[0h 0m 0.1s] [ERROR] [RTRenderer::loadGPUPlugin] -1: Failed to create CUDA renderer plugin instance.
[0h 0m 0.1s] [ERROR] [RTRenderer::loadGPUPlugin] -1: Failed to create CUDA renderer plugin instance.
[0h 0m 0.1s] [WARNING] Duplicate string IDs (Quadro - Biały_7085C2AF5A1615039DD246019E970000) with different generators in uvwgen_ids parameter in material: Płyta_boczna_70A16FF5163F828E@mtl_uvwselect

I consider this a bug that should be fixed immediately in order to benefit from hybrid rendering painlessly.!

[Makushimu]

I changed the mappings in problematic selections. I quit with C4D, reloaded the scene and it doesn't work again, with such a error:

Successfully initialized V-Ray 5 for Cinema 4D, hotfix 1 (API R23.000, runtime R23.110, V-Ray version: 5.00.43.30654, revision: 54d1b52c, build date: Mar 12 2021)
[0h 0m 1.9s] [ERROR] Exception in CORE: Internal error. Please save and restart as soon as possible!
[0h 0m 31.9s] [ERROR] Renderer exited with error: No error.

Without leaving C4D, I closed the console and VFB, and then I fired the render again, which this time worked, but at the end of rendering showed the following error:

Successfully initialized V-Ray 5 for Cinema 4D, hotfix 1 (API R23.000, runtime R23.110, V-Ray version: 5.00.43.30654, revision: 54d1b52c, build date: Mar 12 2021)
[0h 0m 1.9s] [ERROR] Exception in CORE: Internal error. Please save and restart as soon as possible!
[0h 0m 31.9s] [ERROR] Renderer exited with error: No error.
[0h 0m 0.1s] [ERROR] [RTRenderer::loadGPUPlugin] -1: Failed to create CUDA renderer plugin instance.

I have the recommended 461.09 driver.
GeForce RTX 2080 Ti and Threadripper 2990WX

Hybrid works like Russian roulette, no one knows when it will fire.

Anyone have any ideas what it could be?

[shaio]

Makushimu I was able to reproduce the crash and will strip the scene to find what is the causing it. I'll update you when I have more info on this one.

[shaio]

Makushimu the crash is caused because inside the Ecophone biały material inside your scene there is a non-existing texture inside the Filter shader. daniele_nicolaci was in the right direction and it is caused by missing textures but only the ones that are inside a filter shader. Please remove the non existing texture to stop V-Ray GPU from crashing until the issue is fixed.

[Makushimu]

Makushimu the crash is caused because inside the Ecophone biały material inside your scene there is a non-existing texture inside the Filter shader. daniele_nicolaci was in the right direction and it is caused by missing textures but only the ones that are inside a filter shader. Please remove the non existing texture to stop V-Ray GPU from crashing until the issue is fixed.

Thanks for your time.
Question: since cpu is able to render without any problems despite missing textures and paths, is it possible to repair hybrid rendering so that I can render without any problems, despite of missing textures? The only problem I have with gpu is that you need to be more careful to keep it running smoothly. It would be nice if you don't have to put more work into fixing texture connections that vray often loses itself, to run gpu with out errors.

[shaio]

Question: since cpu is able to render without any problems despite missing textures and paths, is it possible to repair hybrid rendering so that I can render without any problems, despite of missing textures?
The only problem I have with gpu is that you need to be more careful to keep it running smoothly. It would be nice if you don't have to put more work into fixing texture connections that vray often loses itself, to run gpu with out errors.

It is important to know that V-Ray and V-Ray GPU are two different render engines.
Not having issues with V-Ray doesn't mean that you won't have issues with V-Ray GPU. When using V-Ray GPU in hybrid mode it does use the CPU for rendering, but what V-Ray GPU actually does is to make the CPU being emulated as a GPU.
We won't be fixing the texture connections. What we want to fix the crash that is caused by the missing texture connections. That way whenever there is a missing texture V-Ray GPU won't crash and will let you continue the rendering despite the missing texture.

[daniele_nicolaci]

We won't be fixing the texture connections. What we want to fix the crash that is caused by the missing texture connections. That way whenever there is a missing texture V-Ray GPU won't crash and will let you continue the rendering despite the missing texture.

Hi Shaio,
this is just a personal opinion, but maybe a warning about a missing texture would be more helpful than continuing rendering and getting an unexpected final render.
Then you can decide to stop and fix the missing texture or continue rendering, but at least you are aware that something could be different than expected.

Regards

[Makushimu]

Hi Shaio,
this is just a personal opinion, but maybe a warning about a missing texture would be more helpful than continuing rendering and getting an unexpected final render.
Then you can decide to stop and fix the missing texture or continue rendering, but at least you are aware that something could be different than expected.

Regards

Yes I agree. My point was that it should be possible to render at all despite errors.
Reporting these errors before starting the rendering would be helpful, especially if it would indicate which texture is lost and in what material.