Hello everyone.

We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.

On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.

So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.

[360VideoPlayback sample error] Cannot render to Right-Eye when connect headset

edited June 2018 in Q&A and Discussions

I have tried to using 360VideoPlayback sample on GitHub to render 360 video with DirectX.

It's run well on simulator and Samsung HMD Odyssey headset.
But I found a issue like below:

  • Connect Samsung HMD Odyssey headset to PC
  • Run sample app
  • Focus to out of Mixed Reality Portal windows (click to another PC app)
    => Cannot render 360 video to the headset right eye. You can see on attach image.

Seem that this issue come from API. Please help me ask 360VideoPlayback team for us.

Thank you!


  • Hi Ryu,

    I can reproduce this issue in my side and I've reported this issue. Thanks for your feedback!

  • RyuRyu
    edited July 2018

    Hi Jay,

    Sorry for many questions an issues ^^!
    I have added a ticket to MS support center also.
    Mr Ray Wang is supporting this issue for me.
    He said that Acer headset can produce this problem.

    I hope dev team can fix it.

    Thank you!

Sign In or Register to comment.