Wireless VR headsets are fast becoming the new standard in virtual reality hardware—and for good reason. Since VR environments are all about immersion, nothing zaps immersion like being in the middle of an exciting firefight, only to trip and fall on a cumbersome wire while trying to duck for cover.
One of the most promising products (the official HTC VIVE Wireless adapter) had everyone waiting excitedly for its release, but due to tech issues, this adapter won’t be released in Japan. That means that the TPCAST is the only wireless adapter legally allowed for use in Japan.
The good news is, TPCAST is an excellent piece of hardware, and by all means a great option.
While there are some minor issues around the TPCAST’s functionality (which is to be expected as a first-generation commercial product of this kind), the article below outlines several methods to improve usability, and resolve some of the frustration around using TPCAST.
One major issue many TPCAST users encounter is its unstable connection—leading to instances of failure, which is definitely a big con when trying to enjoy your VR experience.
Now, once the TPCAST connects successfully, users will enjoy a reliable connection until the device restarts. However, encountering issues when trying to establish an initial connection is frustrating at best, and prevents you from enjoying your VIVE at the worst.
Fortunately, there is an unofficial firmware, known as OpenTPCast, currently in development. When testing it out, a stable connection was created (for now.)—and the reason may lie in the fact that the original frequency isn’t high enough.
Much like a mini raspi-PC (with a battery that mounts from a microSD), the TPCAST’s USB device can only transmit video using a wireless LAN connection.
OpenTPCast offers an easy installation process since it is disassembled and exchanged with an OpenTPCast-branded microSD.
Please Note: There is a possibility that microphones that are normally disabled via traditional TPCAST may function with OpenTPCast.
A software option to work in unison with OpenTPCast is FlexiHub, a tool that recognizes USB devices. This is a fantastic alternative to the OpenTPCast software, as it’s reliable and very easy to set up.
It does cost $14/month, but FlexiHub can turn devices into device servers (allowing for USB devices to connect wirelessly), meaning it has a plethora of use cases that make it a worthwhile investment.
With a cable that connects from the top of the headset, the TPCAST’s miniature PC and battery are designed to attach separately to belts or pockets.
This is an excellent design choice, as it ensures the headset is lighter and more comfortable to wear, which contributes to longer playing times and better experiences for users.
But, pending on the user's preferences, the battery and mini PC can be integrated with the headset.
Conveniently, 3D printer owners can access the mount data on Thingiverse, and have a few different options to choose from.
And for those who don’t have 3D printers, don't worry. You can just as easily fasten the battery using zip ties, rubber bands, etc.
As seen in the example below, this battery pack was attached with non-slip rubber bands.
There are no power switches on a TPCAST. Once the batter and mini PC connect, the hardware turns on automatically, and the only way to turn it off is by disconnecting the battery and mini PC.
As one would assume, if the battery and mini PC are left plugged in, the headset will continue to run until the battery life is used up.
That means it’s very important to always disconnect it each time to maximize the lifespan of the battery. Additionally, power cannot transfer to the battery because the charging port is blocked when the headset, battery, and mini PC are connected.
This inconveniences many users, but there is a simple solution.
As an example, one can attach a bifurcated USB cable and USB-style power switch between the TPCAST and its battery—allowing users to power off the headset without having to disassemble the battery.
Regarding the TPCAST’s battery life, the PowerCore 20100 (by Anker) is utilized without any addons or enhancements. With a clean and organized design, the PowerCore 20100 is housed within the TPCAST box.
One drawback is that the power core isn’t compatible with quick charging capabilities, so a full charge can take up to 12 hours. An easy fix is simply replacing the PowerCore 20100 with the PowerCore II 10000. This reduces output to a single port, and also functions normally via bifurcated connections.
Operating time using a standard 20100mAh is 5 hours. However, this varies heavily on individual usage. Being that some may not even use VR for 5 hours, any inconveniences could be minor.
Alternatively, if the user spends a majority of their playtime in less physically demanding VR experiences (like in VRChat or for use in distribution), they may find it problematic.
Being that it only functions as a power supply, it’s totally compatible with mobile batteries developed by other brands.
Users can also try out a similar configuration involving two smaller batteries arranged on the left and the right.
Please note: For those just looking for a spare battery, it isn’t necessary to purchase the same model as the attached battery because of the PowerCore II 20000.
Being that it is very frustrating to connect and disconnect the micro USB for battery charging, using a magnetic charging option could eliminate some of the irritation. All the user needs to do is attach a basic magnet connector into the battery charging port.
Just bring the cable close to the battery, and charge via connecting the magnets together!
When introducing TPCAST, formal instructions dictate that users should place the TPCAST router between the PC and the current router.
In reality, this setup makes a big impact on the network’s wireless configuration, and is way too complicated for no reason. With that in mind, many users think there really aren't any pros to doing it that way.
The TPCAST instruction manual neglects any further explanation in this regard, but it’s believed that this setup is intended for USB device-oriented transmissions via the network.
Please Note: If a PC has two NICs, users can just connect the TPCAST router into whichever one they’d like.
Even if users have a connection destination between the TPCAST and a pre-existing router, it functions as it should (OpenTPCast gives users the ability to configure their preferred connection destinations.)
Many believe this has to do with compatibility problems, over-simplified instructions, and router performance. However, if everything operates successfully using a pre-existing router, then there’s no need for the additional TPCAST router.
Additionally, TPCAST routers appear to have a specification defining that reset buttons are attached to an easily accessible location, but it won’t connect upon reset, and a postscript caution paper reading "Do not press" is included.
Please note: The mini PC’s SSID/PASS is fixed, and looks as though it matches the settings on the router side (so there’s a possibility that that side perhaps won’t match.)
Some report that when the TPCAST is off, it’s treated like a monitor that lacks HDCP connection support. This means users encounter issues when trying to use apps that need HDCP.
Some have attempted to remove the HDMI cable or shut off the link box, but this leads to unstable/unpredictable performance results when using a remote control or switch.
While there are many adaptations that improve the experience, the default TPCAST product offers vastly improved usability.
All of the VIVE’s standard hardware (body, video reception unit, audio strap, battery, mini PC, switch, and the cable for 11 connectors between the devices) are all attached, so it can be a bit cumbersome to move around in. However, all cables are connected on top of the head, which means the usability is still pretty impressive.
While there are definitely cons to the TPCAST, the wireless connection is very comfortable. If users can adapt to the various unpolished details and design elements, it’s a worthwhile product to consider.