No connection to Quest

[tonyschuite]

I have tried the MRC Tools setup. There is no connection to be found both using discovery as well as manual IP. I have tried pinging the device, wich works so the connection is valid. Any Thoughts?

Windows 10, Private network with firewalls turned off.

[gongxinheng]

I have tried the MRC Tools setup. There is no connection to be found both using discovery as well as manual IP. I have tried pinging the device, wich works so the connection is valid. Any Thoughts?

Windows 10, Private network with firewalls turned off.

Hi Tony, Did you open the Mixture Reality Capture app in Quest and made sure the ip address showed in the app was exact the same you tried to match to? The app link

[tonyschuite]

Oh wow!! Totally missed that in the instructions. I will try tomorrow.

Thanks for the reply! Kind regards Tony

Sent from my iPhone

On Feb 12, 2020, at 18:47, Hengstar notifications@github.com wrote:

 Hi Tony, Did you open the Mixture Reality Capture app in Quest and made sure the ip address showed in the app was exact the same you tried to match to? The app link

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[gongxinheng]

Cool, let us know if this works.

Thanks, Hengstar

[tonyschuite]

Ok, so I got some sort of calibration and using OBS I can connect to the MRC app. Next step is to somehow integrate it into my unity project. I have a basic unity app with the MixedRealityCapture Scene from the oculus asset. There is no connection possible.

Any suggestions?

Kind regards

Tony Schuite • Docent, Werkplaats Performatieve Media (K3), Voorzitter OC Theater T 030 209 17 09 • M 06 14498448 HKU Theater • Postbus 1520 • 3500 BM Utrecht • www.hku.nl

aanwezig • dinsdag t/m vrijdag

On 12 Feb 2020, at 20:05, Hengstar notifications@github.com wrote:

Cool, let us know if this works.

Thanks, Hengstar

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/facebookincubator/obs-plugins/issues/5?email_source=notifications&email_token=AAOPNCL23AE2MRZTARC3ZQDRCRB6XA5CNFSM4KTDO3S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELR7W7I#issuecomment-585366397, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOPNCPIQQXINYSJD3HNCDDRCRB6XANCNFSM4KTDO3SQ.

[gongxinheng]

@xwovr, I think this is the question for you.

[xwovr]

@tonyschuite Can you try SuperHot on Oculus Store to see if OBS can connect to it? If it does work, please verify if there is in the manifest of your test app.

[HellgaM]

Installed plugin yesterday with Oculus Quest 1 (with all latest updates), OBS won't connect to Oculus with "check IP..." message, however IP match to Oculus IP. However, Oculus Calibration Tool is shown in OBS, but when you want to catch BeatSaber - can't connect. Is there a way to check logs, something to find the reason why?

@xwovr Grateful for any help you can suggest!

[xwovr]

Could you run "adb logcat -s OVRPlugin OVRMrcLib" and then execute BeatSaber, to see what's dumped in the log?

[HellgaM]

I was able to connect using 5555 port, however, still do see a green/blue screen and sidequest log part says:

`.073  1085  1085 D OVRPlugin: nativeBatteryEvent(2, 45, 310)
10-04 00:18:31.073  1085  1204 D OVRPlugin: Developer mode: 0
10-04 00:18:31.074  1085  1106 I OVRPlugin: HandleVrapiEvents: Unknown Event.
10-04 00:18:31.130  1085  1106 D OVRPlugin: User present: 1
10-04 00:18:31.132  1085  1106 D OVRPlugin: HMD present: 1
10-04 00:18:31.456  1241  1241 D OVRMrcLib: ovrVulkanLoader::Unload

` where everything is "loaded" till "OVRPlugin: HandleVrapiEvents: Unknown Event." is this something you may know about?

Thank you in advance!

[xwovr]

"OVRPlugin: HandleVrapiEvents: Unknown Event." is not anything need to worry about. However I noticed that you are using Vulkan. There are some known issues when using MRC with Vulkan which are on the list of our "pending fixes". It would be worth to switch to GLES3 and see if it helps.

[HellgaM]

How would I do that? I've BeatSaber purchased, Mixed Reality Tool and OBS with plugin instaleld.

OBS don't show any issues:

