Search Unity

  1. Are you interested in providing feedback directly to Unity teams? Sign up to become a member of Unity Pulse, our new product feedback and research community.
    Dismiss Notice
  2. Read here for Unity's latest plans on OpenXR.
    Dismiss Notice

Disable log flood XRStats::SetStatFloat Failed. Stats queue full! Stats for this frame will be lost.

Discussion in 'AR/VR (XR) Discussion' started by AVOlight, Oct 7, 2019.

  1. AVOlight

    AVOlight

    Joined:
    Apr 15, 2014
    Posts:
    421
    Hi,
    Please, please, please help me disable these warning logs from XRStats.
    is there a way to disable XRStats completely?
     

    Attached Files:

  2. williamj

    williamj

    Unity Technologies

    Joined:
    May 26, 2015
    Posts:
    94
    Hello @AVOlight,

    There is no way to disable stats completely right now. I will bring this up with my team to see if it's something we can accommodate as I know it's been brought up in the past. I will get back to you shortly on this.

    Regardless, this behavior is strange and unexpected, Ii it possible to submit a repro project through our bug reporter?

    Thanks,
    Will
     
    AVOlight likes this.
  3. AVOlight

    AVOlight

    Joined:
    Apr 15, 2014
    Posts:
    421
    Hello and Thank you @williamj,
    this is my bad for some reason I thought having the Test Framework package was a dependency of the Entities package

    after removing Test Framework package I no longer get these logs

    Cheers,
    Nicklas
     
    ANS_TT_VR likes this.
  4. FortuneSyn

    FortuneSyn

    Joined:
    Oct 28, 2019
    Posts:
    5
    Hi @williamj, I'm getting this same issue at the moment, a flood of the following message:

    XRStats::SetStatFloat failed. Stats queue full! Stats for this frame will be lost.

    I am testing using an Oculus Quest with link. I tried removing Test Framework package similar to AVOlight but the issue persists.
     
    Sammyueru1 likes this.
  5. ANS_TT_VR

    ANS_TT_VR

    Joined:
    Nov 3, 2019
    Posts:
    6
    Hello there. Testing Unity 2019.3 with Rift S and I am getting this same warning, flooding my console. Has anyone found anything yet?

    *EDIT: AVOlight is right. After removing that package the warning goes away. It fixed the problem for me.
     
  6. Ninjastyler4

    Ninjastyler4

    Joined:
    Mar 21, 2020
    Posts:
    1
    i get the same thing, once i open the console, the fps drops to 1 and i get spammed with that message
     
  7. colinleet

    colinleet

    Joined:
    Nov 20, 2019
    Posts:
    97
    Same thing here as soon as I open up the console I get flooded with dozens of these warnings every frame.
     
  8. PeppeBoi

    PeppeBoi

    Joined:
    Sep 2, 2020
    Posts:
    2
    I have removed Test Framework package but still geting the same error message.

    Is there someone that has an solution to this in 2020?
     
    FyodorKrasniy likes this.
  9. FyodorKrasniy

    FyodorKrasniy

    Joined:
    Jul 9, 2019
    Posts:
    2
    Had the same issue with quest and link, removing the test framework helped -- using HDRP in 2020.1.5f
     
  10. Xiaoki

    Xiaoki

    Joined:
    Jan 3, 2017
    Posts:
    5
    I am also getting this error even after removing the test framework. Any news yet?
     
  11. magnetica

    magnetica

    Joined:
    Jan 3, 2008
    Posts:
    84
    same here.
    I noticed this error after an Oculus update.
     
  12. Parfy3c

    Parfy3c

    Joined:
    Feb 2, 2020
    Posts:
    2
    Any update this on this? I am having the same problem testing a Quest 2 with Oculus Link. I don't have to take off the headset to get the error: XRStats::SetStatFloat failed. Stats queue full! Stats for this frame will be lost. I am getting this error even after removing the test framework.Using Unity 202.1.9f1 > XR Interaction Toolkit 0.9.4 > XR Plugin Management 3.2.16 > with XR Rig, a Tracked Pose Driver, XR Controller, XR Grab Interactable, and XR Direct Interactor.
     
  13. kokutouchichi

    kokutouchichi

    Joined:
    Mar 29, 2020
    Posts:
    2
    2021 and this error seems to still persist. BUMP
     
  14. alevjen

    alevjen

    Joined:
    Sep 11, 2020
    Posts:
    3
    I am also getting this error, but it only happens if the Console window is tabbed behind the Game window when I press play and then switch to it. If I dock the console window elsewhere it seems to work fine with no errors!
     
    Last edited: Jan 22, 2021
    bromans likes this.
  15. bromans

    bromans

    Joined:
    Dec 24, 2018
    Posts:
    1
    I found a workaround thanks to @alevjen answer, I pinned the console in front of the project tab and now it works fine. Previously it was pinned behind the Game tab.
    upload_2021-2-16_11-34-10.png
     
  16. unity_16WE64TkKkYDdg

    unity_16WE64TkKkYDdg

    Joined:
    Nov 16, 2020
    Posts:
    1
    Confirmed, I didn't even check for Test Framework package, simply relocated the console to join scene window rather than game window. All errors ceased.
     
  17. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    69
    I was able to disable these warning when using Oculus Link by closing the OVRLint tool window.
     
unityunity