The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 907 - File: showthread.php PHP 7.2.34 (Linux)
File Line Function
/showthread.php 907 errorHandler->error




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TERRIBLE performance of TUNAI button + CooSpo sensor
#1
Sad 
I wanted to use VZFit on my Quest. Since the official sensor kit is no longer available (why?), I bought a cadence sensor and a media button for VZFit myself. To be sure that they would be compatible, I went with the devices listed at the top of the compatible devices: The TUNAI media button and the CooSpo cadence sensor. Pairing the devices was already rather painful since it didn't work with the Oculus app, but I was able to eventually do it from within the Quest headset via the "experimental" settings. The cadence sensor also took a long time to get working, after restarting the headset at some point it was able to connect. Ok. 

I can change the volume with the TUNAI button reliably, so its connection definitely works. But the performance inside VZPlay/Explore is awful! The "A" button takes forever to react! When I keep mashing it for several seconds, at some point it actually triggers and resets the view, but it's completely unplayable! And yes, I did try pairing the button with my phone and it works there, it's not a hardware issue with the button. So I don't know why you guys wrote on the list that it "worked great in testing", because it performs terribly!

I'm also not happy with the performance of the CooSpo sensor, which you listed as the official partner so I hoped that it would be the best I could get. There is a delay of several seconds between me starting to pedal and the game reacting to it, and the RPM inside the game are very loosely connected to my actual pedaling speed! Sometimes it speeds up or slows down for no apparent reason, making it impossible to do challenges like "keep above x km/h". It also breaks the immersion and I don't feel encouraged to do sprints since they are not registered. 

I don't know why I don't see anyone else having these problems, apparently everything works fine for other people? Is something wrong with the Bluetooth in my Quest? It seems to me like the issues with the button and the sensor are related, is Bluetooth just losing packets all the time? That could explain why the button is unreliable and why the cadence sensor just misses beats.

Did anyone else have issues like this? Did they get it to work? Because like this it's just not fun and I'll cancel my subscription...

https://www.virzoom.com/compatible-devices/
Reply


Messages In This Thread
TERRIBLE performance of TUNAI button + CooSpo sensor - by atrettin - 05-21-2020, 10:23 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)