Special webcam "auto greenscreen background" mode is stuck on, can't disable.

A few weeks ago, me and a friend of mine were in a private voice chat together and my friend noticed that he has a new option/feature for the camera in voice chat.

I did not have this option that he explained to me, so we assumed it was experimental and only some people got it. The feature was found under the little tiny circle button that is with the "turn on camera" button. Which when clicked on, reveals a context menu that normally allows you to pick which webcam device to use. That menu apparently had another section for a special feature that tried to "crop out" the background in my friend's webcam. So he could then add a custom image that would appear behind him. Essentially this was like an "auto green screen". Which I figured used some sort of Ai algorithm to try and figure out what to crop and what not to crop.

Anyway, today we had a voice call, and he turned on his camera and the background was still there. He wanted to show something, but the "feature" kept removing that object so you couldn't see what it was. He went to try and disable the auto green screen, or whatever It was called. And the menu option apparently wasn't there.

Of course, we were in a server voice chat this time, so maybe the bug is just that the option only shows up in private voice chats.

The reason I'm writing this is because I just want to let the devs know about this potential oddity/issue. I know there is a bug report page. But I also was wondering if anyone reading this could maybe also explain how to possibly disable this "auto green screen" thing for now. So he isn't stuck with it on. Because that's basically the big issue here, the feature is stuck enabled, but he wanted to disable it.

Also, the reason my friend isn't writing this message is because he tends to get frustrated quickly and doesn't really try to look further into the issue when it could be a very simple fix. 

I did not see info after many searches about other people having this issue, so I'm imagining this is VERY rare.