VRTK vs INTERACTION BUILDER: Which one is for you?
VRTK is one, if not the most known open-source toolkit for VR solutions creation. It is currently in the beta process of its 4th major version.
Following, you will find a breakdown of its characteristics, and full a comparison between the interaction builder and the VRTK.
VRTK’s list of scripts & modules
Interaction Builder architecture
VRTK is a comprehensive and complete development framework for XR applications. It includes a lot of features and script to address the development needs. The drawback is the steep learning curve, and the legacy development mechanism to fully understand the whole architecture. A lot of these scripts are utility scripts for specific needs, it means that you do not necessarily need to know everything to be able to build your VR solution.
One part of the characteristics of VRTK is its management of the project/scene for specific platforms (Oculus, Vive, etc.). It is required to set up tracking, bindings, and several SDKs if you want to work on multiple platforms. Like every open source project, several of its scripts are interdependent and they require some time to fully understand how to combine them.
On the other side, as we specified in our MRTK comparison, the Interaction Builder has far smaller architecture. It removes the extra utility tools to focus on an easy to use interaction development system, which is completely focalized on a painless and streamlined development process. You can port your application in 2 clicks between several different XR platforms.
Thanks to the release of the Oculus Quest, one of the most popular UI in XR today is the hand tracking input. VRTK, as other existing VR interaction toolkits, is built around logic input from controllers. The system is technically compatible with hand tracking, but it is not natively supported. Developers will have to build or find an extra module to make the bridge between the analogic hand tracking, and the logic controller input.
The Interaction Builder is built specifically for hands interaction, which makes the integration of hand tracking far easier. It now supports Oculus Quest, HTC Vive and UltraLeap (former Leap Motion) systems of skeletal hand tracking for interactions based on realistic, and customizable, hand poses. This allows Interhaptics to cross-compile between platforms, the same application is compatible with hand tracking and controllers without any issue.
VRTK is it is pretty similar to the VR Interaction Framework comparison. VRTK proposes a simple grab system that can be coupled with the physic engine of Unity to define the desired behavior of the interaction you are creating. VRTK also proposes premade assets to skip the setup of specific interactions (like doors, drawers, etc.). To fully manage your creative and development process, it is necessary to learn how to use joints and to deal with physics to create the specific interaction you want. The implementation of physics in the process makes it necessary to pay attention to the system physics to avoid any stability issue.
The Interaction Builder is based on a logic engine. It avoids the learning curve of the physics implementation without giving up the extreme customization of your creations. It includes the precise mathematical definition of how several interactions will behave in the 3D environment. This allows Interhaptics to include a more advanced event system due to logic-based interactions. To go more in-depth, VRTK includes start interaction and end interaction events. However, the Interaction Builder covers everything that happens between the start and the end: constraints reached, target reached, the specific value on a slider, etc. See here for more information!
VRTK suffered from a loss of popularity and slow development progress. As for today, it is a bit behind comparable competitors (mainly VR Interaction Framework or MRTK) in terms of features and UX. However, the currently under development 4th version will add new functionalities, and good things might appear in the future to restore VRTK’s notoriety. If you are not planning to develop for hand tracking, it is still an efficient toolkit to use with large platform incompatibilities.
If you are looking for an easier and simpler development solution that is specifically built to meet new technologies such as hand tracking, choose Interhaptics. Develop your experience & deploy it everywhere in a few clicks!