Feed groups = None

[A00107408]

When I run in Unity, the feed groups are detected as seen above.
When run on the HMD over WIFI the Feed Group drop down menus only have "none".

[milanwulf]

Since the correct groups are at least displayed in Unity, you probably have OBS set up as described and shows that NDI feeds are being sent. The websocket connection has nothing to do with the video streams (NDI) and is only used to control OBS and update the user interface. The fact that you cannot select the NDI groups on the headsets has probably something to do with your network. The best thing to do is to check that you can receive the NDI streams on any device other than the headset. For example, another computer or an iOS/Android device - if you search for "NDI Viewer" you will find plenty of apps for this. If no NDI streams appear there either, check your WiFi network settings.

[A00107408]

I can see the NDI feeds on my IPhone using an app over the WIFI network. It seems to not be a network issue but rather something with the Quest HMD. I have tried the Quest 2 and Quest 3. Do you recall if there are any further configurations required to the Quest 3 or to any other elements of the project that are missing from the ReadMe?

[milanwulf]

Interestingly, it worked fine for me when this issue was opened, but now I have the same problem with the standalone build. As I have tested it on three different networks - and the NDI streams can be received on other devices such as my smartphone - it can only be the headset itself. I strongly suspect that Meta has blocked the necessary ports in a firmware update (according to NDI the following are required: 5353, 5959, 5960, 5961 and above). I have also tried another build that only receives the NDI streams, but unfortunately this does not work either. However, the websocket connection works fine. I will continue to look for a solution, otherwise for the time being my application can only be run directly in Unity via Meta Quest Link (passthrough can be enabled in the Meta Link settings). I will continue to search for a solution, any hints are welcome.

[milanwulf]

Potential solution: After trying all day to figure out what the problem might be, I noticed that sometimes my headset would automatically connect to a different saved WiFi network, after switching back to the correct network it suddenly worked again!
Maybe you can try changing the network while using the application and see if this works for you and give me feedback.

I also added a new version with a dedicated NDI refresh button.