Hi @demonixis
Thanks for all the work you have put in developing OXRSys. I've been testing OXRSys on an Apple Silicon Mac and wanted to report some of my findings.
Test Environment
Mac Studio (Apple Silicon)
macOS Sequoia 15.7.4
Meta Quest 2
OXRSys 1.2.0
Windows OpenXR application running under a Wineskin wrapper
Quest
Successfully completed:
Developer Mode enabled
USB Debugging enabled
ADB installed and working
adb devices reports:
oxrsys-quest-1.2.0.apk installs successfully.
Quest application launches correctly.
Quest displays:
Waiting for server
Runtime JSON
The supplied oxrsys-runtime.json contains:
"library_path": "/Users/yann/projects/openxr_osx/build/runtime/liboxrsys-runtime.dylib"
This path does not exist on another machine.
I changed it to my local runtime path:
"library_path": "/Users//Downloads/openxr-osx-runtime/libopenxr_osx.dylib"
Was the developer path included in the release by mistake?
OXRSys Home
OXRSys Home crashes immediately on launch.
Crash report:
Termination Reason: Namespace DYLD, Code 1
Library missing:
/usr/lib/swift/libswift_DarwinFoundation1.dylib
Running:
otool -L "OXRSys Home"
shows the executable is linked against:
/usr/lib/swift/libswift_DarwinFoundation1.dylib
This library is not present on macOS Sequoia 15.7.4, so the application terminates before launching.
Not Working:
OXRSys Home crashes immediately due to the missing Swift library.
The Mac-side server never starts.
Questions
Is OXRSys Home responsible for starting the server that the Quest connects to?
Can the server be launched independently from the command line?
Is the libswift_DarwinFoundation1.dylib dependency expected?
Was the runtime JSON intentionally released with the developer build path?
I'm happy to test development builds or provide additional logs if that helps.
Hi @demonixis
Thanks for all the work you have put in developing OXRSys. I've been testing OXRSys on an Apple Silicon Mac and wanted to report some of my findings.
Test Environment
Mac Studio (Apple Silicon)
macOS Sequoia 15.7.4
Meta Quest 2
OXRSys 1.2.0
Windows OpenXR application running under a Wineskin wrapper
Quest
Successfully completed:
Developer Mode enabled
USB Debugging enabled
ADB installed and working
adb devices reports:
oxrsys-quest-1.2.0.apk installs successfully.
Quest application launches correctly.
Quest displays:
Waiting for server
Runtime JSON
The supplied oxrsys-runtime.json contains:
"library_path": "/Users/yann/projects/openxr_osx/build/runtime/liboxrsys-runtime.dylib"
This path does not exist on another machine.
I changed it to my local runtime path:
"library_path": "/Users//Downloads/openxr-osx-runtime/libopenxr_osx.dylib"
Was the developer path included in the release by mistake?
OXRSys Home
OXRSys Home crashes immediately on launch.
Crash report:
Termination Reason: Namespace DYLD, Code 1
Library missing:
/usr/lib/swift/libswift_DarwinFoundation1.dylib
Running:
otool -L "OXRSys Home"
shows the executable is linked against:
/usr/lib/swift/libswift_DarwinFoundation1.dylib
This library is not present on macOS Sequoia 15.7.4, so the application terminates before launching.
Not Working:
OXRSys Home crashes immediately due to the missing Swift library.
The Mac-side server never starts.
Questions
Is OXRSys Home responsible for starting the server that the Quest connects to?
Can the server be launched independently from the command line?
Is the libswift_DarwinFoundation1.dylib dependency expected?
Was the runtime JSON intentionally released with the developer build path?
I'm happy to test development builds or provide additional logs if that helps.