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

https://dl.acm.org/doi/pdf/10.1145/3544548.3581136

• 

https://www.youtube.com/watch?v=QZyglCjf5pQ

• This is really cool (blu3mo)

  • It’s nice to have other people in the miniature branch in collaboration.

• Introduction

  • Prior research:
    • It would be convenient to be able to manipulate 3D environments in VR with a WYSIWYG interface.
    • It would also be convenient to collaborate in VR.
      • CollaboVR: A Reconfigurable Framework for Creative Collaboration in Virtual Reality
    • It would be useful to have a version history.
  • Proposal:
    • It would be very convenient to be able to travel between versions and collaborate with each other.
    • There doesn’t seem to be any research that combines VCS and collaboration.

  • The contributions of our paper are:

    • (i) the design and implementation of a new VCS for collaborative content creation in VR,
    • (ii) results and design insights gained from an exploratory lab study that evaluated the usability and utility of the VCS for content creation in VR.
  • Collaboration seems to be the main focus.

• Prior works

  • 3D VCS
    • Git-related
      • 
      • Dobos 3D Dif: an interactive approach to mesh diferencing and confict resolution
      • Meshgit: Difng and merging meshes for polygonal modeling
      • SceneGit: a practical system for diffing and merging 3D environments
      • MeshHisto: collaborative modeling by sharing and retargeting editing histories
      • cSculpt: a system for collaborative sculpting
      • Spacetime: Enabling Fluid Individual and Collaborative Editing in Virtual Reality
  • History visualization

    • For example, MeshFlow 17 and 3DFlow 19 are proposed to summarize the history of mesh editing by clustering editing operations.

      • I want to refer to this (blu3mo)
      • Meshflow: Interactive Visualization of Mesh Construction Sequences
      • 3dflow: Continuous summarization of mesh editing workflows
      • But both seem to focus on meshes, so it might not be ideal.
  • Time-Machine Computing: A Time-centric Approach for the Information Environment

• Techniques

  • Summarization

    • Our summarization techniques take into account three parameters: (i) operation dependencies, (ii) spatial constraints, and (iii) workspace awareness. We use a simple timeout mechanism to determine operation dependencies, which generates a new node in the history graph after the user has been idle for a specified amount of time (10 seconds when working alone, 15 seconds when working collaboratively—defaults that we found to work anecdotally).

• Evaluation

  • Subjective

• Interesting paper

  • Meshgit: Difng and merging meshes for polygonal modeling