Render issue, one area is not rendered properly

[cedric_vaucher]

Hello!

When rendering this scene (you may recognise it ), one area of the final image remains unrendered. I've tried several render settings (bucket, progressive). When rendering a region only, it gets through fine... When hiding all props and leaving only the walls, it's also ok... The carpet uses V-Ray fur and the center portion of the wall is displaced.

Any solution would be appreciated !
Cheers

[sirio76]

Don’t know what is causing the issue, in the past I had this problem with specific ies file. As a temporary fix try to disable the adaptive lighting and set the mode to full evaluation, usually it solves this kind of problems.

[cedric_vaucher]

Hi Sirio,

Yes, we tackled the IES issue some days ago. I've disabled the "adaptive lighting" (Render Settings/V-Ray/Overrides/Lights(Light Evaluation Mode: Full Evaluation) and it indeed looks alright now. Not sure about the increased render time though....

[shaio]

Hey cedric_vaucher
This is odd. What V-Ray version are you using, also can you please check the Console log to see if you have any warnings or errors? A few versions ago we had an issue that was causing this type of behavior, and it was mainly because there were invalid or NaN pixels in the rendering but was fixed, so if you're not using the latest version please try updating, otherwise we need to look into the scene if there are no clues in the logs. If you have any render elements in the scene could you please check them as well since I'm sure they will be affected as well and this might help us find the cause of the behavior.

[shaio]

Hi Sirio,

Yes, we tackled the IES issue some days ago. I've disabled the "adaptive lighting" (Render Settings/V-Ray/Overrides/Lights(Light Evaluation Mode: Full Evaluation) and it indeed looks alright now. Not sure about the increased render time though....

Most of the issues with the adaptive lighting were solved with the new V-Ray core (not sure which version you're using here), but there still could be some cases (like with specific IES lights) that could cause this behavior, so we might need to check the scene in this case and see if we can reproduce it and try fixing the issue.
As for the increased render time in Full evaluation mode... this is expected, especially if you have more lights in the scene since the goal of the Adaptive light mode is to select and evaluate only the lights needed for the current view and excluding the ones you don't need in a smart way which helps reduce render times.

[cedric_vaucher]

It's time consuming... I'll have a look later - stand by!

[sirio76]

Not sure about the increased render time though....

The adaptive lighting provides large speed gains and depending on the scene setup that can be huge, so you should always keep it on unless you have this kind of issues. That being said, try to install the latest build as suggested by Ivan, I haven’t seen this problem for a while.

[sirio76]

It's time consuming!

Not really, installing a new version take no more than a minute I suggest you to do that at least once a month since improved Vray versions are released every couple days on the nightly build site.

[cedric_vaucher]

This is the only error in the log file: [09:50:46.201] Warning : Material "Metal_mtl_BCD07401C26A16074E4DB712D8250000@ma teri al" produced overbright or invalid color (rgb=nan nan nan) [x=770.839, y=400.951].

New version does NOT the trick.

I tend to wait with updates, because I had some seriously time consuming issues after updating... (you know the feeling, being a guinea pig, with no way back...).

[sirio76]

with no way back

The builds on the nightlies website should not be considered as beta versions, usually there are no big problems and severe issues are fixed in a few days, but just in case do like me before upgrading.
Go to Vray menù > help > about, this will tell you what release you are using:



Then update to the new version. If for any reason you encounter serious problems you can easily revert to an older build by going on the nightlies website and choosing the corresponding version, then revert to the older build:

[cedric_vaucher]

Well well

the error still remains after updating.
How can I post the scene and the error log?

[shaio]

The forum has a limit in file size, so I guess it will be best to share them with a link here or a PM to me via some cloud service you feel comfortable with (Dropbox, Google drive, etc) which could be faster for me to get the scene or you can contact our support (there is a submit request button in the upper right corner) and send it there alongside a link to the forum. Thank you for the feedback and the help.

[sirio76]

Well well

the error still remains after updating.
How can I post the scene and the error log?

That build is from a month ago, try the latest one

[cedric_vaucher]

Hi Sirio

Today's build is not doing it either. I have submitted a support request.

[shaio]

What macOS version and hardware do you use, also if you happen to use an M1 arm device do you start Cinema 4D with Rosseta or do you run it natively? Knowing the exact Cinema 4D version would also be helpful when we debug the scene trying to reproduce the issue.