`14:54:59.652: Switched to scene 'Quest MRC' 14:54:59.652: ------------------------------------------------ 14:54:59.652: Loaded scenes: 14:54:59.652: - scene 'Quest MRC': 14:54:59.653: - source: 'Background' (group) 14:54:59.653: - filter: 'Crop/Pad' (crop_filter) 14:54:59.653: - filter: 'Color Correction' (color_filter) 14:54:59.653: - source: 'Oculus MRC' (oculus_mrc_source) 14:54:59.653: - monitoring: monitor and output 14:54:59.653: - source: 'Video Capture Device' (dshow_input) 14:54:59.654: - filter: 'Chroma Key' (chroma_key_filter) 14:54:59.654: - filter: 'Render Delay' (gpu_delay) 14:54:59.654: - filter: 'Color Correction' (color_filter) 14:54:59.654: - source: 'Foreground' (group) 14:54:59.654: - filter: 'Crop/Pad' (crop_filter) 14:54:59.654: - filter: 'Chroma Key' (chroma_key_filter) 14:54:59.654: - filter: 'Color Correction' (color_filter) 14:54:59.654: - source: 'Oculus MRC' (oculus_mrc_source) 14:54:59.654: - monitoring: monitor and output 14:54:59.654: ------------------------------------------------ 14:54:59.831: --------------------------------- 14:54:59.832: [DShow Device: 'Video Capture Device'] settings updated: 14:54:59.832: video device: HD Pro Webcam C920 14:54:59.832: video path: \?\usb#vid_046d&pid_0892&mi_00#6&26a0dc56&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global 14:54:59.832: resolution: 1920x1080 14:54:59.832: fps: 30.00 (interval: 333333) 14:54:59.832: format: MJPEG 14:55:04.103: [OculusMrcSource 'Oculus MRC']: ConnectClicked 14:55:06.103: [OculusMrcSource 'Oculus MRC']: Unable to connect 14:55:32.148: [OculusMrcSource 'Oculus MRC']: ConnectClicked 14:55:34.149: [OculusMrcSource 'Oculus MRC']: Unable to connect 14:55:42.949: [OculusMrcSource 'Oculus MRC']: ConnectClicked 14:55:43.047: [OculusMrcSource 'Oculus MRC']: Socket connected to 192.168.0.105:5555 14:55:43.047: [OculusMrcSource 'Oculus MRC']: m_codecContext constructed and opened

however, there`s still green\blue screen, no picture from Oculus, and log cat for "OVRMrcLib" says

2020-10-04T12:14:24.461Z: debug15846/15846 OVRMrcLib ovrVulkanLoader::Unload

I did that using Sidequest log listener. What else may I have installed to figure out that issue?

[xwovr]

Sorry, I didn't notice that you were trying to capture from Beat Saber. I thought it's your own project. There is no way you can change graphics API in Beat Saber, and it already uses GLES.

From the log almost everything looks good. But it said "Socket connected to 192.168.0.105:5555". The port 5555 is not the default port, which should be 28734. So it seems likely you were not connecting to the game running on Quest.

If changing the port still doesn't work, you could grab all the lines in logcat with "OVRMrcLib" or "OVRPlugin". They would include the networking connection details on the device, which was missed from all the logs that you posted before.

[HellgaM]

Restored default port 28734 and as I see, I can't connect because Quest doesn't launch a kind of listener at 28734, I've recorded logs starting from Beat saber launch, trying of OBS connect, and logging stopped.

Logs are here (can't attach file here ) https://drive.google.com/drive/folders/1A2rCjuksCLZATX2eiNi-CTE5lur_DBLS?usp=sharing,

I hope with all my heart that you will see what's wrong, thank you for all your help!

[xwovr]

Sorry I can't find much valuable information from the logs you posted. Especially I can't find a log line that says if Quest was listening on the 28734 port or not. I have no idea what was wrong.

[bgarrison25]

I know this isn't helpful....but I am having the same exact issue. Months later. I can connect when the calibration tool is open but when i open up Beat Saber nothing. Yes I have selected the options to turn on MRC in beat saber. Yes I am connecting on port 28734. Not a clue how to run those log programs you were talking about up above.

[EthanZoneCoding]

I think I figured it out! Port 5555 seems to activate the listener. When I ran curl [ip]:5555, the stream started working.