Chaos cosmos people (material) looks different depends on camera

[mrsacan]

I think this could be related to vram somehow, but it only happens for a single camera.
Any ideas?

[mrsacan]

If I change to perspective (P) and pan a little, it fixes

[mrsacan]

This is not an urgent issue (I already completed the job) but I'm curious, any theory about this?

[romullus]

I think you should report a bug and provide a scene where the bug is happening. This clearly does not look like expected behaviour. https://support.chaos.com/hc/en-us/requests/new

[maru]

I am guessing (but just guessing) that your camera is somehow placed inside a volumetric material such as glass without "thin" option. To fix that, you can run a script which will globally disable volumetric effects in your materials (but not it may also "break" materials which are supposed to be using volumetrics so it's best to save a scene backup):
https://forum.corona-renderer.com/index.php?topic=41371.msg219089#msg219089

Here is a similar case:
https://forum.corona-renderer.com/index.php?topic=41610.0

We are working on detecting this and handling it automatically or through a notification as we understand it is not expected from user point of view.

[mrsacan]

So I read your replies and other thread, then started to delete objects one by one.
Found the guilty one, it's a chaos cosmos tree (I didn't noticed because it came as wire bounding box, as default), it still doesn't make sense to me though, because camera doesn't look like inside/intersect with the object.
Since I was able to recreate with just people & tree & camera & sun, I converted those to meshes, archived and sent you the file.

[maru]

Does the tree have some volumetric effects enabled? (refraction, absorption, scattering)

[Avi]

Hi,

It seems like there some issue with distance value being empty in the Volumetric scattering section in the Corona physical material. Please see the video for a temporary fix for such issues.

We have logged this as a bug in our system to be reviewed by our devs. We will let you know as soon as we have any update on this issue.

(Report ID=CMAX-895)