error while loading shared libraries: libBufferedSocket.so.0.1

[le-patenteux]

First of all, let met start by saying THANK YOU for your work on making such an important piece of software and making it cross platform!
As a Linux user, I can't believe VR mixed reality tools have not made their way in our ecosystem yet!

Now, with my issue... I was able to build the project from your code (had to add cmake and qt libraries first but it made it through after that)

When I run it from the "install" folder, I get this error:
./RPMixedRealityCapture: error while loading shared libraries: libBufferedSocket.so.0.1: cannot open shared object file: No such file or directory

Since I don't know where it is looking for the file, from this error, I can't fix it... but a simlink to the file is in the install folder alongside the RPMixedRealityCapture binary...

Any help would be greatly appreciated!

[le-patenteux]

Oh wait... I did this trick nd it launched!:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/RPMixedRealityCapture/install/libBufferedSocket.so.0.1

Maybe something is missing in the build scripts to tell it where to find it!

Now I have to try it!!!

[RandomPrototypes]

Hello,
I'm happy to see linux user here, I don't think there are many among VR users.
The buildWithDeps script is supposed to configure everything automatically, it's weird that it doesn't find the libraries. Did you got any error message during the install? Maybe a conflict somewhere... Which distribution do you use? cmake version?
But yes, a "export LD_LIBRARY_PATH..." can fix these problems.

Btw, I didn't test recently but it seems the official calibration app on quest is not working properly anymore. You can have a look at these explanation from RealityMixer project :
https://github.com/fabio914/RealityMixer/blob/main/Additional-instructions.md
I think the option 1 would be the easiest, but I can have a look and help you if you get any problem.

[le-patenteux]

Thanks for taking the time to answer me! Yes, I switched to using only Linux in 2020 and never looked back!
If the Oculus Quest1 I own could run Linux reliably, I would convert it! (Whenever I see the Meta logo it makes me want to throw-up!!!)

My setup:
Rig #\1 is an AMD APU and rig #\2 is and Intel CPU with AMD RX-5700 XT GPU
Both rigs
Pop!OS 22.04 (based on Ubuntu 22.04)
X11
cmake version 3.22.1

I did not have time to report on my tests, but the program started and I could get into the calibration window.
After the calibration, when in "review calibration" mode... I see the camera, but no red or blue circles...
So I guess this is the bug you were talking about ?
Also, in the terminal it repeatedly says it is receiving video at 0fps

[RandomPrototypes]

It may be this bug but I'm not sure. I'll test it again during the weekend. You may try the "SoapyMan" calibration app on quest instead of the official as indicated in the other post.

Sadly, this app has not been tested by many people. It works fine on my ubuntu and a few windows, but I think you are the only other person to test it on linux.

If you are ok to do some testing, we can try the command-line version first that will give us more detail about what happens.

The command-line tools are in the demo folder of libQuestMR :
https://github.com/RandomPrototypes/libQuestMR/tree/master/demo

We can start by demo-connectToMRC to test if we can communicate with the calibration app on the quest. You just need to call "demo-connectToMRC ipAddr" and it should write all the headset and controller pose update messages.

[RandomPrototypes]

I did a quick testing during this weekend.
For me, the calibration process worked up to "review calibration" (the red and blue circles appear) with the official app.
Copying the calibration file to the game folders is probably not working with the official app, I'll have a look on how to make it easier (the alternative app was difficult to run and not sure if it work or not yet). I'm thinking to embed adb in my software so the calibration process would just require to plug the usb cable to fix the problem.
I could not get the video feed from beat saber but it worked in another game so I'll have to verify it too.

[le-patenteux]

Okay, tell me if I can help!
I could not play around with this last weekend... I was busy!

EDIT:
I sent a picture of the snowfall but for some reasons Github won't add it...
Anyways, there is a LOT of snow here, I was outside!

[RandomPrototypes]

I'm implementing the new method to fix the bug but it will take a few weeks because I'm quite busy.
You can already try the command line tools like demo-connectToMRC to see if you can connect and communicate properly with the quest.

[le-patenteux]

Thank you for your dedication!
I have to admit I am on a sprint before Christmas so I might end-up trying again at the end of December... So take your time!

[RandomPrototypes]

Good news is that I succeed to implement an easier way to update the calibration (you'll need to transfer xml file only one time, then it can be updated automatically).

Bad news is that it seems some games (such as beat saber) totally removed the support for mixed reality in recent updates (maybe it's possible to downgrade to older version, I didn't try).

[le-patenteux]

Bad news is that it seems some games (such as beat saber) totally removed the support for mixed reality in recent updates (maybe it's possible to downgrade to older version, I didn't try).

What?... are you serious?... That means Liv-VR too can no longer work with Beat Saber??? That would be stupid!