# Collaborative surgery planning in virtual reality

**URL:** <https://discourse.slicer.org/t/collaborative-surgery-planning-in-virtual-reality/6407>\
**Category:** Support\
**Tags:** virtual-reality, creepy-cool\
**Created:** [April 5, 2019, 2:53pm UTC](https://discourse.slicer.org/t/collaborative-surgery-planning-in-virtual-reality/6407 "2019-04-05T14:53:50Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [May 7, 2019, 11:14pm UTC](https://discourse.slicer.org/t/collaborative-surgery-planning-in-virtual-reality/6407/9 "2019-05-07T23:14:28Z")

</div>

> [@cpinter](#):
>
> There is no tutorial, because the process is not polished at all (it was quite lengthy to set up),

I think the setup is quite painless, especially if you just modify an existing scene that has the controller transforms sharing already configured. The setup could be also automated with a short Python script.

The main idea is that you run two instances of Slicer, each of them connected to a headset. Both instances contain the same data nodes (models, volumes, etc.) and their parent transforms are set as outgoing nodes in OpenIGTLinkIF module (which ensures the transform nodes are synchronized between the instances). The scene that we used in the video is available [here](https://1drv.ms/u/s!Arm_AFxB9yqHt6I_2zmVp7FhX9b0Cw).

---

_[View the full topic](https://discourse.slicer.org/t/collaborative-surgery-planning-in-virtual-reality/6407)._