I am getting 128 bytes of memory allocations per frame when using realtime lighting combined with the dynamic ambient mode. I basically cannot afford to have any allocations during gameplay… is this something that can be refactored?
Bump as this is also a CPU performance regression.
This is not expected. Do you have a small repro project that exhibits the issue? If so, please file a bug so that we can investigate.
We have many automated tests that check for GCAlloc and none of them have ever showed that so I expect this to be a more specific setup.
Also keep in mind that during the first few frames there is bound to be some allocations (new render textures and internal objects necessary for the exeuction of HDRP) but this should never occur after that.
Unfortunately no, our project is a big one, with 265 gb of assets. If I find the time I’ll try profilling on a smaller project, but we’re really busy for the next month.
I can confirm the 128 B GCAlloc is happing every frame in a build, at least on XB1.
