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

Hi,
Please, please, please help me disable these warning logs from XRStats.
is there a way to disable XRStats completely?

 

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

 

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.

 

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.

 

i get the same thing, once i open the console, the fps drops to 1 and i get spammed with that message

 

Same thing here as soon as I open up the console I get flooded with dozens of these warnings every frame.

 

I have removed Test Framework package but still geting the same error message.

Is there someone that has an solution to this in 2020?

 

Had the same issue with quest and link, removing the test framework helped -- using HDRP in 2020.1.5f

 

I am also getting this error even after removing the test framework. Any news yet?

 

same here.
I noticed this error after an Oculus update.

 

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.

 

2021 and this error seems to still persist. BUMP

 

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!

 

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.

 

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.

 

I was able to disable these warning when using Oculus Link by closing the OVRLint tool window.

 

This worked for me, but wondering if anyone else found a good solution

 

Bumping...

Hiding console is not a viable workaround. Not excited about removing Test Framework...

Any timeframe on fixing this?

 

I had to delete the UserSetings folder...

 

Hello from the future! Still this issue exists in 2023. Removing the test framework and restarting unity worked for me.
LTS 2021.3.16f

 

It works, ty

 

I believe the bug causing the game not to update frames is due to the GameView window being invisible.

Moving the GameView window to a visible position resolves the issue.

 

I'm doing performance testing in 2023.2.3f1, and suddenly started getting this log spam in my PRODUCTION build after disabling Multithreaded Rendering in the player settings. Maybe that will help someone.

I find it unbelievable that this log message is not behind some form of #IF... Classic.