Some users of my game are getting this spam in their logs:
One user in particular, who submitted a report, is running Windows 7 with an NVIDIA GeForce GT 630, which supports DirectX 11 and Shader Model 5.1. This error message was spamming about 3600 times in the course of a couple of minutes of play.
I don’t really have anything to go on. I’m using HDRP 7.4.3, and this doesn’t occur normally when I run the game. Any idea what I can look for to resolve this?
I had another user encounter this today trying my demo, this time with a NVIDIA GeForce GTX 660. The same error/warning spam in the log, resulting in a 16 megabyte log file after a few minutes of play. It looks like this spam was probably being emitted once every frame, which killed performance.
Is there anything I can be looking into with respect to this? Has anyone seen this before? Is it associated with a particular HDRP feature? Right now I can’t reproduce this locally, so I don’t have any way to try to diagnose this further.
I’m still looking for suggestions on this. This turns out to be fairly easy to reproduce. I encounter this easily in the test project associated with bug report #1277585, as long as I use my integrated GPU. But I have users who get this log file spam from the moment they open the game. Here’s the first few lines of the log file of one user, which you can see almost immediately begins emitting this error/warning:
So, my questions are:
Is this a known problem that will be fixed in HDRP 7.x?
Is this due to a specific HDRP feature?
Is there any way to identify this is happening / will happen on any given system due to some value in SystemInfo that I can look for, and react to?
Is this due to a specific problem on the users hardware that cannot be avoided? If so, is it a problem I can detect so that I can warn users about this? Is there a feature they’re missing, so that I can present accurate system requirements?
My colleague has the same problem on his PC which equips GeForce GTX 760.
The problem only occurs in built runtime(not Play mode), but occurs with even the sample scene of the HDRP template project.
This is not a solution to the root of the problem, but in his case, disabling HDRP Decals solved the error message spamming (“Rendering - Decals” checkbox in HDRP Default Frame Settings of Project Settings or the same one in HDRenderPipelineAsset).
It sounds like this log spam behavior is the symptom of several different underlying causes. In the case of the bug report I filed, it was caused by the presence of a “Trails” system in a VFX graph.
So there are multiple things causing some GPUs (possibly low-end GPUs, but still Shader Model 5+ GPUs) to write this stuff to the log file. I definitely don’t think it’s reasonable to stop using decals entirely in my project, given that this happens to only a small number of people. But I would consider it more reasonable if I could detect a specific system info value, and avoid using certain features in cases where that value indicates it will result in this kind of behavior. So far, I don’t have any indication of what it is about certain GPUs that causes this to happen.
I’ve just encountered the same “ShaderProgram is unsupported, but because jobified rendering is enabled the ShaderProgram can not be removed.” message spam in the log file while playing Kerbal Space Program. This made the game freeze completely.
Solution for me was to disable “Optimize for Compute Performace” 3D setting in nvidia control panel. I’m using gtx 970.