Skip to main content
Xcalllibur
Participant
April 3, 2013

XNA Integration

I am currently working on integrating the Oculus SDK into XNA, to add support for one of my existing projects. Anyone else interested in me posting my findings and code for them to use?

    10 replies

    stephanelx
    Participant
    April 3, 2013
    I am working on a wrapper to use the ovr lib in c# but with WPF.
    My objective is to integrate the orientation tracking in VR Player.
    I would be very interested to heard about your findings!
    DWDan
    Participant
    April 3, 2013
    We have several XNA projects currently in the pipeline, we would be very interested in XNA integration.
    ihaveanothereye
    New Participant
    April 3, 2013
    Yes please, much appreciated!
    stridergax
    New Participant
    April 16, 2013
    I'm also very interested in hearing about your findings.

    @stephanelx Also the WPF findings as well.
    EpiX
    New Participant
    April 17, 2013
    great!
    ppetermann
    Participant
    May 1, 2013
    since XNA will no longer be supported by MS, why not make it work with MonoGame (Opensource XNA) instead?
    pmarques
    Participant
    June 24, 2013
    Any more news on this? I would love to be able to convert some XNA demos to Oculus now that I have my devkit.
    Vin
    Up and Coming
    June 24, 2013
    "ppetermann" wrote:
    since XNA will no longer be supported by MS, why not make it work with MonoGame (Opensource XNA) instead?


    Yeah, with XNA being shut down, should it be targeted for new development? I haven't heard anything about a successor to the platform yet.
    Anonymous
    October 8, 2013
    Any more news on this project, either with continuing XNA development, or going MonoGame?

    Thanks
    pmarques
    Participant
    February 21, 2014
    I have managed to get the Rift working on XNA (headtracking + stereo rendering + distortion correction + reset orientation), and I wrote a little tutorial here: https://developer.oculusvr.com/forums/viewtopic.php?f=39&t=6485
    Terms & ConditionsAccessibility statement