What’s becoming clear in VR development is that with the market split across Rift, Vive and PlayStation VR, the developers of some of the most successful apps like Job Simulator, Fantastic Contraption and Raw Data work hard to make their software work well across all three headsets.
Even if it is hard to stand out from dozens of apps launching each week, making a virtual world available across Steam, the PlayStation Store and Oculus increases the chances of a developer finding success. Though large teams working with big budgets often turn to the Unreal world engine from Epic Games for building VR products, the very well-funded Unity Technologies is the engine most indie developers use in bringing their products to fruition across multiple systems. Unity is used by a majority of VR developers and its asset store makes it easy for developers to find cheap or free tools with which to build more immersive worlds.
VRTK — the Virtual Reality Toolkit — is one of those Unity-based tools that a large group of indie creators used to jumpstart their efforts in VR development. The open source toolset was created by Harvey Ball, also known as TheStoneFox, after he bought an HTC Vive last year.
“I wanted to build something for it as I was new to game dev. I’d been using Unity for about a month just as a hobby,” Ball wrote to me. “I tried to use the SteamVR Unity plugin and found it confusing, realized a lot of people found it confusing and started VRTK as a way to help people get into developing for VR.”
Ball’s crowdfunding on Patreon for VRTK stands at nearly $2,000 per month and the community for the effort on Slack is populated by more than 2,000 members. Here’s a list of games made with the software. Ball works on VRTK in the evenings when he can but still holds a day job as a Web developer. He says the money from Patreon isn’t his income — it’s so that “if we as a community need something that requires money then we have budget for it.” He also launched a Kickstarter project earlier this year with a very high goal for a more ambitious roll out. Though it received more than 400 backers, the project fell short of its goal.
I asked Ball to break down why he is building VRTK as an open source solution and to break down the benefits of the tools:
I wanted to make it available to as many people as possible. My belief is the more people building for VR is only better for evolving the platform. VRTK is all about getting as many people as possible working together on solutions to common problems for the common good. Also making it accessible for people new to dev but with good ideas so to remove high barriers of entry. Charging for it would just limit that for people. Plus it enables developers to build for a crazy fragmented market, using VRTK means it just works on Steam, Oculus, PSVR, etc.
The initial benefit is the VRTK abstraction layer. So if you use VRTK components for the mechanics of the game then it just works on any supported SDK. So it just works on SteamVR or Oculus or PSVR without any coding. If you build something for SteamVR you have to either write your own abstraction layer or rewrite chunks of code for other SDKs. Some popular SteamVR games already are suffering from this where they can’t be easily ported to Oculus Home. If they had been built on top of VRTK then porting is easy.
Ball said he plans to add support for Microsoft’s Windows platform as soon as he gets his hands on the controllers.
We’ve heard developers swear by VRTK in the past, but I put a call out on Twitter to find out how the toolkit has helped developers and the response was pretty strong. I’ll embed some of those tweets at the bottom of this post, but Unity developer @Mcdoogleh offered a response that summed up a lot of what I heard. The dev is working on a project based on VRTK aiming to release next year, “and without question it would’ve taken me longer to develop without VRTK.”
“It’s useful to developers for quite a lot of reasons, one of them being that as far as VR development goes, prototyping is extremely tricky. So VRTK provides…features which are useful just to play around with,” Mcdoogleh said. “It’s also end to end… So you could just use VRTK as a foundation and build up from it or update as you go along to get the latest features. Anywhere from prototyping to a release product, again, highly useful. In addition, VRTK can provide a useful point of reference to other developers, so they may not necessarily want to use VRTK, but they can use components of it as a foundation for their own code. Lastly, it’s knowing that it’s going to be supported, Harvey has been very engaged in terms of talking with developers, and has fostered a community of developers who can help each other.”
This story originally appeared on Uploadvr.com. Copyright 2017