Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Unity Alert: Integration 1.32 compile issue (01/07/19)

NinjaGaijinNinjaGaijin Posts: 140 Oculus Staff
edited January 22 in Unity Development
We have been receiving reports of an issue when attempting to compile with the current integration (v1.32) offered on the Unity Asset Store
Assets\Oculus\Avatar\Scripts\OvrAvatarSkinnedMeshRenderPBSV2Component.cs(4,23): error CS0234: The type or namespace name 'Policy' does not exist in the namespace 'System.Security' (are you missing an assembly reference?)
Our team is aware of the issue and working to rectify it. For the time being, this can be fixed by opening the Assets\Oculus\Avatar\Scripts\OvrAvatarSkinnedMeshRenderPBSV2Component.cs file and commenting out/removing the following line (line 4) highlighted in bold:
using UnityEngine;
using System.Collections;
using System;
using System.Security.Policy;
using Oculus.Avatar;


If you need immediate help or want additional support/context on an issue you are having with our platform or integrations:

1. Gather any and all logs, screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.)
2. Please submit a ticket here (include what you've gathered in step 1).
3. Tag me @NinjaGaijin once you have done so!

Comments

  • NinjaGaijinNinjaGaijin Posts: 140 Oculus Staff
    01/22/19: This issue has been fixed in our Oculus Integration v1.32.1 update. Read the patch notes here.
    If you need immediate help or want additional support/context on an issue you are having with our platform or integrations:

    1. Gather any and all logs, screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.)
    2. Please submit a ticket here (include what you've gathered in step 1).
    3. Tag me @NinjaGaijin once you have done so!
This discussion has been closed.