Bug Warning in Editor - You can only call cameraDepthTarget inside the scope of a ScriptableRen

Hi

My console is filling up with this warning since upgrading to 2020.2 and relevanr AR packages etc.

You can only call cameraDepthTarget inside the scope of a ScriptableRenderPass. Otherwise the pipeline camera target texture might have not been created or might have already been disposed.
UnityEngine.GUIUtility: ProcessEvent (int,intptr,bool&)

From the code (in ScriptableRenderer.cs - URP 10.2.2):

Code (CSharp):

1.  
2.         /// <summary>
3.         /// Returns the camera depth target for this renderer.
4.         /// It's only valid to call cameraDepthTarget in the scope of <c>ScriptableRenderPass</c>.
5.         /// <seealso cref="ScriptableRenderPass"/>.
6.         /// </summary>
7.         public RenderTargetIdentifier cameraDepthTarget
8.         {
9.             get
10.             {
11.                 if (!m_IsPipelineExecuting)
12.                 {
13.                     Debug.LogWarning("You can only call cameraDepthTarget inside the scope of a ScriptableRenderPass. Otherwise the pipeline camera target texture might have not been created or might have already been disposed.");
14.                     // TODO: Ideally we should return an error texture (BuiltinRenderTextureType.None?)
15.                     // but this might break some existing content, so we return the pipeline texture in the hope it gives a "soft" upgrade to users.
16.                 }
17.  
18.                 return m_CameraDepthTarget;
19.             }
20.         }
21.  

This is the same as https://forum.unity.com/threads/xcode-warning.1024825/ but on Windows (not mac). I'm going to comment out the warning to avoid filling the console but does anyone know if a fix is in the works?

 

+1 : Hitting this as well.

 

+1, same config and error. SRP project. AR camera stopped working.

 

I reported this as a bug and it's being tracked afaik.

 

Were you able to comment out the code in the package? My project seems to object when I try to do that and requires a rebuild/re-import that reverts my change.

It's hard to de-bug the project with the console full of this message.

 

+1

 

I'm seeing XCode throwing this warning on iOS build with unity 2020.2 and AR Foundation 4.0.9 or 4.1.1
All the AR objects, particles or augmented mask are not shown in AR mode (iphone 12)
Android is fine

 

I wouldn't recommend this, but upgrading to 2021.1.0b1 fixed it, no more warning messages. I made a copy of my project folder before attempting, as it's never been possible to downgrade a project in my experience.

I had some other problems with building in XCode and so it was worth fixing the various things that broke in my upgrade to the beta. I'm using ARFoundation 4.1.1 with URP 11.0.0. I got rid of any preview or experimental packages as well, so had to lose my UI Elements work and just use the standar uGUI.

 

looks like Unity 2020.2's URP 10 is not yet compatible with ARF 4.1.1

 

Another related report here:
https://forum.unity.com/threads/ar-foundation-broken-on-urp-10.1007057/

 

Currently getting this error on URP10.2.2, 2020.2.1f1, and ALSO it looks like the depth (or camera Z?) channel isn't clearing? Once an object pops in, it is slowly occluded by the AR background as they write closer Z values and disappear behind them.

It's one of the weirdest things I've seen. I even removed the occlusion manager. Could this be connected to the error? I could post a video.

 

Hi @mfuad , my issue is exactly the same as @Chopium explained right above
Clearly URP 10.2 is having compatible bug with any version of ARF
I downloaded ARF samples from github and try to run with URP10.2.2, 2020.2.1f1; the issue occurs on iOS

 

Thank you for your help. I have submitted a bug report (Case 1305714, not yet approved for public) In the meantime we are reverting to the standard renderer, which seems to have no issues. Luckily switching between pipelines is smooth at this stage of the project.

This was a small screen recording of what I'm seeing on device. My project is not super standard, but I believe URP + ARFoundation are the cause of the issue.

 

Hi, sorry, I've been out of the forums a bit. My bad. Anyway, you can find the script buried in the packages folder. Interestingly, since commenting out and refreshing the package (i.e. back in), the issue has disappeared. I'm at a loss, but I see some people have raised a bug for proper investigation.

 

Thanks! I recently found while tracking down another bug that it's possible to move libraries out of the package manager and put them directly into the Packages folder (same level as the Assets folder) in this post.

In my case (on a mac), the VFX package was located inside the Unity application Builtin folder. Here are the exact steps on a mac:

1. In the Unity Editor, open the Packages folder, right-click (vfx package for me) and Show in Finder.
2. Back in Unity, remove the vfx package using the package manager
3. Quit Unity.
4. Make a copy of the package folder and put it in the Packages folder in your project
5. Now edits will 'stick' since you are working off your own copy of the package

The "You can only call cameraDepth..." error is gone in 2021.b1+ so I didn't have to do any of this, but if you don't want to upgrade your project, the above steps should work.

 

I'm getting this bug too, but only in the actual build (showing up in Xcode console)

 

+1

 

I had this issue in the last 12hours. My solution was to downgrade to Unity 2019.4.18f1 and to URP 7.5.2 because I need to keep on work on AR features. It sucks but it works for now.

 

This was indeed the same case ID I was given back in december. Hopefully it'll be fixed soon!

For me the error is just showing up in android logcat and afaik doesn't prevent me from doing anything I want. Do you know if the issue has actual implications on features?

 

Is there any workaround for iOS? It seems like it's preventing the camera feed from working at all

 

Has anyone been able to resolve this?

 

Great (not). Just upgraded to latest AR Foundation and AR Foundation Remote (Asset) and the issue is back

 

Same. I'm sort of getting around it by blitting the camera frames to a render texture and drawing myself. A real fix is still needed.

An active ARCameraBackground seems to cause some other render pass hooks to be invoked, despite the URP configuration. This no longer happens when you copy that script into your project and use it instead!

Here's a gist I'm using with legacy renderer support stripped and a separate blit script. You can disable the blur option.

https://gist.github.com/marns/0df3335b10b8f2065ae29f18de2c04dd

 

I just encountered this warning message as well.

Unity 2020.3f1 LTS
AR Foundation 4.0.12
ARKit XR Plugin 4.0.12
Universal RP 10.3.2

Unfortunately the hack by @marnsmith does not work for me.

[EDIT] Issue persists with:
AR Foundation 4.1.5
ARKit XR Plugin 4.1.5

 

Confirmed. Updating my project to 2021.1.0b10 Beta solved the issue for me.

 

Damn, I reported this back in December and really hoped it would've been fixed by now...

This is really super annoying. I thought I would be safe using LTS version and verified packages only, but I guess not.

Does anybody know if you can filter out the warning message in Android Logcat?

Please vote Unity Issue Tracker - [URP] [AR Foundation] warning message regarding cameraDepthTarget with URP / AR Foundation projects (unity3d.com)

 

Really doing my head in when debugging a build in Xcode too

 

Same here.
Unity 2020.3 0f1 LTS
AR Foundation 4.0.12
ARKit XR Plugin 4.0.12
Universal RP 10.3.2

Could anyone confirm I can safely ignore the Warning Log?
At the moment it doesn't look to affect anything on the app.

Anyone have a way to comment the Log without disable all of them?

Thanks.

 

No issues here but I do have the error

 

Still experiencing this warning.
Unity 2020.3.4f1 LTS
AR Foundation 4.0.12

 

When I doing this:

blitPass.Setup(renderer.cameraDepthTargetHandle);

inside AddRenderPasses()

I got the same warning. And playmode alwyas stop when I enter game mode