maxSwapchainSampleCount is 1 on Quest 2? No multisample swapchain images?
With deprecated Oculus API, it was possible to submit multisample textures. Now, with OpenXR, xrEnumerateViewConfigurationViews() tells that maxSwapchainSampleCount is 1. It means it's impossible to create multisample swapchain images (XrSwapchainCreateInfo.sampleCount must be 1). Is that correct? So, the only option is to render to other multisample framebuffer, then do `blit` to swapchain image?
unable to get grip button input on quest 1; getting path unsupported for spec-allowed binding
When I try `xrGetCurrentInteractionProfile` for `/user/hand/left` on the quest (v1), I get `/interaction_profiles/oculus/touch_controller` (as expected). However, when I try to suggest a binding for the path `/user/hand/left/input/squeeze/value` with `xrSuggestInteractionProfileBindings`, I get `XR_ERROR_PATH_UNSUPPORTED`. The openXR spec shows that this binding _should_ be supported here: https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#_oculus_touch_controller_profile , and further, specifies that it _MUST_ be supported through this line: "A runtime must accept every valid binding in the allowlist though it is free to ignore any of them." But to be clear, I'm not concerned with "spec correctness" for its own sake- I simply can't access the grip input on quest 1 with openxr at all until this is fixed. Is it true that there are just _no_ openXR applications available for quest 1 which use the grip button? or am I missing something elsewhere? If this is a bug, who can I contact to get this (major) issue resolved ASAP?OpenXR for quest, failing on xrCreateInstance
I've built for quest with the oculus openxr sdk, have explicitly loaded libopenxr_loader, got procaddr for xrInitializeLoaderKHR, it isn't null, I initialized the loader, but then it fails with XrResult = -1 on xrCreateInstance. The only way I've been able to debug is with logcat + printf. (I can print a message before xrCreateInstance and one after, and I only see the former). If there is some way to debug this, I would love to hear it (I've asked that question directly in another thread with no responses). Here is my backtrace, which isn't very helpful: (the "assert(0)" is what happens when xrCreateInstance fails) 08-16 15:00:39.390 23044 23044 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 08-16 15:00:39.390 23044 23044 F DEBUG : Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/821490.13210.0:user/release-keys' 08-16 15:00:39.390 23044 23044 F DEBUG : Revision: '0' 08-16 15:00:39.390 23044 23044 F DEBUG : ABI: 'arm64' 08-16 15:00:39.390 23044 23044 F DEBUG : pid: 23029, tid: 23043, name: phil.gnometower >>> com.dophil.gnometower <<< 08-16 15:00:39.390 23044 23044 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 08-16 15:00:39.394 23044 23044 F DEBUG : Abort message: '../../../../../gnomes/do_vr.cpp:156: void DoVR::init(DoConfig &, DoInfo &, struct android_app *): assertion "0" failed' 08-16 15:00:39.394 23044 23044 F DEBUG : x0 0000000000000000 x1 0000000000005a03 x2 0000000000000006 x3 0000000000000008 08-16 15:00:39.394 23044 23044 F DEBUG : x4 0000000000000000 x5 0000000000000000 x6 0000000000008080 x7 0000000000000038 08-16 15:00:39.394 23044 23044 F DEBUG : x8 0000000000000083 x9 0000007f94796450 x10 ea5c33b4d623965e x11 ea5c33b4d623965e 08-16 15:00:39.394 23044 23044 F DEBUG : x12 0000000000000000 x13 0000000000000020 x14 ffffffffffffffdf x15 0000000000000008 08-16 15:00:39.394 23044 23044 F DEBUG : x16 0000007f9fbecec8 x17 0000007f9fb8ded0 x18 0000000000000000 x19 0000007f947964f8 08-16 15:00:39.394 23044 23044 F DEBUG : x20 0000000000000006 x21 0000007f94796450 x22 0000000000000000 x23 0000007f9b612954 08-16 15:00:39.394 23044 23044 F DEBUG : x24 0000007f947964d0 x25 00000000000fd000 x26 0000007f9ccf6448 x27 ea5c33b4d623965e 08-16 15:00:39.394 23044 23044 F DEBUG : x28 0000007f9ccf6240 x29 0000007f94793d10 x30 0000007f9fb8ac84 08-16 15:00:39.394 23044 23044 F DEBUG : sp 0000007f94793cf0 pc 0000007f9fb8ded8 pstate 0000000060000000 08-16 15:00:39.414 23044 23044 F DEBUG : 08-16 15:00:39.414 23044 23044 F DEBUG : backtrace: 08-16 15:00:39.414 23044 23044 F DEBUG : #00 pc 0000000000079ed8 /system/lib64/libc.so (tgkill+8) 08-16 15:00:39.414 23044 23044 F DEBUG : #01 pc 0000000000076c80 /system/lib64/libc.so (pthread_kill+64) 08-16 15:00:39.414 23044 23044 F DEBUG : #02 pc 0000000000024ac0 /system/lib64/libc.so (raise+24) 08-16 15:00:39.414 23044 23044 F DEBUG : #03 pc 000000000001cdcc /system/lib64/libc.so (abort+52) 08-16 15:00:39.414 23044 23044 F DEBUG : #04 pc 0000000000021978 /system/lib64/libc.so (__libc_fatal+104) 08-16 15:00:39.414 23044 23044 F DEBUG : #05 pc 000000000001d168 /system/lib64/libc.so (__assert2+48) 08-16 15:00:39.414 23044 23044 F DEBUG : #06 pc 00000000000d04d4 /data/app/com.dophil.gnometower-1/base.apk (offset 0x1000) 08-16 15:00:39.414 23044 23044 F DEBUG : #07 pc 0000000000059a1c /data/app/com.dophil.gnometower-1/base.apk (offset 0x1000) 08-16 15:00:39.414 23044 23044 F DEBUG : #08 pc 000000000005b384 /data/app/com.dophil.gnometower-1/base.apk (offset 0x1000) 08-16 15:00:39.414 23044 23044 F DEBUG : #09 pc 0000000000133a88 /data/app/com.dophil.gnometower-1/base.apk (offset 0x1000) 08-16 15:00:39.414 23044 23044 F DEBUG : #10 pc 0000000000076454 /system/lib64/libc.so (_ZL15__pthread_startPv+204) 08-16 15:00:39.414 23044 23044 F DEBUG : #11 pc 000000000001e204 /system/lib64/libc.so (__start_thread+16)
