Assertion failed on expression: 'm_BuffersToBind[shaderType][bind].buffer == NULL'
We are getting this error logged approximately 10,000 times a second in our project across all of our workstations.
It happens from unity 2017 all the way up to the very latest release of unity (2018.2.4).
Nothing in the scene is broken, everything runs as expected, however console clearing eventually takes up to 1 minute to clear if you spend over 10 minutes in the scene. Also a noticeable performance decrease over time in the editor. In the build this does not happen.
It is very annoying as I cannot go and debug this code specifically as it is c++ and we don't have access to that.
The reproduction steps are unknown, as it seems we are the only team using unity in the world that is encountering this issue, as googling shows one instance of the error and his fix is unrelated.
Also is there any way to manually suppress errors sent to the console log? and if it is collapsing logs, why does it exponentially take longer to clear? it is just a string and an int representing the log count right?
Here is an image of the error:
Answer by neurograph · Apr 04, 2020 at 11:59 PM
Hi, I'm having the same weird error. I'm trying to upgrade a shader to URP. Any chance you found out what was causing it? Thank you! G.
Hi, the same error here, also trying to upgrade a shader to URP. In order to use URP batching, I wrapped using "CBUFFER_START(UnityPer$$anonymous$$aterial)" and "CBUFFER_END", my shader also included a cginc file, so while I edit the cginc file, I get the same error. Have you found any solution yet?
Your answer
Follow this Question
Related Questions
Loading Next Scene 2 Answers
Can you make a 3d game have "2d lighting"? 0 Answers
Constant messages in the Console 0 Answers
I am new to unity and I am having problems with my code when trying to load the current scene 1 Answer
Saving an image's state 2 Answers