https://www.slicer.org/w/index.php?action=history&feed=atom&title=Documentation%2F4.8%2FDevelopers%2FFAQ%2FDevice_InteroperabilityDocumentation/4.8/Developers/FAQ/Device Interoperability - Revision history2026-04-06T04:22:41ZRevision history for this page on the wikiMediaWiki 1.33.0https://www.slicer.org/w/index.php?title=Documentation/4.8/Developers/FAQ/Device_Interoperability&diff=55181&oldid=prevUpdateBot: Nightly -> 4.82017-10-18T07:01:12Z<p>Nightly -> 4.8</p>
<p><b>New page</b></p><div><noinclude>{{documentation/versioncheck}}</noinclude><br />
<noinclude>__TOC__<br />
={{#titleparts: {{PAGENAME}} | | -1 }}=</noinclude><includeonly><br />
='''Developer FAQ: {{{1}}}'''=<br />
</includeonly><br />
<br />
== Can Oculus Rift be used with Slicer ? ==<br />
<br />
Some preliminary integration work has been done. See http://slicer-devel.65872.n3.nabble.com/Oculus-Rift-td4032779.html<br />
<br />
== Can Oculus Rift be connected with Slicer through OpenIGTLink ? ==<br />
<br />
Oculus requires very tight integration with the rendering pipeline, so probably the current approach of using a C++ loadable module that directly communicates with the Oculus SDK to get pose and send images is better than going through OpenIGTLink.<br />
<br />
Source: http://slicer-devel.65872.n3.nabble.com/OpenIGT-and-Slicer-tp4032868p4032875.html</div>UpdateBot