Known Issues

2019, 2020, 2021, 2022, 2023

When starting a project on Mac OS, you may have bundle importation problems. This issue was caused when downloading the Prysm package from the web, in Mac version 11 (Big Sur) and above because the Unity3D import process adds or modifies .meta files in the already signed UPM package.

If you have that issue with Prysm, you can solve it when ignoring the bundles manually from Mac quarantine. Execute the line below in the terminal:

xattr -dr com.apple.quarantine <bundles_directory>

2021.3.9

When a scene is played on Mac OSX, an assert will be encountered with a native backend using Metal rendering API. In the first couple of frames, Unity3D’s native API gives us a command buffer with an active encoder. Later when we try to create our command encoder in the backend and an assert in Metal is hit due to the presence of an already active one. There is a workaround for the issue by adding this code in CohtmlView.cs Draw method.

int framesCount = 0;
void Draw()
{
    if (m_HasDrawn || View==null || !enabled)
    {
      return;
    }
    
    framesCount++
    if (framesCount < 2)
    {
      return;
    }

// rest of the code
}

2021.3.34

When using composited textures, you may get a Unity warning stating “Registering a native texture with height=256 while the actual texture has height=0”. Unity3D has fixed this warning in later versions of the editor.

2021, 2022

On Mac OS M1 Silicon edition when Texture.GetNativeTexturePtr In CohtmlView.cs is called repeatedly e.g. in the Update method, the main thread freezes after a couple of frames.

2020, 2021, 2022

The UI Surface Partitioning feature does not work with the native Vulkan rendering backend due to a long standing bug in Texture2D.CreateExternalTexture when use on Vulkan.

← Rendering Architecture
Library Configuration →