Compatibility matrix

[jbltx]

Do you provide any compatibility matrix to know which version of SteamVR plugin works with which version of Unity?

I am currently trying to install the last version (2.6) in Unity 2017.4 but it doesn't work due to the missing XR framework module from newer versions of Unity... Even tho on the Asset Store the description says it is compatible starting Unity 5.4.6...

I think the compatibility matrix is mandatory at this point since both Unity and SteamVR change drastically at each iteration.

[rib]

I can at least contribute these to the matrix:

Unity Version	Steam VR Unity	xr.openvr.standalone	unity.openvr	Status
2019.4.8f1	2.6.0b4	2.0.5	1.0.1	No working OpenVR input - unable to activate/use any action set
2019.4.8f1	2.6.1	2.0.5	1.0.1	No working OpenVR input - unable to activate/use any action set
2020.1.3f1	2.6.1	N/A	1.0.1	No working OpenVR input - default action set actives but actions not working

I'm pretty tied to Unity 2019.4 currently, since the application I'm developing has been released and I'd rather stick with a LTS version of Unity. I really hope it will be possible to get support for OpenVR input with Unity XR for rendering some time soon - otherwise it's going to be a real pain to add SteamVR support to my app.

[rib]

Ah, so this already helped me realize that I should have removed xr.openvr.standalone which makes sense when I think about it. Removing xr.openvr.standalone at least seems to make 2019.4 consistent with 2020.1 for me now and I can start seeing the default action set get activated, even though I can't see any actions apart from poses working. Updated table:

Unity Version	Steam VR Unity	xr.openvr.standalone	unity.openvr	Status
2019.4.8f1	2.6.1	!removed!	1.0.1	No working OpenVR input - can activate action set but only pose actions seem to be working
2020.1.3f1	2.6.1	N/A	1.0.1	No working OpenVR input - can activate action set but only pose actions seem to be working

(removed line for 2.6.0b4 since I didn't go back and re-test that)

[rib]

Okey, so with further testing I also found that the SteamVR Input Live View is misleading (broken?)

If I open and run the Simple Sample scene and open the Live View then all I see is pose data, I don't see the state for InteractUI (for example) in the default action set change.

If I add a very simple behaviour to an object in the scene that does actually read the InteractUI state e.g. with:

    void Update()
    {
        if (SteamVR_Actions._default.InteractUI.state)
        {
            Debug.Log("InteractUI");
        }
    }

then I do start to see the Live View showing state updates for the InteractUI action. So the Live View is apparently not a direct view of the input itself, but rather a view of the application reading the input data? That's not really what I expected - and I'm not sure if that's intended?

Based on this I can update the table again, since it looks like these actually work, and maybe there's a separate bug with the Live View:	Unity Version	Steam VR Unity	xr.openvr.standalone	unity.openvr	Status
2019.4.8f1	2.6.1	!removed!	1.0.1	Basic OpenVR Input tested OK
2020.1.3f1	2.6.1	N/A	1.0.1	Basic OpenVR input tested OK

[IronStomachVR]

I have the same issue on 2017. It is keeping me from porting my game to SteamVR. If it isn't to much trouble, where do I go to remove xr.openvr.standalone?

[rib]

I'm not familiar with what's supported with Unity 2017 (and I wouldn't be surprised if some of this latest stuff isn't supported on Unity 2017) but assuming that version supports newer XR plugins then you should be able to use the package manager (Window -> Package Manager menu) to remove the 'OpenVR Desktop' package which is their legacy driver that seems to conflict with this newer XR plugin. Hope that helps @IronStomachVR - good luck!

[zite]

@IronStomachVR The Unity XR Plugin is not supported on Unity 2017. You'll need to stick with the desktop plugin.

[IronStomachVR]

Oh i figured it out. The desktop plugin auto adds the xr plugin associations but by clicking each compile error it will take me to the offending files. Then in the inspector I click on the nulls and select the minus option to remove them. Do this to each file and then it will compile correctly.

[kaplat]

I also work in Unity 2017.4. When importing the newest SteamVR plugin from the asset store into an empty project i get the following error message: Assembly has reference to non-existent assembly 'Unit.XR.OpenVR' (Assets/SteamVR/SteamVR.asmdef)

@IronStomachVR : Is this the same error you got? So you deleted the entries from the respective asmdef files correct? I did that as well. I have no problems in the inspector yet, but might get there later...

@zite : Will there be a fix for this because it makes the SteamVR plugin unuseable in Unity 2017 out of the box.

[IronStomachVR]

That's what I did

On Tuesday, September 22, 2020, kaplat notifications@github.com wrote:

I also work in Unity 2017.4. When importing the newest SteamVR plugin from the asset store i get the following error message: Assembly has reference to non-existent assembly 'Unit.XR.OpenVR' (Assets/SteamVR/SteamVR.asmdef)

@IronStomachVR https://github.com/IronStomachVR : Is this the same error you got? So you deleted the entries from the respective asmdef files correct? I did that as well. I have no problems in the inspector yet, but might get their later...

@zite https://github.com/zite : Will there be a fix for this because it makes the SteamVR plugin unuseable in Unity 2017 out of the box.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/steamvr_unity_plugin/issues/818#issuecomment-696636609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOCB4XEQEBF5RJCPPGMNUELSHB32BANCNFSM4QGDEWPA .