Rendering-Times Interior

[fixeighted]

I'm on Max but my guess is that it is the 'Trace Depth' (defaults to 5) levels in GPU performance settings - set it to a higher number and that may fix the 'weird' window situation....

[YunalZobu]

Also I have transparency Issues when rendering the same scene with GPU. When rendering with CPU I can see through the Window onto the roof. But when rendering the same sfene with GPU I can clearly see everything through the window when Light Cache is built but when rendering Starts, something weird is going on.

If I understood it right, this setup (see the attached image) does not render properly on your side?
That's a gpu rtx render with Update 1.

[shaio]

Also I have transparency Issues when rendering the same scene with GPU. When rendering with CPU I can see through the Window onto the roof. But when rendering the same sfene with GPU I can clearly see everything through the window when Light Cache is built but when rendering Starts, something weird is going on. I cant even explain what happens.

V-Ray and V-Ray GPU are two separate renderers, and they should be accepted as such. Whenever you start a project and chose your render engine, you should stick with it. A lot of the algorithms that are calculating different aspects of the scene are vastly different for GPU devices compared to CPU devices because of the different architecture therefore in some case one of the engines will be fast, where in others not so fast. I can give you as an example the Min/Max subdivisions of the Bucket sampler. If you use the Min=1 and Max=24 values on V-Ray GPU the same way as you use them with V-Ray, you won't get the same noise amount as you would get with V-Ray only. And this isn't because one is of the engines is faster than the other. It is because they're using different approaches.
Nowadays, V-Ray GPU supports a large portion of the available features for V-Ray, but this doesn't make them and won't make them the same render engines.
I'm starting to think more and more that we should really separate the two engines fur our future releases.

Also waiting so Long for responses. Dont know exactly why. When I post something in the Redshiftforum its answered after 2-3 hours or so. Also they give me full advice and analyze things.
Maybe V-Ray for c4D is still not being taken seriously. Its a real pain. Even Chaosgroup must SEE that so many people are unhappy. It would just Help a lot and give hope if they just be more transparent.

I'm sorry to hear you still think that we're not taking everything seriously, even after the poll that you initiated and after seeing how much of the features from the same poll went in the Update 1 release of V-Ray 5. We will of course continue to work on improving V-Ray and do our best as much as we can.

As for the scene, I've started to look in to it and see what could be the problem for the lost transparency on glass with V-Ray GPU. Checking the rendertimes would take some time, since I need to do a few renderings until I see if there is something that could be optimized for the materials or anything else in the scene.

[shaio]

Also I have transparency Issues when rendering the same scene with GPU.

I've checked the scene about the transparency and as suspected you've reached the internal limit of maximum depth for refraction, which for V-Ray GPU is 16. I've counted around 24 polygons with glass material that the rays should pass through and after the 16th it starts to render black. It just happens that we're currently working on overall improvements on V-Ray GPUs core, and they will lead to the removal of this limitation.

[PdZ]

Ah thank you very much shaio . That explains what is happening here. But this helps me to figure out a workaround.
And to be clear: Iam just a stubborn guy. I sometimes go overboard with my expectations. Iam very happy how development is going right now! Thank you very much that you looked into the scene.