Skip to main content
This diagram represents the workflow we use to create a VR Module. VRseBuilder provides various tools to implement this pipeline.
Collect an SOP (Standard Operating Procedure) or write out the narrative for your desired experience, including, what steps must occur, consequences of missing a step etc.
Feed the SOP into Studio. Studio will convert the SOP into a VR-ready storyboard. You can make changes to the story from within Studio’s web interface, or you can download the storyboard as an Excel spreadsheet, make changes in Excel, and upload again to update.
Along with a VR storyboard, Studio will also generate a recommended list of 3D and environment assets that will be required for your VR module. If you don’t already have the environment and 3D assets that your module requires, you can select from over 1000+ assets in VRseBuilder’s asset library.
Use VRseBuilder’s automation tool to import the storyboard generated from Studio into the Unity SDK. The automation tool will walk you through scene setup, adding environment and 3D assets, and editing the story.
Within the Unity SDK, you can add advanced triggers to your story which allow for more interactivity than a touch based interaction. Advanced triggers can include: grab, rotate, slide etc.
Connect your VR module to VRseBuilder’s Pulse Dashboard. This is done by attaching a dashboard-generated API key to module configurations in Unity. Once connected you can collect and analyze user statistics including training/evalution data for your module.
The last step is to create an APK from Unity which can be deployed on any OTA platform. VRseBuilder includes an automation tool that creates a build and deploys it on the Meta Developer Store (previously App Lab).

​
Source Control Recommendation

We recommend two options, both require self-setup.
  1. Git + Git Large File Storage (LFS):
    • Git is a popular distributed version control system that tracks changes to your files.
    • Large File Storage (LFS) is an extension that handles large assets (e.g., textures, audio, and models) by storing them in a separate location, keeping your core repository lightweight.
    • This approach ensures quick pulls/pushes for code, while preventing huge binary files from ballooning the main repository size.
  2. PlasticSCM (Built-in Integration with Unity):
    • Unity offers a native integration with PlasticSCM, which allows you to manage version control directly from the Unity Editor.
    • PlasticSCM is designed specifically for game development and large binary assets.
    • If you prefer a more visual/graphical approach and minimal setup effort, PlasticSCM might be the simplest option.
Tip: Check out Unity’s own documentation for how to set up and use these tools with your project: Version Control for Unity Projects