Meta Quest Link's virtual camera causes third-party applications to crash.[windows]

Hello! I have a couple of questions to ask you.

What source was put into OBS? Is it a specific Meta Link Virtual Camera? or is it a different video capture device?

If possible, could you provide a repro video?

My DMs are available for you to respond.

I just tried OBS Studio with my Q3 plugged in. It does show the Q2 and Q-pro virtual cameras as available, even when they are not available. I own a 2 and pro, they are not plugged in, so maybe it just remembered them.  Which seems odd. So I deleted the 2 and pro and got no error. Restarted OBS, and the non existing 2 and pro showed up again.

Then I tried deleting the Q3 camera (which shows no video, was connected, and was in the list). Deleted it. Nothing crashed.

Not sure if that means I misunderstood the steps, or just not happening to me.

It looks like the Quest drivers show all possible cameras it supports as available to be selected. Even when they are not currently available. And some software may have issues with that.

OBS Studio 31.1.2 (64 bit)

Hope this helps.

Even Unity sees the non existent cameras. And oddly, the only way you can find out in Unity that they do not exist, is to connect to them. Then wait a second and check if it is rendering. Then assume if it does not render that it is not really connected (or fails). There does not seem to be a failed exception or error. You just have to assume it does not exist when it fails to render anything. Not really the same issue, but maybe related or helpful in debugging. And his behavior is documented in the Unity WebcamTexture docs.

I am affected by this issue as well.

I write an application that enumerates DirectShow devices to present a list to the user so they can connect to them.

Since the last software update the users are now presented with 4 fake cameras.

Meta Quest 2, Meta Quest 3, Meta Quest 3S, Meta Quest Pro.

These devices obviously don't exist, this happens without the Quest connected to the system at all, I have not connected my Quest a single time since that update.

My application creates thumbnails of the connected cameras. Trying to open such camera causes a low level silent crash.

Please push another update as soon as possible to remove these fake DirectShow devices, they have nothing to do here.

Thank you.

DirectShow device enumeration: Meta Quest 2 (moniker:@device:sw:{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{1BA5C5B4-1BC8-4480-B2AE-B5EF1920EC8F}).
DirectShow device enumeration: Meta Quest 3 (moniker:@device:sw:{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{0FEDCBA9-8765-4321-0FED-CBA987654321}).
DirectShow device enumeration: Meta Quest 3S (moniker:@device:sw:{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{12345678-90AB-CDEF-1234-567890ABCDEF}).
DirectShow device enumeration: Meta Quest Pro (moniker:@device:sw:{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{A1B2C3D4-E5F6-7890-1234-56789ABCDEF0}). 

I have the same issue with any meeting rooms in firefox. google meets or ms teams meetings immediately crash the browser when i try to join, and all crash reports point to video capture devices. I have the same 4 virtual devices showing up. I havent found a way to delete these virtual devices without uninstalling the meta app