'ProcessorPerformanceLevel' does not exist in the type 'OVRManager' after migration to v2.8.0

[abhilashca]

Describe the bug

Migration from v2.7.3 to v2.8.0 using MR Feature Tool resulted in compile time error as - Library\PackageCache\com.microsoft.mixedreality.toolkit.foundation@9e95381a667f-1659615280629\Providers\Oculus\XRSDK\OculusXRSDKDeviceManagerProfile.cs(131,27): error CS0426: The type name 'ProcessorPerformanceLevel' does not exist in the type 'OVRManager'

To reproduce

Steps to reproduce the behavior:

1. Unity project with MRTK v2.7.3
2. Launch MR Feature Tool and try to migrate to v2.8.0
3. Get's compile time error - The type name 'ProcessorPerformanceLevel' does not exist in the type 'OVRManager'.

Expected behavior

Unity project should build fine after migration

Your setup (please complete the following information)

• Unity Version [e.g. 2019.4.14f1]
• MRTK Version [e.g. v2.7.3]

Target platform (please complete the following information)

• Oculus Quest

[MaxWang-MS]

Hi @abhilashca, can you let us know what version of the Oculus Integration package you are using?

[abhilashca]

@MaxWang-MS Here is what I am using

I tried re-importing the package again, but didn't helped.

[ProfDru]

Also experiencing this issue

[RogPodge]

Hey there,

I'm testing this in our project with Oculus Integration 42.0 and am not seeing this issue. MRTK2 was tested to work as of Oculus 39.0, where they introduced the new performance level variable

https://developer.oculus.com/reference/unity/v39/class_o_v_r_manager/#a6ec677bb216ae0ad4e62bff3fd8bdadf

Their documentation for v39 shows that it's still in their API, as does the documentation for v42 https://developer.oculus.com/reference/unity/v39/class_o_v_r_manager/#a6ec677bb216ae0ad4e62bff3fd8bdadf https://developer.oculus.com/reference/unity/v42/class_o_v_r_manager/

Could it be that the Oculus Integration Package needs to be updated to the latest?

[abhilashca]

@RogPodge My scenario was little different. I was upgrading the project from MRTK v2.5.3 to v2.8.0 steps by step. The upgrade went smooth till version v2.7.3 but got the error when I upgraded from v2.7.3 to v2.8.0.

Thanks for sharing the link for Oculus Integration v42. Let me try adding the same one more time and see what happens.

Will keep you posted in next couple of days.

Thank you.

[Zee2]

Closing as external API change; please reopen if the issue is not resolved.