search

KyryloKuzyk / AR-Foundation-Remote-support

Support page for the 'AR Foundation Remote' plugin on the Asset Store
https://assetstore.unity.com/packages/tools/utilities/ar-foundation-remote-2-0-201106
9 stars 0 forks source link

ARCameraBackground calls CommandBuffer.IssuePluginEvent crashes Unity 2022.3.0 #70

Closed Bersaelor closed 1 year ago

Bersaelor commented 1 year ago

Describe the bug ARCameraBackground calls CommandBuffer.IssuePluginEvent crashes Unity 2022.3.0

When I start the app in the editor it crashes after the console message:

AR Foundation Remote. ARCameraBackground calls CommandBuffer.IssuePluginEvent which crashes/freezes some versions of Unity.
Possible solutions:
- If you're confident that your version of Unity is not vulnerable to this issue, please add your Unity version to the 'Unity Versions With Issue Plugin Event Fix' in the plugin's debug settings.
More info: https://forum.unity.com/threads/arfoundation-arcamerabackground-commandbuffer-freezes-editor.1019461
- OR embed the AR Foundation package via AR Foundation Remote Installer. After embedding the plugin will automatically apply the required fixes.

Plugin Version: 2.0.30-release.0

Unity: 2022.3.0

Problem is, the logs say:

AR Foundation Remote. ARCameraBackground calls CommandBuffer.IssuePluginEvent which crashes/freezes some versions of Unity. Possible solutions:

But when I open the AR Foundation Remote Installer, there is no more button to embed any plugins. I remember there being a button about embedding in earlier versions last year, but now it just looks like this:

Screenshot 2023-06-06 at 13 11 07
KyryloKuzyk commented 1 year ago

Thanks for the report!

Some older versions of Unity were crashing at the call to CommandBuffer.IssuePluginEvent(), but newer Unity versions don't have this vulnerability anymore. In fact, I haven't seen this crash in new Unity releases in the last two years or so.

I just uploaded a new plugin version 1.4.30-release.1/2.0.30-release.1 that doesn't have this legacy check. Please update and tell me if this helps.

Or to silence the error on your current plugin version, please add '2022.3.0' here:

image