Forum Discussion
ecilasun
12 years agoHonored Guest
Non-SDK rendering and direct-to-rift
Hi,
I have just integrated OVR support to my test engine. I do not use the SDK-rendering, and I can see the distorted rendering on my output window. When the application starts, the tracking works (I do not use the result yet but I see the camera turns on and moving the headset does the motion compensation in distortion rendering)
However, my HMD does not show any output on its display (this is in Direct-to-Rift mode). I assume outputting the distorted image to the device render target and calling Present() should simply make it work?
It must be due to something obvious but I am unable to pinpoint the issue. Does anyone have any hints that might help?
Thanks.
PS: I've forgotten to mention this is with DK2.
I have just integrated OVR support to my test engine. I do not use the SDK-rendering, and I can see the distorted rendering on my output window. When the application starts, the tracking works (I do not use the result yet but I see the camera turns on and moving the headset does the motion compensation in distortion rendering)
However, my HMD does not show any output on its display (this is in Direct-to-Rift mode). I assume outputting the distorted image to the device render target and calling Present() should simply make it work?
It must be due to something obvious but I am unable to pinpoint the issue. Does anyone have any hints that might help?
Thanks.
PS: I've forgotten to mention this is with DK2.
3 Replies
- ecilasunHonored GuestFIXED:
Apparently I missed something tiny as I predicted. One should call ovr_Initialize() before the D3D11 device creation. Everything works fine now. - cyberealityGrand ChampionThanks for following up on this.
- ecilasunHonored GuestYou're welcome :)
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 2 years ago
- 3 years ago
- 7 months ago