Input System and Pointer Pos/Rot
Hi there! Recently i found a bug that arrived with latest Oculus integration package. I can't tell exactly wich one but around V55. So, input system is broken when importing the Oculus integration or Meta XR package. Pointer Position and Rotation will gone and missing if we use Oculus, 4-5 month ago it worked well. First picture, without Oculus SDK/Meta XR After importing SDK:Developer Mode - Android Apps - Documentation on iteraction methods?
Hi support team, I'm testing traditional Android apps on Meta Quest 3 to solve some of my needs (specifically remote desktop at this time). I was able to install and run some apps. However, I'm confused when it comes to app touch input. Is there documentation explaining how controllers and direct touch works with Android apps? So far I've found this: B = back button A = tap where the pointer is Trigger = tap where the pointer is 2 triggers + move controllers - pinch-zoom I tried coming closer to the screen and tapping with 2 fingers at once - this doesn't seem to have any effect. Can you confirm? While testing NoMachine Client app, I was able to do right click (done with 2-finger tap) only once, and I did not understand how I did it. Can you provide some guidance? Can I do 2 finger tap with controllers or hands? What about 3 finger, 4 finger? Additionally, can you please allow resizing windows in "Near" view just like they can be in "Far" view? Essentially I'm looking for a direct-touchable remote desktop, and the issues mentioned above really limit my options.
Which input system to use with Movement SDK
I'd like to experiment with the Movement SDK. The readme indicates Oculus Integration is a prerequisite.and that package uses the new input system (UnityEngine.InputSystem). The Movement SDK, however, is uses the old input system (UnityEngine.Input). Which system should I use?Memory Error when opening the overlay menu
While monitoring the Android logs, and running my Unity Quest game, and pressing the Oculus button to open the overlay menu, I get this wierd memory error: error getting shared memory region, memory type: Controller, failed with Status(-1, EX_SECURITY): 'requested shared memory When this happens, the game stops receiving controller and headset inputs, so the entire screen freezes that is incredible jarring. Any idea how to solve this? I guess it has something to do with the Focus Aware, and how the Input System works, as it only receives input while being active? I'm using Unity 2021.2.7 with OpenXR Plugin v1.3.0 and the "New" Input System.
Dumping QWERTY and porting an alternative text entry system to Oculus
It seems that we are about to continue using QWERTY for text input, even though we are entering a completely new technological era with VR/XR/Oculus/Metaverse. Puleeeeeze! Let's NOT! About two centuries ago, QWERTY was purposefully designed to slow down typing! It's time to put it to rest. There are much, much more efficient alternatives for a single finger/hand full text entry, more suitable for VR/AR. Our imminent technological transformation begs for a commensurate technological innovation. My question is, given that a non-qwerty input tool is implemented and available for Android, what's the easiest way to port it from Android Studio to Oculus?Is there a way to invoke the keyboard overlay in a VR app not made with Unity or Unreal?
In the documentation, there seems to be a way to open the keyboard overlay for Unreal and Unity development: https://developer.oculus.com/documentation/unreal/unreal-keyboard-overlays/ https://developer.oculus.com/documentation/unity/unity-keyboard-overlay/ However there is no indication on how to do the same with a third party engine or app written without using those two solutions, I couldn't find anything in the Mobile SDK docs: https://developer.oculus.com/documentation/native/android/mobile-intro/ Is this functionality available? Thanks in advance for your help!
