VRGit: A Version Control System for Collaborative Content Creation in Virtual Reality

Document Title

VRGit: A Version Control System for Collaborative Content Creation in Virtual Reality

Document Information

• Subject Area: Version control system for collaborative content creation in virtual reality
• Keywords: Virtual reality, collaboration, version control system, virtual user interface, real-time collaboration, 3D modeling

Research Background and Problems

• What problems or challenges did the authors identify?

  • Current version control systems (e.g., Git and Subversion) are primarily designed for text-based content and cannot effectively manage 3D content such as spatial layouts and 3D scenes.
  • Most existing collaborative version control systems are designed for asynchronous collaboration and lack support for real-time collaboration needs in virtual reality (VR), such as real-time operation awareness and communication.
  • Existing VR tools only provide linear history tracking and lack effective visualization and operational support for nonlinear histories, such as branching and version merging.

• Why is this problem important?

  • VR offers an immersive operational experience for 3D scene construction, but its lack of collaboration and version control capabilities limits its broader application in fields such as game design, architecture, urban planning, and interior design.
  • Providing version control for creative design can help users record history, compare different design options, avoid conflicts, and revert to previous states.

• Research Motivation and Related Work

  • Inspired by existing literature on version control for 3D modeling, graphical history visualization, and collaborative virtual environments, the authors aim to explore a VR tool that integrates version control, real-time collaboration, and intuitive visualization functionalities.
  • The authors seek to advance research on the completeness and real-time interactivity of version control systems for 3D scenes.

Solution

• What methods or solutions did the authors propose?

  • The authors proposed a new collaborative version control system, VRGit, specifically designed for 3D content creation in VR.
  • VRGit employs an operation-based history model to record every user edit and use it for version management.
  • The system provides version history visualization functionality (History Graph, HG), supporting version navigation, branch creation, previewing, and content reuse.
  • It integrates real-time collaboration features, enabling users to understand other users' activities and communicate remotely through "mini avatars" and video portals.

• What are the innovative aspects of this solution?

  • VRGit innovatively visualizes version records as 3D mini models and branching graphs, using color coding in the models to represent object additions (green), modifications (yellow), and deletions (red).
  • It supports mixing and reusing objects across multiple versions, rather than merely simple version merging.
  • To address collaboration challenges, it offers two functionalities: portal views for real-time cross-version observation of other users' perspectives, and shared history visualization for collaborative operations on version history and design content during team discussions.

• What are the implementation steps and key technologies used?

  1. Constructing a basic immersive authoring environment that allows users to design virtual room layouts.
  2. Developing a DAG-based version management model to store the historical state of each operation.
  3. Designing the History Graph (HG) to help users understand version changes by displaying miniature 3D scenes and showing differences.
  4. Implementing real-time collaboration features, including mini avatars to represent other users' version positions, first-person portal views, and shared history visualization.
  5. Using Unity and Firebase for system development and real-time data synchronization.

Research Outcomes

• What specific outcomes were achieved?

  • VRGit enables users to manage nonlinear version histories simply and intuitively, including creating branches, reverting to previous versions, and reusing objects from historical versions.
  • Experimental results show that users found the system highly helpful for understanding historical changes and collaborating with others.
  • Users appreciated the miniature version visualization, color coding methods, and history navigation operations as highly intuitive and user-friendly.

• What advantages does it have compared to existing solutions?

  • Provides intuitive 3D version history visualization, rather than traditional text-based or timeline-based representations.
  • Offers both synchronous and asynchronous collaboration support, allowing users to work independently in different versions while maintaining awareness of other members' activities.
  • The shared history view integrates design history with collaborative discussions, effectively supporting creative design tasks.

• What were the experimental or evaluation results?

  • An experimental study involving 14 participants (7 groups) showed that users felt VRGit improved their creative efficiency and was highly beneficial for collaboration and historical retrospection.
  • User ratings (on a 7-point scale) indicated that the ease of use and practicality of history visualization scored 6.2 and 6.4, respectively; the practicality of branch creation scored 6.1; and the practicality of portals and shared history visualization scored 6.3 and 6.4.
  • Participants generally found the interface intuitive and engaging but noted a learning curve for history navigation and permission control.

• Limitations and Future Directions

  • Limitations:
    • The study was conducted with small user groups (only three-person collaborations), and its applicability to large-scale teams remains unverified.
    • System operations are primarily based on controller input, which increases users' memory burden for complex operations.
    • Currently, it only supports limited immersive creation operations and does not cover high-granularity 3D model operations (e.g., changes to meshes or vertices).
  • Future Directions:
    • Explore visualization techniques for larger-scale version histories, such as summary methods based on operation clustering.
    • Investigate VR interactions based on more natural inputs (e.g., gestures and voice) instead of controllers.
    • Design version control systems suitable for cross-device and cross-platform use, supporting more complex collaborative content creation tasks (e.g., integrating 3D modeling with VR/AR development workflows).