Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: Johnny Em on 2022-02-03, 09:04:35

Title: Flicker in animation caused by physical glass material
Post by: Johnny Em on 2022-02-03, 09:04:35
Hello, I have a problem with an animation I was working on, with flickering, that I believe is caused by the Corona physical glass material I had in the openings. The workaround I found, was to replace the glass material with a legacy one. I have already managed to successfully reproduced the bug in a clean, scene that I uploaded with the following name "1643873698_glass-test.rar" with the private uploader. The animation was distributed in 5 PCs with Thinkbox deadline and I am using 3Ds Max 2021.3. Is this a known issue? Because I couldn't find anything in the forums. Could this bug has implications in other scenarios? I have attached two videos showing the flickering.
Title: Re: Flicker in animation caused by physical glass material
Post by: GeorgeK on 2022-02-03, 17:13:19
Hi Johnny and thanks for reporting this, we are aware of this issue and I believe it's already addressed, please stay posted.

(Report ID=CRMAX-1120)
Title: Re: Flicker in animation caused by physical glass material
Post by: Deckard on 2022-02-04, 08:30:23
I came across the same issue a few weeks ago, when sending animation frames to render farm:
https://forum.corona-renderer.com/index.php?topic=35314.msg193881#msg193881
I ended up using the same workaround (replacing the glass material with a legacy one).

GeorgeK, when you say it's already addressed, what do you mean? Will it be fixed in the next Corona release?
Title: Re: Flicker in animation caused by physical glass material
Post by: GeorgeK on 2022-02-04, 11:45:18
I came across the same issue a few weeks ago, when sending animation frames to render farm:
https://forum.corona-renderer.com/index.php?topic=35314.msg193881#msg193881
I ended up using the same workaround (replacing the glass material with a legacy one).

GeorgeK, when you say it's already addressed, what do you mean? Will it be fixed in the next Corona release?

It's already fixed, it should be included in the next public daily, we will notify you here.