Difference between revisions of "Documentation/Nightly/Developers/FAQ/Device Interoperability"
From Slicer Wiki
m (Created page with '<noinclude>{{documentation/versioncheck}}</noinclude> <noinclude>__TOC__ ={{#titleparts: {{PAGENAME}} | | -1 }}=</noinclude><includeonly> ='''Developer FAQ: {{{1}}}'''= </include…') |
m (moved Documentation/Nightly/Developers/FAQ/DeviceInteroperability to Documentation/Nightly/Developers/FAQ/Device Interoperability) |
(No difference)
| |
Latest revision as of 21:29, 18 November 2014
Home < Documentation < Nightly < Developers < FAQ < Device Interoperability
|
For the latest Slicer documentation, visit the read-the-docs. |
Contents
Device Interoperability
Can Oculus Rift be used with Slicer ?
Some preliminary integration work has been done. See http://slicer-devel.65872.n3.nabble.com/Oculus-Rift-td4032779.html
Can Oculus Rift be connected with Slicer through OpenIGTLink ?
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.
Source: http://slicer-devel.65872.n3.nabble.com/OpenIGT-and-Slicer-tp4032868p4032875.html
