Question [OpenXR 1.3.1] ActionSets already attached - Console LogError

Hello, after upgrading from OpenXR 1.2.8 to 1.3.1, I'm getting this error below (in addition to the "Failed to suggest bindings errors" already reported):


"ActionSets already attached
UnityEngine.GUIUtilityProcessEvent (int,intptr,bool&)"


This occurs any time I take off my headset, and put it back on (Rift S, using Oculus runtime). No errors are thrown using my Vive with the SteamVR runtime. So far I haven't noticed any issues occurring, besides the error getting reported in console.

 

I'm having the same issue. It applies on 1.3.0 too, Are you using the BNG framework (asset from the
Bearded Ninja Games in asset store)?
In addition I experience that after opening unity only the first time I hit play the controllers input works, all other times I gets only the controller position correctly until Unity reboot. don't know if it is related.

 

I'm not using the BNG framework - have not noticed this issue either.

 

For future reference, I share a reproducible repository.
Fairly simple except using zenject (I was practicing that).
Environment: Unity 2022.1.0b4.2571, Windows 11 21H2 22000.434, Oculus Quest 2 with air link

 

Did you find a solution to this problem same thing is happening to me

 

Edited:

I've been getting this problem as well for the past month or so when using Oculus as my OpenXR runtime. I guess I originally was conflating this as just being a bazaar secondary error/effect of the

... so I didn't end up investigating this error (oops)... For this other bug there is a temp work around (which I haven't personally tasted yet) and a lengthy discussion about the what's causing this error message here: https://forum.unity.com/threads/unity-openxr-error-failed-to-suggest-bindings.1206319/#post-7838898

Has anyone tested if the above fix fixes this ActionSets bug as well? They both started on the same day for me a short time after switching to 2021.1.7f1.

 

Using 2020.3.26f1 with OpenXR 1.3.1 and seeing the same thing. Anyone found a solution yet?

 

Same here, using Oculus Quest 2 and Unity 2020.3-26f.
Any Solution?

 

Problem is still there in Unity 2021.2.12
Using Quest 2 in Air Link mode

 

Same here Unity 2020.3.32f any solution? This is very annoying.

 

Yup, same for me too. 2020.3.25, OpenXR 1.3.1

 

same too. Unity 2020.3.27f1, OpenXR 1.3.1

 

Same, Unity 2021.2.19f1, OpenXR 1.3.1

 

Same here, Unity 2020.3.31f1, OpenXR 1.3.1

 

Also getting the same issue, it only happens when the OpenXR runtime is set to Oculus for me

 

Same on 2021.3.1f1 and OpenXR 1.3.1

 

I also have the issue OpenXR 1.3.1 and Unity 2020.32f1

 

For me this issue seems to be resolved in the new LTS branch (2021.3.2f1), but it's still apparent in the new Tech branch (2022.1.0f1).

 

Yes. When I used the Unity 2021.3.9f1, the problem solved.