I keep getting "
Progressive Lightmapper: Material render job skipped - out of system memory.
" whenever I try to bake my lightmaps. I have a RX7600XT with 16gb of vram, 32gb ram, and 200gb of free space on my ssd. I’ve tried clearing my GI cache and putting the maximum cache size to the max and it still doesn’t work.
These are my lighting settings, anything with a lower resolution looks bad so idk what to do.
How much RAM is Unity using around the point where the error fires? It should only happen if memory usage goes about 90% or so. If you are seeing low memory usage, this might be a bug in how how we retrieve memory usage info from the OS.
If you are seeing high memory usage, it’s “expected”, but that high memory usage might be due to a leak or something similar. What kind of scene are you trying to bake? How many renderers are there roughly in it?
Since Unity 2023.2, we made the memory/speed tradeoff in the lightmapper more explicit, which should make bakes more stable. You might want to try it out.
It’s a large city scene, the only light I’m baking is the sun directional light. I don’t think I’d be able to change the Unity version since I’ve had problems with unity 2023 with quest games. There’s probably at least 300 buildings
Wow! That’s a lot of memory usage. We might have a memory leak somewhere.
If you post your log, we might be able to get some hints from it.
If you’d like to investigate further yourself, you can use our memory profiler (Memory Profiler | Memory Profiler | 1.0.0) to get an idea of where the memory is going. However, if most of it is allocated on native side, the tool won’t give very detailed information.
Otherwise, I’d suggest to file a bug report with the project attached. It’s hard to say where the memory is going without access to the project.
Memory profiler didn’t work at first but I restarted unity and it showed about half of the usage from native and a third to graphics
9813321–1409658–Editor.txt (79.6 KB)
I migrated to Unity 6 and I was happy to see that there was an option for low memory usage. Didn’t work.