Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
Dismiss Notice
Join us now in the Performance Profiling Dev Blitz Day 2023 - Q&A forum where you can connect with our teams behind the Memory and CPU Profilers and the Frame Debugger.

Bug Repeating "[XR] SetOutput Failed" error on OpenXR build when running via Oculus/Meta runtime

Discussion in 'VR' started by robbiecargill, Jan 10, 2023.

  1. robbiecargill

    robbiecargill

    Joined:
    Jul 5, 2017
    Posts:
    1
    We're building a VR game in Unity 2021.3.16f1, targeting OpenXR plugin

    When we run the OpenXR build via Oculus/Meta Quest (running on Windows, playing on Meta Quest 2 via link cable) our player log is filled with "[XR] SetOutput Failed" errors.

    When we run the same build via SteamVR (still playing on Quest 2 via link cable, just with SteamVR as OpenXR runtime) we don't get those errors.

    I've not been able to find anything else regarding this error online, and the player log doesn't seem to have any other useful output around it that I can see. The game still seems to be fully playable, and not noticed any directly related OpenXR issues, however we are getting occasional unexplained crashes and wondering if this is the cause.

    Attached log of the relevant output.

    Has anyone else seen this or might be able to assist in any way?
     

    Attached Files:

    • log.txt
      File size:
      34.8 KB
      Views:
      17
  2. Tanya_Li

    Tanya_Li

    Unity Technologies

    Joined:
    Jun 29, 2020
    Posts:
    98
    Looked at the code, seems like that error msg means "Failed to set the audio output endpoint", which could be no audio output devices available or you disabled the audio output. Could you please check that on your desktop?

    The error output is too vague and spamming, we will fix it.
     
  3. Estemyr

    Estemyr

    Joined:
    Oct 9, 2018
    Posts:
    7
    We have the same error, haven't updated from 2021.3.4f1 but I can confirm that we have disabled Unity audio since we're using FMOD instead. So I'd assume it's safe to disregard for the time being?

    Just a little more annoying to find actual bugs in the log file haha!
     
  4. Tanya_Li

    Tanya_Li

    Unity Technologies

    Joined:
    Jun 29, 2020
    Posts:
    98
    Yes. if you disabled audio source, then it is safe to disregard.
    I will create a ticket internal to get that error spamming fixed.