10-13-2022 01:15 AM
Hi,
I just got the K375s and it works fine in the Meta Quest 2's general environment but somehow it is not possible to use it Horizon Workrooms. Should I return it or is K375s support will be implemented soon?
Thanks
10-13-2022 06:00 PM
Hey! We see you're having issues with connecting your K375s keyboard. This is not the experience we want you to have. We know the time this is taking away from being able to use Horizon Workrooms. Let's work together to get you back on track!
Please go ahead and try and redownload the Meta Quest Remote Desktop and please click here for more steps. If these steps did not work and you're still experiencing issues please let us know so we can provide you with more help!
10-14-2022 09:00 AM
Hi. I'm having the same/similar issue.
I just purchased a K375S as it was a recommended keyboard.
I paired it with the device under settings no problem, but when I go into Workrooms it only gives me the option to use the Logitech K830. I've tried re-downloading Horizon Workrooms, unpairing and re-pairing the keyboard, updating the quest 2, but nothing seems to work to let me use it.
10-14-2022 11:11 AM
Same here, somehow it doesn't seem to be supported in Horizon Workrooms when it is supported in the Quest's main environment. Like the left hand doesn't talk to the right hand😅
10-14-2022 01:32 PM
Exactly - I understand if it was added/removed in a previous update, but it would be nice to know.
If Oculus Support could just provide information, it would be greatly appreciated.
I am using:
Workrooms V1.6(47)
Software Version 46.0.0.226.0.406523063
System Version 47421700667400000
Is there a newer version being rolled out that has support for the Keyboard, or was this Keyboard removed from a certain version?
I mainly want to know whether I should be sending back my new keyboard if support has been removed.
10-20-2022 06:36 PM - edited 10-20-2022 06:37 PM
Wow, today's "Hoziron Workrooms" update added K375s support! Everyone try it!
10-21-2022 03:09 AM
Indeed, I just tried and it does work now. Thanks for the heads up.