Sometimes u will get error spamming issue when enter play mode at URP. Not sure about HDRP but I believe it also have similar issue. You need to tick reload domain or restart unity to fix it which is kind of annoying. This issue still exist at latest 2021.3 LTS version. Any plan to properly fix it to make sure this error spamming will never happen again? I will migrate my project to 2022.2 very soon. I hope 2022.2 won’t happen this error spamming anymore.
Hi! Could you elaborate more on what error you are getting?
Here’s the error
NullReferenceException: Object reference not set to an instance of an object
UnityEngine.Rendering.DebugManager.UpdateActions () (at Library/PackageCache/com.unity.render-pipelines.core@7.4.3/Runtime/Debugging/DebugManager.Actions.cs:176)
UnityEngine.Rendering.DebugUpdater.Update () (at Library/PackageCache/com.unity.render-pipelines.core@7.4.3/Runtime/Debugging/DebugUpdater.cs:18)
I’ve never bothered getting around to reporting this bug since it’s rare and a pain to repro since it requires a big project. But I believe that it’s 100% reproducible.
Steps are:
- Use URP (we’re on 2D, don’t know if that matters)
- Turn off domain reloading
- Make a build
- Enter play mode
And UnityEngine.Rendering.DebugManager will spam errors forever.
The DebugManager is also an anti-feature for us; we’ve seldom want or use it, but sometimes testers bring it up by accident and since they don’t know what they pressed to open it, they’re unable to close it and have to close the game to make it go away.
Hmm this is interesting, I’ve been in 21.3.6f1 all week and not running into issues with the DebugManager, which version specifically are you using? Might be worth submitting a bug report as it might be something that resides in the project or a specific configuration that is leading to this.
To unblock you, you might be able to remove the debug game object that is spawned, I’ve used this in the past when needing to unblock myself when the DebugManager was buggy.
Currently I’m using 201.3.8 and sometimes I will still getting error spamming. I think need to rewrite this DebugManager to make sure this error spamming not happen again.
This is a long standing issue, more info here Errors with the URP Debug Manager page-2
The correct Issue (I think): Unity Issue Tracker - isDebugBuild returns False in the Editor when its value is checked after a build
From the thread above I can see there was this issue reported and it’s already fixed. If that case is not the same as the issue described here we will need a bug report indeed to figure out what’s going on and timeline resolve this.
1 Like
For awareness, DebugManager and DebugUpdater are related to Rendering Debugger - documentation explains how to open/close it: https://docs.unity3d.com/Packages/com.unity.render-pipelines.universal@15.0/manual/features/rendering-debugger.html#how-to-access
It’s also possible to disable this at runtime by using this: https://docs.unity3d.com/Packages/com.unity.render-pipelines.core@15.0/api/UnityEngine.Rendering.DebugManager.html#UnityEngine_Rendering_DebugManager_enableRuntimeUI
DebugManager.instance.enableRuntimeUI = false;
I think this error was fixed a while back but sadly we failed to backport the fix to 2021. I made the backport a few weeks back after getting a report and the fix should be there in the next 2021.3 LTS release.
Do u mean 2021.3.11? Btw does fixed at 2022.2.0b8?
Yes should be in 2021.3.11. I think the original fix went in already in 2022.1 but that wasn’t backported.
The problem is when say we’ve sent the build to a sound designer or tester that’s working with the game, and they hit the shortcut for some reason. I’ve done it by mistake when reaching for the ctrl+prtscrn shortcut that I believe is default for “start screen capture” on some screen recording software, and I’ve had several Discord messages from people going “why did you put in this window, I can’t close it?”. The instinct when a window you’ve never seen before and didn’t want shows up is not to go googling for how to close it - especially since there’s no way to know what the window is called.
A great help would be if it
a) had an X button in the upper right corner so it could be closed like any other window
b) had a “press BUTTON to close” tooltip so people knew how to close it with a shortcut.
c) had a header with the name “Unity Rendering Debugger” so people understood what they had opened
That’s solid feedback, thank you!
Alright. So I can confirm that 2022.2.0b8 has the fix.
1 Like