oculus system keyboard not working using bluetooth keyboard
I try to develop application in quest 3 using unity engine, but when I use system keyboard in oculus it just work for virtual keyboard. When I click input field the virtual keyboard shows up, but when I try to type with my bluetooth keyboard that connected to my quest, it won't work for typing any more. any help?
Bug Report: Accumulation of Black Passthrough Quads due to OVRTrackedKeyboard
I'm using the Meta All-in-one SDK (v62), and there's a minor bug that is impacting the user experience. Whenever a keyboard is loaded, it creates a passthrough "Quad" with it. The problem arises when it creates a new "Quad" without destroying the existing one, leading to the scene accumulating numerous black passthrough Quads. You can easily reproduce it by toggling "KeyboardQueryFlags" between Local and Remote repeatedly. Its in OVRTrackedKeyboard.cs Script, function : LoadKeyboardMesh() variable : passthroughQuad_
[Feature Request] Integrate Tracked Keyboard with Meta Remote Desktop
I've been experimenting with Tracked Keyboard (Logitech MX Keys Mini) and Workrooms recently and have noticed a few UX/usability issues. The tracked keyboard communicates directly with the Quest, which makes perfect sense if you plan to use it as a direct input while using the Quest. However in Workrooms, when you bring your PC (or Mac in my case) in to the workroom, the keyboard does not control the PC. This is a major source of friction from a usability/UX perspective. A possible solution, and hence the feature request, would be to integrate the tracked keyboard with Meta's Remote Desktop app as the intention in this scenario is to control and directly input in to the PC. This way the user sees the keyboard (passthrough), the keystrokes are inputted directly to the PC, and Remote Desktop can pass keyboard events, positioning, etc. to the Quest. It does throw up the issue of two modes of Tracked Keyboard (one directly to Quest, the other to Remote Desktop), however cognitively this is easier for a user to manage than having two separate keyboards on the same desk (one for the Quest another for the PC), or to have the disconnect that the Tracked Keyboard doesn't directly control the applications on the PC that are brought in to Workrooms. I hope this helps. rgds DaveCustomized Tracked Keyboard
Hello All, I frequently use the Quest 2 for productivity, and while the black-and-white passthrough is just fine for keyboards, I would much prefer the tracked option. However - and I am sure I am not alone in this - I am an avid mechanical keyboard enthusiast, so none of the supported tracked keyboards are even close to what I am using. Are there any development resources available to create tracked keyboard packages for the Quest 2? I cannot find any reference material on the subject, only instructions for connecting supported keyboards. Thanks, Alex
Tracked Keyboard SDK for UE5
Is there a way to get the Tracked Keyboard SDK working in Unreal Engine 5? I didn't know if there was an alpha or beta plugin available that I could try out with the Logitech K375s. If not is there a way I could extend the plugin in github and add this capability myself? I tried using passthrough by itself but its so blurry that it is not really suited to type a paragraph. The Keyboard SDK is perfect but I can only find Unity or Native examples.
